Carlos E. R. wrote:
On Thursday, 2008-10-09 at 21:48 +1030, Rodney Baker wrote:
OK - back to the DVD (or online repository), reinstall zypper via rpm and hopefully we'll be good to go again...
Thanks David and Carlos.
You were right - boost had been updated from 1.33 to 1.36 and zypper requires 1.33. After uninstalling boost 1.36 I was then able to reinstall boost 1.33, libzypp and zypper. All seems to be happy again :-).
I think you should report this as a bug on Bugzilla.
IMO, an automated or manual update should not remove a critical package; certain packages should be listed on a list of critical packages and need a double confirmation with red blinking screen before allowing any of them to be removed.
Kernel, zypper, yast, libc, boot scripts...
-- Cheers, Carlos E. R.
I reported something similar during 11 alpha https://bugzilla.novell.com/show_bug.cgi?id=379480 especially look at comment 4 concerning zypper "Uninstalling zypper is not such a big issue (the in-memory zypper can finish the task)," this bug was about rpm being uninstalled. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org