[Bug 223891] New: mozilla-xulrunner181 has wrong upgrade dependencies
https://bugzilla.novell.com/show_bug.cgi?id=223891 Summary: mozilla-xulrunner181 has wrong upgrade dependencies Product: openSUSE 10.2 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla@forge.provo.novell.com ReportedBy: kkaempf@novell.com QAContact: qa@suse.de CC: aj@novell.com, mls@novell.com (Maybe this only affects Beta/RC1 -> RC2 upgrades) Doing an RC1 -> RC2 upgrade, mozilla-xulrunner180 is flagged as "update problem, will be deleted" However, mozilla-xulrunner181 is a valid upgrade package but fails to indicate this. Solution: mozilla-xulrunner181 should provide _and_ obsolete mozilla-xulrunner180 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #1 from wolfgang@rosenauer.org 2006-11-27 08:18 MST ------- While I don't want to question the solution in that case, I still wonder how such stuff should work finally. Version 1.8.1 doesn't obsolete 1.8.0 in general. It's just that we don't want to ship 1.8.0 anymore and want it to be removed if the user accepts that. We achieve that with the proposed solution but we claim that 1.8.1 is compatible with 1.8.0 which is not really the case. So in case users are running third-party applications on top of 1.8.0 they probably don't work anymore with 1.8.1. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |sbrabec@novell.com |mozilla@forge.provo.novell.c| |om | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #2 from kkaempf@novell.com 2006-11-27 10:16 MST ------- "Version 1.8.1 doesn't obsolete 1.8.0 in general." Well, currently it does. mozilla-xulrunner181 has an explicit 'Obsoletes: mozilla-xulrunner180'. However, it fails to specify "Provides: mozilla-xulrunner180" which is needed to have YaST pick it up during distribution upgraded. If both can be installed in parallel, then mozilla-xulrunner181 _must not_ obsolete mozilla-xulrunner180. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #3 from sbrabec@novell.com 2006-11-27 10:54 MST ------- mozilla-xulrunner181 does not provide mozilla-xulrunner180 API so I did not use Provides. Both can be installed in parallel, but because mozilla-xulrunner180 was just dropped, I added Obsoletes to mozilla-xulrunner181. I guess it is correct. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #4 from kkaempf@novell.com 2006-11-27 12:26 MST ------- No, its not correct. With the current dependencies - Both cannot be installed in parallel - mozilla-xulrunner180 isn't properly replaced by mozilla-xulrunner181 So either - drop the 'Obsoletes mozilla-xulrunner180' from mozilla-xulrunner181 This will make both parallel installable (if they don't provide overlapping packages) or - add 'Provides mozilla-xulrunner180' to mozilla-xulrunner181 So it will be recognized as a proper replacement by YaST during system upgrade. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #5 from andreas.hanke@gmx-topmail.de 2006-11-27 12:46 MST ------- Be careful not to mix up things here, you're evaluating an RC1 -> RC2 upgrade. mozilla-xulrunner180 and mozilla-xulrunner181 are parallel installable, but mozilla-xulrunner is not parallel installable with either of them. 10.1 originally had mozilla-xulrunner. This package was not using the update-alternatives system. Then it was renamed to mozilla-xulrunner180 and got update-alternatives support, but this was never part of a released product because it was done after the 10.1 release. And then there is mozilla-xulrunner181 (what we currently have), using update-alternatives, too. Summary: mozilla-xulrunner + mozilla-xulrunner180: Not parallel installable, but mozilla-xulrunner is in fact just a renamed mozilla-xulrunner, so there's a proper upgrade path and no need to install both in parallel. mozilla-xulrunner180 + mozilla-xulrunner181: Parallel installable thanks to update-alternatives, but this does not help because mozilla-xulrunner180 was introduced after 10.1 and dropped before 10.2. mozilla-xulrunner + mozilla-xulrunner181: _Not_ parallel installable. Try it yourself: Use a 10.1 system, build mozilla-xulrunner181 without the "Obsoletes" tag and you'll see that the postinstall scriptlet of mozilla-xulrunner181 will fail because the old mozilla-xulrunner blocks /usr/bin/xulrunner without using update-alternatives and so mozilla-xulrunner181 won't be able to register itself for /usr/bin/xulrunner (it will silently fail). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #6 from kkaempf@novell.com 2006-11-28 01:27 MST ------- comment #5 "Be careful not to mix up things here". Yes, I know. See my initial comment. comment #5 "mozilla-xulrunner180 and mozilla-xulrunner181 are parallel installable" No, they're not since mozilla-xulrunner181 has an explicit "Obsoletes mozilla-xulrunner180". So RPM will remove mozilla-xulrunner180 as soon as it installs mozilla-xulrunner181. Thanks for the summary. 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. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 kkaempf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #7 from kkaempf@novell.com 2006-11-28 01:35 MST ------- Added provides, approved by AJ. -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #9 from andreas.hanke@gmx-topmail.de 2006-11-28 05:08 MST ------- Sorry, now it provides exactly the package it doesn't need to provide: The RC1 -> RC2 upgrade case is now handled (which is neither technically nor from a support point of view necessary), but the 10.1 final -> 10.2 final case is not handled at all. Once again, summarizing the relationships (How to express them in Provides/Obsoletes is up to you because you know better how this depsolver works): - mozilla-xulrunner181 needs to make sure that mozilla-xulrunner as distributed with 10.1 final is removed from the system, as the packages cannot coexist because of lacking update-alternatives support in the original mozilla-xulrunner. - mozilla-xulrunner181 can, but does not have to make sure that mozilla-xulrunner180 is removed from the system because mozilla-xulrunner180 is dropped, but otherwise it can coexist with mozilla-xulrunner181. There is no technical need to remove it, and IMHO the Obsoletes should have been removed instead of adding a Provides next to it. - mozilla-xulrunner181-devel cannot coexist with either gecko-sdk or mozilla-xulrunner180-devel. - mozilla-xulrunner181-i10n does not need to make sure that mozilla-xulrunner180-i10n is removed from the system because the packages can coexist. I do not consider this bug fixed until someone cleary states that the current dependencies behave as intended for a 10.1 final -> 10.2 final upgrade. Right now, the problem mentioned in comment 0 (mozilla-xulrunner being flagged as update problem) is _not_ fixed for a clean 10.1-10.2 upgrade. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #10 from andreas.hanke@gmx-topmail.de 2006-11-28 05:35 MST ------- Proposal: mozilla-xulrunner181 (keep) Obsoletes: mozilla-xulrunner (add) Provides: mozilla-xulrunner (technically not accurate, needed for the upgrade path) (delete) Obsoletes: mozilla-xulrunner180 mozilla-xulrunner181-devel (delete) Obsoletes: mozilla-xulrunner (unless you can explain why this has been added in the first place) (keep) Obsoletes: gecko-sdk (add) Provides: gecko-sdk (technically not accurate, needed for the upgrade path) (delete) Obsoletes: mozilla-xulrunner180-devel (delete) Provides: mozilla-xulrunner180-devel (re-add) Conflicts: mozilla-xulrunner180-devel mozilla-xulrunner181-i10n (delete) Obsoletes: mozilla-xulrunner180-l10n This needs to be reviewed by an rpm expert _and_ a zypp expert _and_ a gecko export *with 10.1->10.2 upgrades in mind*. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 ------- Comment #11 from kkaempf@novell.com 2006-11-28 05:41 MST ------- comment #9 "but the 10.1 final -> 10.2 final case is not handled at all." Bad. Why didn't this bug appear before ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 kkaempf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #12 from kkaempf@novell.com 2006-11-28 05:50 MST ------- comment #10 looks almost fine But I would keep the Provides/Obsoletes of mozilla-xulrunner180 in order to properly clean up from pre-10.2 betas/rcs So I'm - adding "Provides: mozilla-xulrunner" to mozilla-xulrunner181 (for proper 10.1 -> 10.2 update) - adding "Provides: mozilla-xulrunner180-devel" to mozilla-xulrunner181-devel (for proper 10.2 beta/rc -> 10.2 final upgrade) - adding "Provides: mozilla-xulrunner180-l10n" to mozilla-xulrunner181-l10n (for proper 10.2 beta/rc -> 10.2 final upgrade) IMHO, it doesn't make sense to keep a dropped package (mozilla-xulrunner180) on the system. YaST should clean up when updating to 10.2-final -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #13 from andreas.hanke@gmx-topmail.de 2006-11-28 06:46 MST ------- It's still not consistent this way. What about the following points: 1. mozilla-xulrunner181-devel (delete) Obsoletes: mozilla-xulrunner (unless you can explain why this has been added in the first place) Why should the -devel package obsolete the old runtime package? It doesn't look correct. (I won't complain that if this stays, but it looks wrong. mozilla-xulrunner is obsoleted by mozilla-xulrunner181 and not by its -devel package. mozilla-xulrunner181-devel does not have the same meaning as mozilla-xulrunner, but packages should only be obsoleted by another package if it has the same meaning.) 2. mozilla-xulrunner181-devel (add) Provides: gecko-sdk (technically not accurate, needed for the upgrade path) With the Obsoletes left in, but without a Provides added next to it, you would still get gecko-sdk flagged as upgrade problem by YaST when trying a 10.1 -> 10.2 upgrade on a system that had gecko-sdk installed because 10.1 had its gecko development environment in a package named gecko-sdk, now called/superseded by mozilla-xulrunner$VERSION-devel. (I'm unsure whether the solution is accurate in general - it's like saying "libc.so.5 provides libc.so.6", just less obvious - but _if_ this solution is preferred, it should be implemented in a consistent way.) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=223891 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #14 from andreas.hanke@gmx-topmail.de 2006-11-28 07:26 MST ------- Sorry for the noise, closing again. It's OK now. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com