Bug#1065135: [Pkg-openssl-devel] Bug#1065135: sort: error while loading shared libraries: libcrypto.so.3
On 2024-02-29 20:37:25 [-0800], Steve Langasek wrote: > This is definitely not the behavior we want. However, the good thing is > that the dependency from coreutils to libssl is new since bookworm. As a > result, while this can affect users on upgrades from testing, it will not > affect upgrades from bookworm because libssl3t64 will be unpacked and > configured before the coreutils that uses it. Can I close this or there something that needs to be done here? Or do we wait until it gets migrated to testing? I *think* we could limit some of the dependencies since `sort' most likely needs nothing from libcrypto… But there were other reported (such as libreadline) so I'm not sure. Sebastian
Bug#1065135: sort: error while loading shared libraries: libcrypto.so.3
Hey. On Thu, 2024-02-29 at 20:37 -0800, Steve Langasek wrote: > Thanks for this report. Another case: Removing libreadline8:amd64 (8.2-3+b1) ... awk: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory awk: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory Selecting previously unselected package libreadline8t64:amd64. Not sure,... shall I report distinct bugs for each of them? > This is definitely not the behavior we want. However, the good thing > is > that the dependency from coreutils to libssl is new since bookworm. > As a > result, while this can affect users on upgrades from testing, it will > not > affect upgrades from bookworm because libssl3t64 will be unpacked and > configured before the coreutils that uses it. So at least for this case, only people tracking testing/unstable may be screwed ;-) ... that is of course only *if* any such error would ever cause any kind of "corruptions". > Can you explain why 'sort' is being called at this point in your > upgrade? > Is this from an apt hook or something? Hard to say... at that point in the upgrade output, are there any APT hooks running at all? Or is it just DPKG hooks? In the other case with libpam where runuser failed, it was likely /usr/share/debian-security-support/check-support-status.hook as Sam Hartman had pointed out. TBH, I'm not sure whether I know all places from where DPKG may load hooks or trigger or the likes. I looked now at: $ ls -1 /etc/dpkg/dpkg.cfg.d/ debian-security-support needrestart But none of them seems to call sort or awk, at least not directly nor the script they're executing (I haven't gone any deeper into debconf or so). These are the triggers, right? $ ls -1 /var/lib/dpkg/triggers/ File Lock Unincorp aspell-autobuildhash ispell-autobuildhash ldconfig resolvconf-enable-updates resolvconf-event rkhunter-propupd rkhunter-update-database texmf-format texmf-hyphen texmf-map twisted-plugins-cache update-ca-certificates update-ca-certificates-fresh update-ca-certificates-java update-ca-certificates-java-fresh update-default-ispell update-default-wordlist update-initramfs update-openoffice-dicts update-sgmlcatalog But AFAIU the actual code that is executed for the trigger, is in the postinst of that package, right? If so,... could be any of them, where sort/awk get called. Cheers, Chris.
Bug#1065135: sort: error while loading shared libraries: libcrypto.so.3
Thanks for this report. This is definitely not the behavior we want. However, the good thing is that the dependency from coreutils to libssl is new since bookworm. As a result, while this can affect users on upgrades from testing, it will not affect upgrades from bookworm because libssl3t64 will be unpacked and configured before the coreutils that uses it. If we see widespread breakage from this in upgrades from testing/unstable then we can try to figure out further mitigations. Can you explain why 'sort' is being called at this point in your upgrade? Is this from an apt hook or something? On Fri, Mar 01, 2024 at 04:53:30AM +0100, Christoph Anton Mitterer wrote: > Package: libssl3t64 > Version: 3.1.5-1.1 > Severity: normal > X-Debbugs-Cc: vor...@debian.org > > Hey there. > > > Just a friendly meant heads up: > > I saw another case similar to #1065017, i.e. where during the t64 transition. > a library is missing while sort (which I think is also considered essential?) > is > executed, causing that to fail. > > (Reading database ... 483226 files and directories currently installed.) > Removing libssl3:amd64 (3.1.5-1) ... > sort: error while loading shared libraries: libcrypto.so.3: cannot open > shared object file: No such file or directory > Selecting previously unselected package libssl3t64:amd64. > (Reading database ... 483215 files and directories currently installed.) > > > Attaching the full APT term log and CCing, Steve Langasek who seems to have > been > among those in charge of the transition. > > > Thanks, > Chris. > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) > Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libssl3t64 depends on: > ii libc6 2.37-15 > > libssl3t64 recommends no packages. > > libssl3t64 suggests no packages. > > -- no debconf information -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1065135: sort: error while loading shared libraries: libcrypto.so.3
Package: libssl3t64 Version: 3.1.5-1.1 Severity: normal X-Debbugs-Cc: vor...@debian.org Hey there. Just a friendly meant heads up: I saw another case similar to #1065017, i.e. where during the t64 transition. a library is missing while sort (which I think is also considered essential?) is executed, causing that to fail. (Reading database ... 483226 files and directories currently installed.) Removing libssl3:amd64 (3.1.5-1) ... sort: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory Selecting previously unselected package libssl3t64:amd64. (Reading database ... 483215 files and directories currently installed.) Attaching the full APT term log and CCing, Steve Langasek who seems to have been among those in charge of the transition. Thanks, Chris. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libssl3t64 depends on: ii libc6 2.37-15 libssl3t64 recommends no packages. libssl3t64 suggests no packages. -- no debconf information term.log.xz Description: application/xz
