On Thu, 9 Oct 2008 22:18:27 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.
Carlos, To be honest I'm not even sure if it was an automatic update or a manual update/install that I did through Yast that caused the problem. I have installed KDE 4.1.2 from the Factory repository on 10.3 which may also have caused the problem - as has been pointed out several times in recent weeks, running anything from Factory can be risky. 4.1.2 has been stable and very useable with virtually no problems of note, apart from this one glitch and, as I said, I can't attribute it to a fault in any particular component. It is more likely a case of PEBKAC (Problem Exists Between Keyboard and Chair) in that I may well have selected to upgrade the boost package, not realising (or paying enough attention to the fact) that zypper was going to be deleted in the process. Had I realised what was going to happen, I would not have allowed that update. Having said all that, I will see if YOU tries to update boost again now that I've reverted it to 1.33. If it does and it breaks zypper again, I'll definitely be reporting it as a bug. Cheers, -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================