Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21498 - [xz] After last update - error while loading shared libraries: liblzma.so.0: (...)

Attached to Project: Arch Linux
Opened by Alexandre (alexcortes) - Wednesday, 27 October 2010, 17:27 GMT
Last edited by Pierre Schmitz (Pierre) - Wednesday, 27 October 2010, 20:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: After last update os xz, pacman hang and show: error while loading shared libraries: liblzma.so.0: cannot open shared object file: No such file or directory.

workaround for me: manually extract lzma libs from previous package and put in /usr/lib - and reinstall previous version.


Additional info:

xz 5.0.0-1
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Wednesday, 27 October 2010, 20:31 GMT
Reason for closing:  Not a bug
Comment by Pierre Schmitz (Pierre) - Wednesday, 27 October 2010, 17:43 GMT
How did you exactly manage to break your system like this? A pacman -Syu shouldn't lead to this. Also please attach your pacman.log. Are you using any third party repos or packages (includes packages from AUR).
Comment by Alexandre (alexcortes) - Wednesday, 27 October 2010, 19:36 GMT
So, normaly I recompile all packages (recompile only, without changes). I download the sources of xz and libarchive, "makepkg -i". After the problem and "workaround", reinstall previous version, I use pacman -Syu for test. The upgrade stop after xz install (showing same error). Libarchive cannot be upgraded.

I use some packages from archlinux.fr: yaourt, package-query, flashplugin-prerelease, cairo-dock, cairo-dock-themes)

From AUR - cairo-dock-plug-ins, dropbox-experimental, firefox-branded, fontconfig-lcd, gnome-color-chooser, gnome-theme-infinity, macfonts, mozplugger, nerolinux, notify-osd-bzr, powernowd, ttf-vista-fonts

At these moment, for me, only xz and libarchive needed upgrade.
Sorry my bad english.
   pacman.log (3 KiB)
Comment by Pierre Schmitz (Pierre) - Wednesday, 27 October 2010, 19:40 GMT
Updating packages pacman depends on is not that trivial as you have noticed. (It's similar to bootstrapping; I either hold a copy of the old lib or use a symlink which is ok in this case as the abi didn't change)

In future you should update pacman's deps from our repo first and then recompile them.
Comment by Alexander (Kosmonavt) - Wednesday, 27 October 2010, 20:16 GMT
I also run into this problem. The reason are wrong filenames, which are mistaken by pacman et al.

xz-5.0.0-1 has the following in usr/lib:
liblzma.a
liblzma.so
liblzma.so.5
liblzma.so.5.0.0

Meanwhile applications need liblzma.so.0, which is absent. The problem can be solved by symlink from .so.5 to .so.0 (it does work).

But please correct the package in repos!
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 27 October 2010, 20:25 GMT
> But please correct the package in repos!

packages are correct, if you build your own packages you need to know when there is soname bump like this (pacman -> libarchive -> xz*) you need to update at the same time xz + libarchive, otherwise pacman will fail...

In this way will work because pacman process will still uses the old unlinked lib (deleted).
Comment by Alexandre (alexcortes) - Wednesday, 27 October 2010, 20:25 GMT
I make the sysmlink and work fine.

Thank you.
Comment by Alexandre (alexcortes) - Wednesday, 27 October 2010, 20:31 GMT
Now, all updated. User error, sorry. I make xz first because libarchive depends "xz 5". But, when i try to update with pacman -Syu i has same problem, maybe because the mistake first. I don't no.

Thank you!
Comment by Pierre Schmitz (Pierre) - Wednesday, 27 October 2010, 20:31 GMT
The packages from the repo are correct. You just build your own packages the wrong way.

Loading...