[opensuse] Problem with software management after zypper update.
Hello, I just installed an update via the tray applet and now the both the updater and software management seem to be broken? Trying applet gave: Can't launch zypp-checkpatches-wrapper helper program. Make sure zypper package is installed and working. Trying software management in YAST gave: Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libzypp.so.324: cannot open shared object file: No such file or directory No such client module sw_single Run 'yast2 -h' for help on usage Trying to launch zypper in termial i find that there is no zypper on system, just something called "zypper_install". I tried log on/off and then reboot. Same result. Is this happening to anyone else or has something just gone wrong with the update on my particular system? Thanks, David -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-16 at 21:26 -0000, d_garbage wrote:
I just installed an update via the tray applet and now the both the updater and software management seem to be broken?
Yes, it deletes libzypp and you are hosed. Replace manually (rpm --install etc). Known bug. :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHPkeitTMYHG2NR9URAnTNAJ458AmXHtUdd0XwpaEDPahhcd8NSQCfewzb iLIxkdSbS15DmeWDkvFQmtU= =rnuK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Дана субота 17 новембар 2007, Carlos E. R. је написао(ла):
The Friday 2007-11-16 at 21:26 -0000, d_garbage wrote:
I just installed an update via the tray applet and now the both the updater and software management seem to be broken?
Yes, it deletes libzypp and you are hosed. Replace manually (rpm --install etc).
Known bug. :-/
Is there no support in zypp to protect various packages from being deleted by
incident? The same thing happened to me yesterday. Applet removed libzypp and
zypper and I had to download them from the oS-Updates repository manually and
reinstall them manually. Now it works, but that's not the point. Nobody asked
me if I wanted to remove libzypp or anything. I did notice that applet
removes applications from time to time due to some dependency issues or
whatever, but it never asks the user does he want to remove that app. The
applet or zypp obviously have issues which are not nice to have. Using YaST I
can look at "installation summary" and I really don't understand why I can't
see resolved dependencies when I update using the applet. If that is not
possible, maybe the applet should be replaced with something that would only
check if there are updates and then launch yast to do the real update.
- --
Filip Brcic
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-11-18 at 14:41 +0100, Filip Brcic wrote:
Дана субота 17 новембар 2007, Carlos E. R. је написао(ла):
Yes, it deletes libzypp and you are hosed. Replace manually (rpm --install etc).
Known bug. :-/
Is there no support in zypp to protect various packages from being deleted by incident?
It seems it doesn't :-(
The same thing happened to me yesterday. Applet removed libzypp and zypper and I had to download them from the oS-Updates repository manually and reinstall them manually. Now it works, but that's not the point. Nobody asked me if I wanted to remove libzypp or anything. I did notice that applet removes applications from time to time due to some dependency issues or whatever, but it never asks the user does he want to remove that app. The applet or zypp obviously have issues which are not nice to have. Using YaST I can look at "installation summary" and I really don't understand why I can't see resolved dependencies when I update using the applet. If that is not possible, maybe the applet should be replaced with something that would only check if there are updates and then launch yast to do the real update.
Yep, I never update using the suseupdater applet. I simply notice the red color, then fire up the full fledged qt style YOU. This one at least tells you there is a conflict. That way I wasn't catched this time. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHQETwtTMYHG2NR9URAmDfAJ9YxmTifbp55xLnALOiowmQYx6NxQCff6lQ SX2fJ4k7wfJ+zgCI1ccK4lE= =xVNg -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Yep, I never update using the suseupdater applet. I simply notice the red color, then fire up the full fledged qt style YOU. This one at least tells you there is a conflict. That way I wasn't catched this time.
I second Carlos' wisdom. Just use Yast -> Software Management -> Package -> All Packages -> Update if newer version is available. This way, you not only get all security updates, but you can keep all packages updated as well. There is always the risk of a bad package, but I have yet to be burned by any package management problem using this method. -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Дана недеља 18 новембар 2007, David C. Rankin је написао(ла):
Carlos E. R. wrote:
Yep, I never update using the suseupdater applet. I simply notice the red color, then fire up the full fledged qt style YOU. This one at least tells you there is a conflict. That way I wasn't catched this time.
I second Carlos' wisdom. Just use Yast -> Software Management -> Package -> All Packages -> Update if newer version is available.
This way, you not only get all security updates, but you can keep all packages updated as well. There is always the risk of a bad package, but I have yet to be burned by any package management problem using this method.
Yes, I agree. That looks to me as a saf/ner way. But I didn't know that
before. And I use GNU/Linux for 12 years. Usually, I use console tools for
all admin stuff, but since openSUSE came with nice GUI apps and an updater
applet (preinstalled, I didn't install it from some strange obscure
home:someone repo and I didn't install it at all, it was already installed
when I installed oS), why would anyone doubt that it works as should be. This
is a really big minus for openSUSE and this one should be resolved quite soon
or it will generate more problems.
- --
Filip Brcic
David C. Rankin wrote:
Carlos E. R. wrote:
Yep, I never update using the suseupdater applet. I simply notice the red color, then fire up the full fledged qt style YOU. This one at least tells you there is a conflict. That way I wasn't catched this time.
I second Carlos' wisdom. Just use Yast -> Software Management -> Package -> All Packages -> Update if newer version is available.
This way, you not only get all security updates, but you can keep all packages updated as well. There is always the risk of a bad package, but I have yet to be burned by any package management problem using this method.
sure, but how does this resolve the specific zypper update problem? You either choose not to update or you decide to update. If you update, you will be burned, if there was a bad package. If you do not update, you are not burned but you are "behind". Being burned now, I chose to not blindly trust the updater, instead wait a few days, if something bad turns up. This way, I will likely not be burned easily, but I also will need to bear the risk to live longer without security fixes. regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-11-18 at 21:33 +0100, Eberhard Roloff wrote:
I second Carlos' wisdom. Just use Yast -> Software Management -> Package -> All Packages -> Update if newer version is available.
This way, you not only get all security updates, but you can keep all packages updated as well. There is always the risk of a bad package, but I have yet to be burned by any package management problem using this method.
sure, but how does this resolve the specific zypper update problem? You either choose not to update or you decide to update.
It does, in a way. Yast warned that there was a conflict, and as soon as I saw that one of the propossed solutions was to remove libzypp, I quitted. But the suseupdater applet didn't do any warning, it seems. Those that used it were doomed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHQKtutTMYHG2NR9URAvGsAJ9dOotar5oaH4pj99hNNDTusRnXEwCdEtTe LOaUDsRxA77waxAEMCzBL2k= =byBm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Nov 18, 2007 at 10:15:23PM +0100, Carlos E. R. wrote:
The Sunday 2007-11-18 at 21:33 +0100, Eberhard Roloff wrote:
I second Carlos' wisdom. Just use Yast -> Software Management -> Package -> All Packages -> Update if newer version is available.
This way, you not only get all security updates, but you can keep all packages updated as well. There is always the risk of a bad package, but I have yet to be burned by any package management problem using this method.
sure, but how does this resolve the specific zypper update problem? You either choose not to update or you decide to update.
It does, in a way. Yast warned that there was a conflict, and as soon as I saw that one of the propossed solutions was to remove libzypp, I quitted.
But the suseupdater applet didn't do any warning, it seems. Those that used it were doomed.
Becuase in its automatic ways it has been told to "use a working solution" (by specifying -y) and one working solution was to deinstall libzypp and zypper. :/ Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Sunday 2007-11-18 at 21:33 +0100, Eberhard Roloff wrote:
It does, in a way. Yast warned that there was a conflict, and as soon as I saw that one of the propossed solutions was to remove libzypp, I quitted.
No way man, throw caution to the wind ;-) I was brave. (not a production machine) I just selected "Ignore this condition generally" and let her rip. libzypp stayed right where it was supposed to and all updates worked just fine. -- 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 Sunday 18 November 2007 07:41:33 am Filip Brcic wrote:
Дана субота 17 новембар 2007, Carlos E. R. је написао(ла):
The Friday 2007-11-16 at 21:26 -0000, d_garbage wrote:
I just installed an update via the tray applet and now the both the updater and software management seem to be broken?
Yes, it deletes libzypp and you are hosed. Replace manually (rpm --install etc).
Known bug. :-/
Is there no support in zypp to protect various packages from being deleted by incident? The same thing happened to me yesterday. Applet removed libzypp and zypper and I had to download them from the oS-Updates repository manually and reinstall them manually. Now it works, but that's not the point. Nobody asked me if I wanted to remove libzypp or anything. I did notice that applet removes applications from time to time due to some dependency issues or whatever, but it never asks the user does he want to remove that app. The applet or zypp obviously have issues which are not nice to have. Using YaST I can look at "installation summary" and I really don't understand why I can't see resolved dependencies when I update using the applet. If that is not possible, maybe the applet should be replaced with something that would only check if there are updates and then launch yast to do the real update.
This bug didn't bite me again as I didn't updated yet, but there was once the same bug that was deleting libbz2 that wasn't loaded in memory before deletion, rendering anything including rpm useless. The present applet is more annoyance than help with present status of underlaying software. In 10.2 opensuseupdater was what you are looking for. It just checked is there any updates and if you wanted to install them it will run YOU (YaST Online Update) module. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Filip Brcic wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Дана субота 17 новембар 2007, Carlos E. R. је написао(ла):
The Friday 2007-11-16 at 21:26 -0000, d_garbage wrote:
I just installed an update via the tray applet and now the both the updater and software management seem to be broken?
Yes, it deletes libzypp and you are hosed. Replace manually (rpm --install etc).
Known bug. :-/
Is there no support in zypp to protect various packages from being deleted by incident? The same thing happened to me yesterday. Applet removed libzypp and zypper and I had to download them from the oS-Updates repository manually and reinstall them manually. Now it works, but that's not the point. Nobody asked me if I wanted to remove libzypp or anything. I did notice that applet removes applications from time to time due to some dependency issues or whatever, but it never asks the user does he want to remove that app. The applet or zypp obviously have issues which are not nice to have. Using YaST I can look at "installation summary" and I really don't understand why I can't see resolved dependencies when I update using the applet. If that is not possible, maybe the applet should be replaced with something that would only check if there are updates and then launch yast to do the real update.
- -- Filip Brcic
To the best of my knowledge, no. I think it is high time that each and every one on this list write to Novell and ask that this 'feature' be reinstated. It used to be possible for (at least in the case of the kernel) to keep the old kernel and reboot from it if the new one failed. Updates should NOT summarily delete anything unless you specifically OPT for it to do so. At a minimum, it should save it or the RPM it is derived from at least one version deep in case you need to revert to a previous version for any reason. Again, the number of previous versions could be user configurable and it would save only the minimum (rpms or patches) necessary to restore to the previous version, again configurable and only for installed software. Again, for those that have space limitations, this should be an OPTION to save ZERO deep (as it is now) but the default should be at least back to the previous version with a mechanism to revert to that version without being a rocket scientist. If enough people write to Novell and openSuse.org, this *can* happen. It *should* happen, and if it doesn't happen, Novell won't have to worry about it for long because the reputation for bad/defective software will drive it out of the market soon enough. It is one thing to make an honest mistake, it is another to design a system so there is no viable recovery from those mistakes. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 18 November 2007 17:06:10 Richard Creighton wrote:
It used to be possible for (at least in the case of the kernel) to keep the old kernel and reboot from it if the new one failed.
No, that has never been possible. It is possible if you install the new kernel from the command line using rpm -i instead of -U, but it is not, and was never, possible to do in any gui updating tool, not from suse, novell, red hat, ubuntu or anyone else Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Sunday 18 November 2007 17:06:10 Richard Creighton wrote:
It used to be possible for (at least in the case of the kernel) to keep the old kernel and reboot from it if the new one failed.
No, that has never been possible.
It is possible if you install the new kernel from the command line using rpm -i instead of -U, but it is not, and was never, possible to do in any gui updating tool, not from suse, novell, red hat, ubuntu or anyone else
Anders
When I first started using SuSE, when a new kernel was updated, GRUB had 2 (or more) kernels, the new one and any older one(s) still there. I suspect it was using the -i instead of the -U method internally but in my 9.3 version that I used for a long time, I could choose from several kernels. Additionally, it used to save the installed RPMs so that I didn't really need to download a DVD or CD to restore to earlier versions that didn't get properly updated or that I didn't like what the update did. I know about installing the new kernel from the command line with the -i option, BUT that is NOT an option with either YAST or the UPDATER which sumarrily downloads the new RPM and deletes everything and often stuff that I had no clue would also be deleted, like the recent 'boost' deletes zypper 'update'. I am just saying that it needs to have the option and I don't intend to quibble about IF it ever did or didn't, that is not a good excuse for continuing the way it is even if my memory is so faulty as to be totally reversed from reality. The fact remains; If it did, bring it back, if it didn't, MAKE it happen. Either way, it needs to be FIXED so the continual breaking of peoples systems by 'fixes' and 'updates' doesn't render them inoperable or worse. Someone mentioned that openSuSE is 'free' as in beer. So what. We, as users of openSuSE are the great Guinea pigs of society, and what works makes it to paying customers. Unfortunately, a lot of what doesn't work also makes it to paying customers, ala, the recent GM release and the 'REPAIR' program on the install disk just to name one little 'minor' thing that thousands (my estimate) of *paying* customers bought and expected functioning software to be contained on the DVD. I suspect that sooner or later, Novell will face an irate 'customer' or his lawyer in the commercial departments as well because the mentality of 'do the minimum' tends to pervade to all levels of an organization sooner or later. If we are the 'testing arena' for Novel, et al, it makes sense to pay attention to little things like recovery from faulty (regardless of reason) updates and fixes or other software released that doesn't perform as expected. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Дана недеља 18 новембар 2007, Anders Johansson је написао(ла):
On Sunday 18 November 2007 17:06:10 Richard Creighton wrote:
It used to be possible for (at least in the case of the kernel) to keep the old kernel and reboot from it if the new one failed.
No, that has never been possible.
It is possible if you install the new kernel from the command line using rpm -i instead of -U, but it is not, and was never, possible to do in any gui updating tool, not from suse, novell, red hat, ubuntu or anyone else
I was under impression that Fedora's yum and it's GUIs can pin the packages
and that kernel is pin-ed by default (I think 3 or 5 versions of kernel are
kept together). You can also protect the packages from being updated,
changed, deleted or modified in any way, as far as I know (except by rpm -U
or rpm -e, of course). I might be wrong.
On the other hand, you can install the packages that would bring such
functionality to openSUSE too. They are
called "yum-versionlock", "yum-protectbase", "yum-protect-packages", "yum-skip-broken"
and so on. Only they work with yum, not with zypper/yast.
I am not sure about Debian/Ubuntu, but apt-get is one of the most advanced
package wrappers and I doubt that it doesn't support such basic
functionality.
Gentoo's portage also supports package or package group based version locks,
release locks or what ever you like. Gentoo never deletes your old kernel
packages unless you explicitly request the delete.
- --
Filip Brcic
On Friday 16 November 2007 13:26, d_garbage wrote:
Hello, I just installed an update via the tray applet and now the both the updater and software management seem to be broken?
Trying applet gave:
Can't launch zypp-checkpatches-wrapper helper program. Make sure zypper package is installed and working.
Trying software management in YAST gave:
Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libzypp.so.324: cannot open shared object file: No such file or directory No such client module sw_single
Run 'yast2 -h' for help on usage
Trying to launch zypper in termial i find that there is no zypper on system, just something called "zypper_install".
I tried log on/off and then reboot. Same result.
Is this happening to anyone else or has something just gone wrong with the update on my particular system?
Thanks, David David: heres the solution that was posted on the alt.os.linux.suse news group. I just completed it on my 10.3 system and it worked fine. I ran into one issue I had to also delete the boost -doc and -devel before the main rpm would delete.
akarui.tomodachi@gmail.com wrote:
It started all in a sudden. Toda (Novemver 16, 2007), when I started openSUSE 10.3, everything was fine. openSUSE updater application asked me to download some available updates and I started the updater (as a root). But it gave me error message as below:
"Can't launch zypp-checkpatches-wrapper helper program. Make sure zypper package is installed and working."
According to the suggestion, I attempted to install "zypper" package from YAST (Software->Software Management). But, once I click on the "Software Management" icon, an "xmessage" windows pop up with the following error message:
"Error loading language plugin /usr/lib/YaST2/plugin/ libpy2lang_perl.so: libzyppy.so.324: canot open shared object file: No such file or directory No such client module sw_single
Run 'yast2 -h' for help on usage"
Note that, my openSUSE 10.3 is up-to-date, because I always install the available updates everyday.
Here is one fix from Dave Thorp via the SUSEforums.net and the Novell Bugzilla. It worked for me, but I had to choose the 64-bit versions of the packages instead of the 32-bit ones. I hope this helps. Slightly clearer instructions that I've just posted on the bugzilla Ok to solve (for anyone still desperate to get package management back) Go to http://download.opensuse.org/distribution/.../oss/suse/i586/ and pick up the following three packages and save them to their own folder (all 3 packages in one folder) http://download.opensuse.org/distribution/...26.2-2.i586.rpm (libzypp) http://download.opensuse.org/distribution/....1-108.i586.rpm (boost) http://download.opensuse.org/distribution/...8.23-7.i586.rpm (zypper) Open a shell and su to root cd to the folder you put them in rpm -e boost-1.33.1-108.2 (which erases the wonderfully and thoroughly tested package that caused the mess) rpm -ivh *.* Right click on the opensuse updater and click check now and all should be back to normal Hope this helps you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 17 Nov 2007 03:21:21 -0000, Russ Fineman
Hope this helps you.
Thank you Russ for explaining the problem. In the end used these steps to recover: As root: rpm -e boost-1.33.1-108.2 and from the suse/i586 directory of the DVD rpm -ivh boost-1.33.1-108.i586.rpm rpm -ivh libzypp-3.26.2-2.i586.rpm rpm -ivh zypper-0.8.23-7.i586.rpm Thanks again, David -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Anders Johansson -
Carlos E. R. -
d_garbage -
David C. Rankin -
Eberhard Roloff -
Filip Brcic -
Marcus Meissner -
Rajko M. -
Richard Creighton -
Russ Fineman