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!
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!
FS#61428 - [libidn2] 2.1.0-1 breaks arch linux in unprivileged lxc guest
Attached to Project:
Arch Linux
Opened by ipp (n8V8r) - Wednesday, 16 January 2019, 13:34 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 16 January 2019, 13:38 GMT
Opened by ipp (n8V8r) - Wednesday, 16 January 2019, 13:34 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 16 January 2019, 13:38 GMT
|
DetailsDescription: having upgraded to 2.1.0-1 in an unprivileged lxc guest the guest cannot be started any more
Additional info: * host ubuntu cosmic (4.18.0-13-generic) | libidn2-0 2.0.5-1 amd64 | lxc 3.0.3 | systemd 239-7ubuntu10.6 amd64 * guest arch linux | systemd 239.370 | libidn2 2.0.5-1 -> 2.1.0-1 Steps to reproduce: pacman -Suy --ignore libsystemd,systemd,systemd-sysvcompat :: Running post-transaction hooks... (1/6) Reloading system manager configuration... /usr/bin/systemctl: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory error: command failed to execute correctly (2/6) Creating system user accounts... /usr/bin/systemd-sysusers: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory error: command failed to execute correctly (3/6) Creating temporary files... /usr/bin/systemd-tmpfiles: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory error: command failed to execute correctly _____ Starting the container on the host with > lxc-start dns -F produces /sbin/init: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory _____ The issue is not present with version 2.0.5-1. Why does it require now a separate kernel module suddenly? Since the container cannot be started the package cannot be rolled back and thus the container is rendered unusable. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Wednesday, 16 January 2019, 13:38 GMT
Reason for closing: Not a bug
Additional comments about closing: Don't break your system by doing partial updates, and your system will stop being broken. Magic!
Wednesday, 16 January 2019, 13:38 GMT
Reason for closing: Not a bug
Additional comments about closing: Don't break your system by doing partial updates, and your system will stop being broken. Magic!