https://bugzilla.novell.com/show_bug.cgi?id=379480
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=379480#c7
Ján Kupec changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jkupec@novell.com
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #7 from Ján Kupec 2008-04-24 09:35:49 MST ---
Schubi, the point here is not the forcing of resultion with drastic removals.
The point is than even if you specifically request to remove rpm with libzypp
(e.g. by choosing to do so in the dependency resolution prompt), it should not
fail on the half of the way - it should ensure that it succeds (e.g. by
postponing the removal of rpm to the end).
Even if you upgrade rpm, we should not rely on the old rpm being called until
the new one is installed, and the start using the new one for the rest of the
commit process - the rpm update should be moved to the end. OK, this is not
that urget like the 'remove' case, but it can break something, too.
As for the removal of zypper itself, i don't agree that that should be forbiden
in any way. What we _could_ do is to display a "Warning: you are about to
remove zypper! You'll be lost without it! :O)". But that would be just a minor
enahncement bug (i think i'll do it anyway). The above is what matters.
--
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.