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.