FS#15817 - [pacman] Pacman update results in broken pacman: liblzma.so.0:: No such file or directory

Attached to Project: Arch Linux
Opened by Alessandro (laynor) - Wednesday, 05 August 2009, 20:38 GMT
Last edited by Allan McRae (Allan) - Friday, 07 August 2009, 11:45 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Allan McRae (Allan)
Architecture All
Severity High
Priority Normal
Reported Version 3.2.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Pacman update results in broken pacman.
Steps to reproduce:
I ran pacman -Sy mercurial, pacman asked for a pacman upgrade. I answered Yes, and pacman upgraded. However, now running pacman results in an error:
pacman: error while loading shared libraries: liblzma.so.0: cannot open shared object file: No such file or directory
return code: 127
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 07 August 2009, 11:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.3.0-3
Comment by Eric Belanger (Snowman) - Wednesday, 05 August 2009, 21:54 GMT
I don't know why you are getting this error. liblzma.so.0 is provided in xz-utils package. Pacman depends on libarchive which depends on xz-utils.

To fix your system, download the xz-utils package. Uncompress it and copy liblzma.so.0 and liblzma.so.0.0.0 to /usr/lib
That should fix pacman. Don't forget to run 'pacman -Sf xz-utils' afterwards to install xz-utils correctly.
Comment by Alessandro (laynor) - Wednesday, 05 August 2009, 22:16 GMT
I used pacman.static to repair my system, but thanks anyway.
I don't know why but maybe pacman has broken dependencies - or tries to install itself before xz-utils?
The sure point is that when pacmn got upgraded, xz-utils was not installed.
Comment by Xavier (shining) - Wednesday, 05 August 2009, 22:33 GMT
which pacman version did you use for upgrading?
Comment by Alessandro (laynor) - Wednesday, 05 August 2009, 23:01 GMT
I have no idea :) I already upgraded pacman.
Comment by Eric Belanger (Snowman) - Thursday, 06 August 2009, 00:01 GMT
check your /var/log/pacman.log
Comment by Eric Belanger (Snowman) - Thursday, 06 August 2009, 00:04 GMT
What version of libarchive were you using? Was it up-to-date? The xz-utils depends was added in libarchive 2.7.0-2
Comment by Alessandro (laynor) - Thursday, 06 August 2009, 00:13 GMT
I upgraded from pacman version 3.2.2-1.
Upgrading pacman did not upgrade libarchive. The version before the pacman upgrade was 2.0.7-1.
libarchive got upgraded after fixing my system (installing xz-utils by hand with pacman.static) when I ran pacman -Syu.
Comment by Allan McRae (Allan) - Thursday, 06 August 2009, 00:24 GMT
Look like pacman needs a versioned dep...
Comment by Dan McGee (toofishes) - Thursday, 06 August 2009, 00:50 GMT
I thought the 2.7.0 bump was enough, whoops. What is the chance anyone else hits this? I'm not sure it is worth a rebuild/signoff cycle until we get to a potential 3.3.1.
Comment by Dan McGee (toofishes) - Thursday, 06 August 2009, 00:51 GMT
And on a side note, Allan- your linker flags would have saved us here I think.
Comment by Allan McRae (Allan) - Thursday, 06 August 2009, 05:03 GMT
Anybody that had not upgraded libarchive to 2.7.0-2 before doing an update will be hit as pacman will be upgraded first. So this is people who have not updated since 2009-06-10.
Comment by Allan McRae (Allan) - Thursday, 06 August 2009, 05:35 GMT
Ouch... that includes everyone not doing an ftp install from the current install media.
Comment by Allan McRae (Allan) - Thursday, 06 August 2009, 05:51 GMT
No, I was wrong. It includes everyone who last updated between ~2009-04-16 (when libarchive-2.7.0 was released) and 2009-06-10 (when the -2 version was packaged for Arch).
Comment by Nagy Gabor (combo) - Thursday, 06 August 2009, 10:33 GMT
Since this is just a packaging error, we should fix this asap (pacman 3.3.0-3).
Comment by Xavier (shining) - Thursday, 06 August 2009, 10:41 GMT
+1 for fixing this asap

these issues are quite annoying.. easy to miss for us and painful for users.
Comment by Allan McRae (Allan) - Thursday, 06 August 2009, 11:39 GMT
pacman-3.3.0-3 is now in [testing], which fixes this issue.

Loading...