[opensuse] Zypper deleted (WTF???!!!)
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself! The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path. This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something. Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been... Thanks, -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-10-09 at 07:01 +1030, Rodney Baker wrote:
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself!
You are not using factory, per chance? By the way, I never use autoupdates.
The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path.
This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something.
Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been...
You should be able to install from the DVD using rpm, and giving in the same line all deps. If you don't have the dvd, just point rpm to any one of the mirrors; but I think it's better to download manually first. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjtMnkACgkQtTMYHG2NR9XYmwCfQsfun5Zi1yBUbmvRUT1dan17 3rMAn1/oDgD+tK/4UYPyCApQukqcoZaK =wHZ5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rodney Baker wrote:
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself!
The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path.
This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something.
Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been...
Thanks,
This also occurs if the packman repo is enabled. It updates a zypper dependency and wipes out zypper if you answer the solution question the wrong way... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 9 Oct 2008 11:36:22 David C. Rankin wrote:
Rodney Baker wrote:
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself!
The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path.
This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something.
Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been...
Thanks,
This also occurs if the packman repo is enabled. It updates a zypper dependency and wipes out zypper if you answer the solution question the wrong way...
It is possible that this may be what has happened - I do use Packman for multimedia stuff and I may simply not have been concentrating... 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. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
On Thu, 9 Oct 2008 21:18:08 Rodney Baker wrote:
On Thu, 9 Oct 2008 11:36:22 David C. Rankin wrote:
Rodney Baker wrote:
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself!
The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path.
This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something.
Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been...
Thanks,
This also occurs if the packman repo is enabled. It updates a zypper dependency and wipes out zypper if you answer the solution question the wrong way...
It is possible that this may be what has happened - I do use Packman for multimedia stuff and I may simply not have been concentrating...
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 :-). Thanks, -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjt74wACgkQtTMYHG2NR9V1jACdGFggeU615bZGlV6hi3LBTyEN sQIAniFTlveOlJVs5+0ESrJgKkbhtY83 =ccpE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
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 ===================================================
Rodney Baker wrote:
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,
I think it's packman's mplayer update if I recall from when it bit me. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rodney Baker wrote:
On Thu, 9 Oct 2008 21:18:08 Rodney Baker wrote:
On Thu, 9 Oct 2008 11:36:22 David C. Rankin wrote:
Rodney Baker wrote:
Hi all. For some reason, after the last round of auto updates (or software installation, I'm not sure which), zypper has been deleted from my system. I certainly did not do this myself!
The last entry in zypper.log was on 10.06.08 at 21:57 local time (which probably doesn't help anyone). Some time after this, zypper has been erased. Running 'which zypper' (as root) reveals no zypper found anywhere in the path.
This means that I can't run online updates or any of the Yast package management plugins. RPM still seems to be installed - at least that's something.
Can someone point me to the zypper rpm so I can reinstall it please? I may have to resolve some dependencies manually if anything else has been deleted that shouldn't have been...
Thanks, This also occurs if the packman repo is enabled. It updates a zypper dependency and wipes out zypper if you answer the solution question the wrong way... It is possible that this may be what has happened - I do use Packman for multimedia stuff and I may simply not have been concentrating...
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 :-).
Thanks,
I was speaking from, umm.. personal experience... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Dave Plater -
David C. Rankin -
Rodney Baker