http://bugzilla.novell.com/show_bug.cgi?id=555627
http://bugzilla.novell.com/show_bug.cgi?id=555627#c17
Michael Andres
Created an attachment (id=333559) --> (http://bugzilla.novell.com/attachment.cgi?id=333559) [details] my repository selection (sorted by priority)
I have prioritised a few repositories differently once again.
Better, but the priority of the update repo (download.opensuse.org/update/11.2) should be higher than the distro(download.opensuse.org/distribution/11.2) to be sure you actually get the released updates. It's also no problem if you assign a buildservice repo which is based on 11.2 the same (or even an higher) priority as the 11.2 distro. Just take care the 11.1 based ones are low. (In reply to comment #15)
Created an attachment (id=333562) --> (http://bugzilla.novell.com/attachment.cgi?id=333562) [details] questionable suggestion for package dependency resolutions
Can the solver cope with the dependency hell here?
Yes. I admit the messages are sometimes hard to interpret, but that's not a bug. So please stop reopening this report unless you actually hit one. If you more need, check the links at help http://en.opensuse.org/Communicate. -- Problem: libapt-pkg-libc6_8-6-2-0.5.15lorg3.2-78.1.x86_64 requires librpm-4.4.so()(64bit), but this requirement cannot be provided The new zypper needs a new librpm. librpm-4.4 belongs to the the old 11.1 rpm. You've got several apt related 11.1 packages, that wont work with the 11.2 rpm. As there's no update for them, the solver asks you what to do. If you are uncertain what to do, try 'zypper up --force' instead. The solver won't ask you how to resolve the conflict, but suggest to delete the conflicting packages. Check whether the suggested deletions are acceptable, and proceed if they are. If they are not, you need to find an 11.2 based repo that provides newer versions of the software which works on 11.2 -- or you stay with 11.1. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.