[opensuse] Zypper died suddenly!
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week. Oops. zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory Now, yast won't start (dbus error), zypper won't start. I suppose I might manually copy the library, if I knew where to get it and where to put it. Is there anything I can do short of reinstalling suse? I do have the opensuse ISO's on my hard drive, but since I haven't downloaded Krusader since going to 11.2, I don't know how to get into it. Even if the .619 version is there. Keep in mind that I'm a fairly advanced _user_ with no more SA skills than one learns by watching and asking questions on this list (embedded systems engineer -- wasn't even sure what "systems administrator" meant until subscribing here :-). John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-05-11 at 11:43 -0400, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Wow. What did you do? :-o It should be in /usr/lib/libzypp.so...., and it comes with libzypp...rpm. You can install it directly with rpm. However, you should need a consistent set of tools, it probably won't do to have a part recently updated and another from the dvd. I think we discussed this some time ago in the list, search for it; I'm tired and sleepy, I'm not of much use right now :-) Maybe just install the entire set from the dvd (now, what is the entire set?), later update. And also, investigate how that library could have disappeared. Faulty update? Human action? Faulty filesystem? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkvpgtUACgkQtTMYHG2NR9UsMACfdZf5LGEU/yNpxPBiQ/nYy6Us iWAAn3ehwYxODwaw8pxdaTtaRz4RL6oF =3PAK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 11 May, 2010 at 11:43:59 -0400, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Not good. As Carlos said: It would be good to know (how/why) what changed. Something like 'less /root/.bash_history' (as root) might help retrace your steps?
Now, yast won't start (dbus error), zypper won't start.
Not entirely surprising, in that both probably need libzypp.so.NNN which is not found. Looking at http://download.opensuse.org/distribution/11.2/repo/oss/suse/i586/libzypp-6.... with Konqueror's embedded KRPMview, we see that it contains libzypp.so.619 This tells us that 'zypper' most likely is the version which is contained on the install medium - since it's referencing the libzypp version from the install medium. It *might* also indicate that 'libzypp' was updated - since that would have replaced /usr/lib/libzypp.so.619 with (f.x.) /usr/lib/libzypp.so.631 (as is the case on my system which has been updated more or less continuously)
I suppose I might manually copy the library, if I knew where to get it and where to put it.
Manually copying individual library files onto the system as almost certainly not a good idea. Manually upgrading packages, however, might be.
Is there anything I can do short of reinstalling suse?
Reinstalling shouldn't be neccessary. But now might be a good time to backup whatever you have on there, in case any of the things I'm about to suggest make matters any worse ;) (In this next bit I'm just assuming the architechture is i586, so substitute x86_64 if neccessary) The first thing I'd suggest is to find out which version of libzypp is actually present on the system: rpm -q libzypp and ll /usr/lib/libzypp.so* should tell us that. Next: Depending on the outcome of the above (which I'm guessing will be that libzypp *is* present, but newer than the version from the install medium) - I would probably suggest to upgrade zypper, yast, et al. to a consistent 'level'. This would entail something like: mkdir -p /tmp/packages Then download individual rpms from: http://download.opensuse.org/update/11.2/rpm/i586/ to /tmp/packages The reason for using a directory is that you can then use: rpm --test -Uvh /tmp/packages/* - which will let rpm figure out the order to upgrade the rpms present in /tmp/packages As for which rpms to download: Well, it may take some iterations to get the dependencies sorted out, but it's probably going to be something on the order of: jon@nx8220:~> rpm -q --whatrequires libzypp zypper-1.3.4-0.1.3.i586 yast2-qt-pkg-2.18.22-1.1.1.i586 libqdialogsolver1-1.3.0-2.12.1.i586 yast2-pkg-bindings-2.18.11-1.3.1.i586 Initially though, just try with zypper-<version>.rpm, run the rpm command, and see what happens. Once rpm stops complaining about dependencies, you should be good to run the command without '--test', to actually install/upgrade the packages.
I do have the opensuse ISO's on my hard drive, but since I haven't downloaded Krusader since going to 11.2, I don't know how to get into it. Even if the .619 version is there.
the way to 'access' a local iso is by 'loop mounting' it, as in: mount -o loop /path/to/name-of.iso /mnt/ But downgrading to the versions on the iso might bring a whole other set of complications, so if at all possible I would go for updating instead.
Keep in mind that I'm a fairly advanced _user_ with no more SA skills than one learns by watching and asking questions on this list (embedded systems engineer -- wasn't even sure what "systems administrator" meant until subscribing here :-).
you will definitely want to have a look at 'rpm --help' and 'man rpm' before and during the above... ;) hth /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/11/2010 10:43 AM, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Now, yast won't start (dbus error), zypper won't start. I suppose I might manually copy the library, if I knew where to get it and where to put it. Is there anything I can do short of reinstalling suse? I do have the opensuse ISO's on my hard drive, but since I haven't downloaded Krusader since going to 11.2, I don't know how to get into it. Even if the .619 version is there.
Keep in mind that I'm a fairly advanced _user_ with no more SA skills than one learns by watching and asking questions on this list (embedded systems engineer -- wasn't even sure what "systems administrator" meant until subscribing here :-).
John Perry
I ran into the same problem when another instructor installed a new copy of 11.2, this same error occurred each time the instructor installed 11.2. A workaround, that worked for this time anyhow, is I created a symbolic link libzypper.so.619 pointing to the current libzypp.so.631.0.4 library, after that zypper and yast ran and I was able to post all updates etc.... Looking in software management (before I posted the update(s)) for what ever reasons libzypp was updated and zypper was not. Some where something failed on the install, I never did see the full error, hoping tomorrow to try the install again see if I can figure it out. Hope this helps. Thanks, Tony -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/11/2010 11:43 AM, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Now, yast won't start (dbus error), zypper won't start.
Thanks, all. Carlos:
Wow. What did you do? :-o
As I said above, I just stopped using "zypper dup" and started using "zypper up". On the second "up", I got that error. The first one appeared to go just fine, so I was pretty happy -- until this :-). ---------------------------------------- Jon:
Something like 'less /root/.bash_history' (as root) might help retrace your steps?
Since I only go to the command line for special reasons (like zypper), I didn't expect to find anything there (the last few lines of 500 :-): zypper dup ifconfig wlan0 ethtool wlan0 ip addr wlan0 ip addr help ip addr show dev wlan0 exit zypper dup zypper up exit zypper up The first zypper dup was from a couple of weeks ago, just before I was experimenting with networking commands after a message on this list made me curious. I don't see anything here that could show a problem? I was reading over the rest of your message, and trying to work up the courage to go through this scary process, when ------------------------------------------------------ Tony's message came up:
A workaround, that worked for this time anyhow, is I created a symbolic link libzypper.so.619 pointing to the current libzypp.so.631.0.4 library,
and it worked fine for me! Apparently I'm not the only one who had this problem? Maybe switching from "dup" to "up" did something similar to what your fellow instructor did? I created the link, ran zypper up (30 packages to upgrade, 1 new, 2 to change arch.), got a couple of errors, ran it again, go no errors. The kupdater icon was still yellow, so I clicked "check now" and it turned red (java security update), and it did its thing and turned green. I started up yast, and it came up, refreshed all the repositories, and waited for a command. I shut it down, since I only use it for installing new packages and system configuration maintenance. So for now, it looks pretty good. Thanks much, all -- particularly Tony, who gave me a successful workaround that was much less scary than Jon's. I suppose sometime soon I'll work up the courage to delete the link and see if my zypper is up to date... jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-05-12 at 16:27 -0400, John E. Perry wrote:
Carlos:
Wow. What did you do? :-o
As I said above, I just stopped using "zypper dup" and started using "zypper up". On the second "up", I got that error. The first one appeared to go just fine, so I was pretty happy -- until this :-).
Ah. Mmm. Ugh. Er... what a funny, er... weird mixtup. Perhaps dup was updating from some repo with newer versions (or older, dup can do that), then now you are getting just updated from the official repo, and got a mixture of, incompatible, versions. I'm not explaining it well. It's late and I'm tired. I have a vague idea of what might have happened, but I can't explain it well :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkvrQuAACgkQtTMYHG2NR9UpNgCcDwSpeNvuJ1ZZ/NKJWv1DJlPY mo4AnRhDa7PT+L2tzfxbTgbU3fA4W6Li =GIkJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/13/2010 02:07 AM, Carlos E. R. wrote:
On Wednesday, 2010-05-12 at 16:27 -0400, John E. Perry wrote:
Carlos:
Wow. What did you do? :-o
As I said above, I just stopped using "zypper dup" and started using "zypper up". On the second "up", I got that error. The first one appeared to go just fine, so I was pretty happy -- until this :-).
'zypper up' is probably innocent here. It might be packaging error (maybe i forgot to bump the version of libzypp on which zypper depends?). To get it working again, please install satsolver-tools, libzypp, and zypper from this repository (if you run Factory): http://download.opensuse.org/repositories/zypp:/Head/openSUSE_Factory/ If you don't have libzypp working, you need to do it with rpm, of course. HTH -- cheers, jano Ján Kupec YaST team ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz ---------------------------------------------------------(EOF)---
On Thursday 13 May 2010 09:30:00 Jano Kupec wrote:
'zypper up' is probably innocent here. It might be packaging error (maybe i forgot to bump the version of libzypp on which zypper depends?).
No you IMO can't mess up the package that way. Zypper requiring 'libzypp.so.619' is covered by rpms auto-requires. It's the version zypper was linked against, and updating 'libzypp.so.631' must lead to a dependecy problem. The solver should have reported this, or some error occurred in the middle of installation and led to an inconsistent system. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 12 May, 2010 at 16:27:22 -0400, John E. Perry wrote:
On 05/11/2010 11:43 AM, John E. Perry wrote:
Jon:
Something like 'less /root/.bash_history' (as root) might help retrace your steps?
Since I only go to the command line for special reasons (like zypper), I didn't expect to find anything there (the last few lines of 500 :-):
<snip>
The first zypper dup was from a couple of weeks ago, just before I was experimenting with networking commands after a message on this list made me curious. I don't see anything here that could show a problem?
No. It ws more of a "let's check, in case something turns up". I wasn't much expecting anything either. Especially since lots of things, like invocation af yast2 from inside a GUI, won't show.
I was reading over the rest of your message, and trying to work up the courage to go through this scary process, when
Not much to be scared of, really ;) None of the 'rpm -q <something>' commands do anything potentially harmful, and as long as you pass '--test' then neither will 'rpm -Uvh <something>'. So the only thing 'scary' is getting lots of various output thrown at you... :D
------------------------------------------------------
Tony's message came up:
A workaround, that worked for this time anyhow, is I created a symbolic link libzypper.so.619 pointing to the current libzypp.so.631.0.4 library,
and it worked fine for me! Apparently I'm not the only one who had this problem? Maybe switching from "dup" to "up" did something similar to what your fellow instructor did?
I think Jano's probably right.
I suppose sometime soon I'll work up the courage to delete the link and see if my zypper is up to date...
Just: rpm -q zypper I get: jon@nx8220:~> rpm -q zypper zypper-1.3.4-0.1.3.i586 - which is the current 'openSUSE 11.2 Updates' version. hth /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/13/2010 04:22 AM, Jon Clausen wrote:
On Wed, 12 May, 2010 at 16:27:22 -0400, John E. Perry wrote: ...
I was reading over the rest of your message, and trying to work up the courage to go through this scary process, when
Not much to be scared of, really ;)
:-) -- Says you! Back up everything. Create a temporary directory Download individual rpms ... True, it all looks pretty safe, and I'm sure it is for you. But I've followed directions I thought I understood before and run into trouble. And as I said, I was working through it to be sure I really understood the instructions before starting when Tony's suggestion arrived.
... Just:
rpm -q zypper
I get: jon@nx8220:~> rpm -q zypper zypper-1.3.4-0.1.3.i586
embelex:/usr/lib # rpm -q zypper zypper-1.3.4-0.1.3.i586 So it appears I'm up to date. In fact, looking back through zypper's command-line log, I find the fourth package is ----------------- Retrieving package zypper-1.3.4-0.1.3.i586 (4/31), 859.0 KiB (3.6 MiB unpacked) Retrieving delta: ./rpm/i586/zypper-1.2.8_1.3.4-0.1.3.i586.delta.rpm, 532.0 KiB Retrieving: zypper-1.2.8_1.3.4-0.1.3.i586.delta.rpm [done (93.3 KiB/s)] Applying delta: ./zypper-1.2.8_1.3.4-0.1.3.i586.delta.rpm [done] Installing: zypper-1.3.4-0.1.3 [done] Additional rpm output: Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.permissions... Checking permissions and ownerships - using the permissions files /etc/permissions /etc/permissions.easy /etc/permissions.d/mail-server /etc/permissions.d/postfix /etc/permissions.local setting /usr/sbin/zypp-refresh-wrapper to root:root 4755. (wrong permissions 0755) Finished. ---------------------------------------- ...followed by several packages of yast. (Had to edit out a LOT of trailing spaces to get most of the lines together! Why do zypper and rpm do that?) So it appears Tony's trick was enough to get zypper back in good shape, and my system back up to date. Thanks very much! Not only is my system fixed, but I've learned some neat stuff. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 13 May, 2010 at 11:36:38 -0400, John E. Perry wrote:
On 05/13/2010 04:22 AM, Jon Clausen wrote:
On Wed, 12 May, 2010 at 16:27:22 -0400, John E. Perry wrote:
Not much to be scared of, really ;)
:-) -- Says you!
:D
Back up everything. Create a temporary directory Download individual rpms ...
True, it all looks pretty safe, and I'm sure it is for you. But I've followed directions I thought I understood before and run into trouble.
Yeah, I know how that feels... Very sensible to tread lightly.
And as I said, I was working through it to be sure I really understood the instructions before starting when Tony's suggestion arrived.
See that's something *I* would've been a little wary of. I've had things go pretty wrong, by 'just symlinking' some version of some lib, to a different version... which reminds me: The link you created probably isn't doing anything bad, but I'd suggest removing it anyways. Since your zypper is now at the 'current' version, the link shouldn't be neccessary anymore, and it might cause confusion at some later stage...
... Just:
rpm -q zypper
embelex:/usr/lib # rpm -q zypper zypper-1.3.4-0.1.3.i586
So it appears I'm up to date.
Indeed. Nice :)
So it appears Tony's trick was enough to get zypper back in good shape, and my system back up to date.
Thanks very much! Not only is my system fixed, but I've learned some neat stuff.
:) /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 5/13/2010 12:06 PM, Jon Clausen wrote:
See that's something *I* would've been a little wary of. I've had things go pretty wrong, by 'just symlinking' some version of some lib, to a different version... which reminds me:
The link you created probably isn't doing anything bad, but I'd suggest removing it anyways. Since your zypper is now at the 'current' version, the link shouldn't be neccessary anymore, and it might cause confusion at some later stage...
I ran into this as well, (on a machine that had a clean install of 11.2 some months ago. Not only did zypper die, but so did Yast software management. ldd /usr/bin/zypper revealed a missing libzypp.so.619 Wary or not, there was virtually no other way to repair the system other than descending into rpm hell. For many naive users this is a PERMANENT breakage. Their opensuse distro is forever blocked from correcting itself, and they are forever blocked from fixing it without some friendly guru to help out. The one thing that MUST not break. It broke simply by running the software updater. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/15/2010 01:59 PM, John Andersen wrote:
... Wary or not, there was virtually no other way to repair the system other than descending into rpm hell.
For many naive users this is a PERMANENT breakage. Their opensuse distro is forever blocked from correcting itself, and they are forever blocked from fixing it without some friendly guru to help out.
Well, I know about symlinking and libraries and such, and I was thinking about searching the library directories for a libzypp to try that with. But I'd never done it with my system software, and I decided to get some advice before either risking a corrupt system or going through the hassle of a reinstall.
The one thing that MUST not break. It broke simply by running the software updater.
Yes, that's true, and scary. But it did get fixed. In fact, taking advantage of Jon's wisdom, I deleted the link, ran "zypper up", and got ... Loading repository data... Reading installed packages... The following package updates will NOT be installed: ffmpeg gnokii gpsd gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-bad-lang gstreamer-0_10-plugins-base gstreamer-0_10-plugins-base-lang gstreamer-0_10-plugins-good libavcodec52 libavdevice52 libavformat52 libavutil50 libfaad2 libmp3lame0 libpostproc51 libschroedinger-1_0-0 libswscale0 libvlc2 libvlccore2 taglib-sharp vlc-beta vlc-beta-gnome vlc-beta-noX vlc-beta-qt The following packages are going to be upgraded: gpa grass grass-docs libgdal1 libpython2_6-1_0 libvlc5 libvlccore5 mozilla-kde4-integration python python-base python-numpy python-tk python-xml qgis qgis-devel qgis-plugin-grass tomboy tomboy-lang 18 packages to upgrade. ... And things finished up fine. But now yast doesn't run. I'll have to restart my system to see if one of the updates disabled it... jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/15/2010 05:06 PM, John E. Perry wrote:
... And things finished up fine.
But now yast doesn't run. I'll have to restart my system to see if one of the updates disabled it...
And I just started up yast and its software manager, and all went well (at least, until I want to download some package. It refreshed the repositories and waited for a command, so things look good at the moment). jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 15 May, 2010 at 10:59:33 -0700, John Andersen wrote:
On 5/13/2010 12:06 PM, Jon Clausen wrote:
See that's something *I* would've been a little wary of. I've had things go pretty wrong, by 'just symlinking' some version of some lib, to a different version...
I ran into this as well, (on a machine that had a clean install of 11.2 some months ago.
Not only did zypper die, but so did Yast software management.
Definitely not good.
ldd /usr/bin/zypper revealed a missing libzypp.so.619
Wary or not, there was virtually no other way to repair the system other than descending into rpm hell.
Yeah, but IMHO it's sort of a "lucky punch" that the app and the lib *did* function properly. While there is some work involved in manually resolving deps, it's also the 'more proper way'. Manually linking libs is a pretty 'dirty' hack, and there is potential for stuff to go wrong in colorful ways. But either way:
For many naive users this is a PERMANENT breakage. Their opensuse distro is forever blocked from correcting itself, and they are forever blocked from fixing it without some friendly guru to help out.
For these users even invoking ldd is going to appear as black magic. But if any of them should be looking over my shoulder, I'd much rather that they see how to fix such a situation by using rpm, rather than ways to 'shortcircuit' the system.
The one thing that MUST not break.
+1
It broke simply by running the software updater.
Very very unfortunate. /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 15 May 2010 19:59:33 John Andersen wrote:
On 5/13/2010 12:06 PM, Jon Clausen wrote:
See that's something *I* would've been a little wary of. I've had things go pretty wrong, by 'just symlinking' some version of some lib, to a different version... which reminds me:
The link you created probably isn't doing anything bad, but I'd suggest removing it anyways. Since your zypper is now at the 'current' version, the link shouldn't be neccessary anymore, and it might cause confusion at some later stage...
I ran into this as well, (on a machine that had a clean install of 11.2 some months ago.
Not only did zypper die, but so did Yast software management.
ldd /usr/bin/zypper revealed a missing libzypp.so.619
If some zypper log containing the "zypper up" that messed up your system is still available, please send it to me. Maybe it contains some hint to what actually caused the error. Helpfull would be: - /var/log/zypp/history - /var/log/zypper.log ( or zypper.log-YYYMMDD.gz in case the log rotated ) -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres ZYPP Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/18/2010 07:09 AM, Michael Andres wrote:
On Saturday 15 May 2010 19:59:33 John Andersen wrote:
On 5/13/2010 12:06 PM, Jon Clausen wrote:
See that's something *I* would've been a little wary of. I've had things go pretty wrong, by 'just symlinking' some version of some lib, to a different version... which reminds me:
The link you created probably isn't doing anything bad, but I'd suggest removing it anyways. Since your zypper is now at the 'current' version, the link shouldn't be neccessary anymore, and it might cause confusion at some later stage...
I ran into this as well, (on a machine that had a clean install of 11.2 some months ago.
Not only did zypper die, but so did Yast software management.
ldd /usr/bin/zypper revealed a missing libzypp.so.619
If some zypper log containing the "zypper up" that messed up your system is still available, please send it to me. Maybe it contains some hint to what actually caused the error.
Helpfull would be: - /var/log/zypp/history - /var/log/zypper.log ( or zypper.log-YYYMMDD.gz in case the log rotated )
Michael, I see you replied to my message above without asking for the logs. Do you not want mine, too? jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 19 May 2010 08:04:34 John E. Perry wrote:
Michael,
I see you replied to my message above without asking for the logs. Do you not want mine, too?
Yes, if they are available. (directly to ma@suse.de please) -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres ZYPP Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R. -
Jano Kupec -
John Andersen -
John E. Perry -
Jon Clausen -
Michael Andres -
Tony