https://bugzilla.novell.com/show_bug.cgi?id=443135 Summary: Zypper/libzypp/satsolver should be more careful with arch changes Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: markus.kossmann@gmx.de QAContact: qa@suse.de Found By: --- Created an attachment (id=250878) --> (https://bugzilla.novell.com/attachment.cgi?id=250878) archive with testcase, zypper.log the zypper output on the command line Trying to update beta4 x86_64 to current factory I get : [...] Die folgenden Pakete werden die Architektur ändern: 3ddiag akonadi-runtime aqbanking at-spi babl-0_0 beagle bluez bug-buddy cairomm chmlib [...] python-satsolver rpm rpm-python sane-frontends satsolver-tools sax2 sax2-gui [...] You see the arch changes include rpm :-( which will cause an update failure and an unusable system after that. And that's not the first time I got that problem during the 11.1 development cycle. Trigger for that problem is probably one of the new -32bit.x86_64 packages with a broken dependency to a .i586 package as it happened before. But I think the solver should become more smart and should try to recognize such a broken dependency. Some ideas for that: Are there really valid cases where a -32bit.x86_64 package depends on an .i586 package ? Is it reasonable that i.e rpm or zypper/libzypp changes arch if the user didn't direct the updater to do so ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.