Dec 6 00:19:41 vulkan pakfire: DOWNLOAD FINISHED: pakfire2/2.27.1-x86_64/paks/tor-0.4.8.9-82.ipfire
Dec 6 00:19:41 vulkan pakfire: PAKFIRE UPGR: alsa: Decrypting…
Dec 6 00:19:41 vulkan pakfire: CLEANUP: tmp
Dec 6 00:19:41 vulkan pakfire: DECRYPT STARTED: alsa
Dec 6 00:19:42 vulkan pakfire: DECRYPT FINISHED: alsa - Status: 0
Dec 6 00:19:42 vulkan pakfire: PAKFIRE UPGR: alsa: Upgrading files and running post-upgrading scripts…
Dec 6 00:19:48 vulkan pakfire: PAKFIRE ERROR: Returncode: 1. Sorry. Please search our forum to find a solution for this problem.
Alsa is a prerequisite for Qemu, too, and these two and a couple of packages are still listed under upgrades after this failed update. I haven’t dared to reboot the machine yet as I don’t want to rebuild it tonight.
mv: cannot stat ‘/etc/asound.state’: No such file or directory
Extracting backup includes…
xz: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
tar: Child returned status 127
tar: Error is not recoverable: exiting now
…Finished.
Stopping ALSA… Saving volumes…
e[1Ae[0Ge[-8Ge[1;34m[e[1;32m OK e[1;34m]e[0;39m
Creating Backup…
tar: Removing leading `//’ from member names
//var/lib/alsa/asound.state
…Finished.
Removing files…
removed ‘/etc/rc.d/init.d/alsa’
(multi-removal of files and directories omitted)
removed directory ‘/var/lib/alsa’
…Finished.
Extracting files…
xz: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
tar: Child returned status 127
tar: Error is not recoverable: exiting now
…Finished.
touch: cannot touch ‘/var/lib/alsa/asound.state’: No such file or directory
Restoring Backup…
var/lib/alsa/asound.state
…Finished.
‘/etc/rc.d/rc3.d/S65alsa’ → ‘…/init.d/alsa’
‘/etc/rc.d/rc0.d/K35alsa’ → ‘…/init.d/alsa’
‘/etc/rc.d/rc6.d/K35alsa’ → ‘…/init.d/alsa’
mv: cannot stat ‘/tmp/asound.state’: No such file or directory
mv: cannot stat ‘/etc/asound.state’: No such file or directory
Extracting backup includes…
xz: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
tar: Child returned status 127
tar: Error is not recoverable: exiting now
…Finished.
Removing files…
removed ‘/var/lib/alsa/asound.state’
removed directory ‘/var/lib/alsa’
…Finished.
Extracting files…
xz: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
tar: Child returned status 127
tar: Error is not recoverable: exiting now
…Finished.
touch: cannot touch ‘/var/lib/alsa/asound.state’: No such file or directory
Restoring Backup…
var/lib/alsa/asound.state
…Finished.
‘/etc/rc.d/rc3.d/S65alsa’ → ‘…/init.d/alsa’
‘/etc/rc.d/rc0.d/K35alsa’ → ‘…/init.d/alsa’
‘/etc/rc.d/rc6.d/K35alsa’ → ‘…/init.d/alsa’
mv: cannot stat ‘/tmp/asound.state’: No such file or directory
I have also found a library link error related to avahi which would also affect people using cups or samba so there will be some other changes coming along as well.
Peter has purged the current version of liblzma and also soundcard firmwares.
I have pushed a fix that is now building…
After removing liblzma pakfire is not able to unpack any files because they are xz compressed. The only way is manually copy a working liblzma on the system.
I put back liblzma.so.5.4.4 from a working system with its matching link (on my broken, not reinstalled system) and reran the update (Alsa release 17->19, it now says). It didn’t work anyway. The logs now say:
Extracting backup includes...
xz: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
tar: Child returned status 127
Does the new version of unpack utilities require liblzma.so.5.4.5, possibly?
If you run ls -hal /usr/lib/liblzma*
what do you get.
I suspect that the linked file liblzma.so.5 is also missing.
If that link is not present then you need to run ln -s /usr/lib/liblzma.so.5.4.4 /usr/lib/liblzma.so.5
and then try the update again.
If that still has a problem then I would suggest the best approach would be to do a fresh install of CU181 on your broken system, do a restore and then try the update to CU182 Testing.
I rebooted the system, and to my surprise it actually rebooted fine. Alsa could still not be updated, however.
So I uninstalled Alsa. Then I updated all other packages, one of them being Qemu, which has Alsa as a dependency. Then everything updated and Alsa installed fine as a dependency! However, Alsa can still not be run from the rc.d script, perhaps the installer is not checking for the error while the updater does – or something.
Reading back through this thread, I believe that you have not done a fresh install of 181 and then upgraded to 182 with the corrected upgrade package that @arne_f provided.
I believe that you put back in the liblzma library and got the upgrade to “work”.
Maybe something still is not correct with the completed upgrade because of the initial hiccup.
It might be better to start with a fresh install of CU181, install your addons and then do the restore of your backup and the addon backups and then do the change to the Testing branch and upgrade to CU182.
