https://bugzilla.novell.com/show_bug.cgi?id=223891 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.hanke@gmx-topmail.de ------- Comment #8 from andreas.hanke@gmx-topmail.de 2006-11-28 02:33 MST ------- (In reply to comment #6)
If mozilla-xulrunner180 was never on a released product, the bug is not that important for 10.2, since it only affects beta/rc upgrades.
No, the bug does affect upgrades from released products as well because of mozilla-xulrunner (the one with neither 180 nor 181 in its name). mozilla-xulrunner181 really needs mozilla-xulrunner to be removed from the system because mozilla-xulrunner did not use update-alternatives and therefore it can break the registration browser because YaST uses the /usr/bin/xulrunner symlink which is occupied by the old mozilla-xulrunner and can't be updated by update-alternatives unless the old package is removed from the system. I don't know how this relationship is expressed correctly (I think that Conflicts is more accurate than Provides/Obsoletes, but YaST tends to show a lot of unpleasant popups for Conflicts), but it's necessary to remove mozilla-xulrunner from the system no matter how. The Obsoletes on mozilla-xulrunner180 was never necessary because until the moment the Obsoletes was added, mozilla-xulrunner180 and mozilla-xulrunner181 were indeed parallel installable and without the Obsoletes they still are from the mozilla point of view. This is now solved for 10.2 (in a not quite optimal way because there are much more Obsoletes/Provides than necessary - only the ones that mozilla-xulrunner180 had should have been transfered to mozilla-xulrunner181 and not random ones added that were intended for supporting RC1-RC2 upgrades and are not even for that necessary), but for future products, you will need a more scalable solution. As a starting point, the registration browser should not rely on the /usr/bin/xulrunner symlink because it's (a) not very reliable because of the "|| :" in the %post section and (b) very hard to predict where this link points to because update-alternatives allows changing it. This becomes a problem whenever you really allow multiple versions to be installed or even ship multiple versions in a product. -- 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, or are watching someone who is.