When I try to apply the latest updates on my 11.3 system, I get the following Warning. I think this is because I did the “switch system packages” to Packman after I installed it. What is the recommended solution?
#### YaST2 conflicts list - generated 2010-07-27 16:30:26 ####
patch:k3b-2785.noarch conflicts with k3b.x86_64 < 2.0.0-1.1.1 provided by k3b-2.0.0-1.pm.2.7.x86_64
] do not install patch:k3b-2785.noarch
] Following actions will be done:
install k3b-2.0.0-1.1.1.x86_64 (with vendor change)
http://packman.links2linux.de --> openSUSE
install k3b-lang-2.0.0-1.1.1.noarch (with vendor change)
http://packman.links2linux.de --> openSUSE
#### YaST2 conflicts list END ###
That seems to keep that package in the list of patches to be installed, just unchecked. Then, the next time I open Online Update, I get the same prompt again. Is there a more permanent solution, or is it just a matter of time before Packman will provide a similar update that will automatically get rid of this problem?
Looking for a more permanent solution, or a way to avoid such problems in the future. Perhaps change the repo priorities? I mean, all I did was add the Packman repo, I didn’t even switch packages or anything.
I chose to open YaST and install the updates manually, and then chose the option “do not install patch:k3b-2785.noarch”, but the updater applet is still bothering me with it.
The whole point of using Packman instead of packages from third-party repos was to avoid conflicts like this. This is why I don’t use Firefox from the Mozilla repo, VLC from the VideoLan repo and so on.
Also, Packman packages are great because usually they’re more up-to-date than the ones in the openSUSE repos, but still not as bleeding-edge as the original vendor’s repos so there are lesser chances of breaking something. When I was new to openSUSE, I was in the habit of installing the latest versions of things like k3b, VLC etc. It worked for the moment, but eventually there were so many conflicts due to mixed up dependencies, that I had to format and start fresh.
No, it means you’ll be changing the vendor to openSUSE. I guess that’s a “solution”, but not if you want to use the Packman version.
Anyways, seeing as how there are no other viable solutions, I went with this option. Atleast the updater applet is no longer troubling me. When Packman comes out with a newer k3b package, I’m switching back.
I think this is fine, but you also use the k3b-codecs from packman?
To keep packman do as deano quoted: ‘do not install patch:k3b-2785.noarch’ and preserve the Packman packages.
Changing priority will not stop the patch.
The update applet doesn’t bother me because I remove it.
If you have /want to use the Packman packages the surely ticking
] Following actions will be done:
install k3b-2.0.0-1.1.1.x86_64 (with vendor change)
[PackMan :: Startseite](http://packman.links2linux.de/) --> openSUSE
install k3b-lang-2.0.0-1.1.1.noarch (with vendor change)
[PackMan :: Startseite](http://packman.links2linux.de/) --> openSUSE
is the way to go, as it indicates to use the Packman packages. Or maybe I am missing the point.