https://bugzilla.novell.com/show_bug.cgi?id=304150#c1 --- Comment #1 from Martin Vidner 2007-08-24 00:53:42 MST --- Hm, you are right. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304150#c2 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #2 from Klaus Kämpf 2007-08-29 08:15:37 MST --- No, you are not ;-) It would be a minor speed improvement to first read the rpmdb and check if the to-be-removed package is actually installed. However, in order to ensure dependency consistency in the installed system, the dependency solver needs to get the 'whole view'. It doesn't know if 'foo' is a leaf package (no other installed packages depend on it) or not. If foo is not a leaf package, removing it will break dependencies of other packages. And here the solver jumps in and will try to 'heal' such breakage. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304150#c4 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Resolution|INVALID |LATER --- Comment #4 from Ján Kupec 2007-08-30 00:52:39 MST --- (In reply to comment #3 from Cristian Rodriguez)

AFAICS, zypper rm will **refresh** (aka. download the updated metadata) of remote installation source to delete a package...

It will refresh only if autorefresh is enabled and the metadata is out of date.

does that make sense ? I can

see below

accept that it will refresh the local metadata cache (kinda odd, but looks like the system has a whole lot of unneeded, excessive complexity behind a simple rpm -e foo :( )

so the question is:

why it needs new metadata from the network to perform this operation ? o_O

The answer is simple: removal of a non-leaf package creates a dependency problem which you need to resolve. You DO need metadata for that. Additionally, the UP-TO-DATE metadata come handy if the removal triggers installation (you choose to install some other package to resolve a dependency conflict). I belive you agree with the above. What makes sense (and what's actually what you originally suggested, right?) is to check whether the package in question is _installed at all_ before trying to load metadata so that zypper can tell the user that it is not installed and be done. Klaus suggested that the performance gain of this would be small, with which i don't fully agree - loading metadata takes some time, and eventual autorefresh makes it even worse. Doing all this only to get 'not installed' message is a waste. IMO, it makes sense to implement this. I don't consider it a bug however, changing to enahncement and to LATER. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304150#c6 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #6 from Ján Kupec 2007-10-06 08:06:48 MST --- reopening for 11.0 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304150 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- 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.