Hi, Quoting Guillem Jover (2024-01-11 00:32:50) > On Thu, 2024-01-11 at 00:19:58 +0100, Samuel Thibault wrote: > > Johannes Schauer Marin Rodrigues, le jeu. 11 janv. 2024 00:12:09 +0100, a ecrit: > > > The util-linux problem is no surprise because less fails to install when > > > investigating that issue I noticed the version of less is 487 which is the > > > version from old-old-stable. Is that plausible? > > > > It has been failing to build for a long time already and is still > > waiting for somebody to contribute a fix, see > > https://buildd.debian.org/status/logs.php?pkg=less&arch=hurd-i386 > > I looked into it and it seemed trivial, so I've got a patch I'm polishing now > and will submit today. thank you, Guillem! I subscribed to #1060420 as well as the upstream bug to make sure I get notified once this gets fixed. since in chrootless mode, maintainer scripts run tools from the outside, it is most useful if the version of the tools on the inside is as close as possible (best equal) to the version of the tools on the outside. To find out if there are other cases similar to less, I wrote a new mmdebstrap hook which will be part of the next mmdebstrap release. Here is its current output for when creating a Hurd chroot: W: libc0.3 is not installed on the outside W: version of coreutils differs 9.4-3 (outside) -> 9.1-1 (inside) W: version of libbz2-1.0 differs 1.0.8-5+b2 (outside) -> 1.0.8-5+b1 (inside) W: hurd-libs0.3 is not installed on the outside W: version of tar differs 1.35+dfsg-2 (outside) -> 1.34+dfsg-1.4 (inside) W: version of diffutils differs 1:3.10-1 (outside) -> 1:3.7-5 (inside) W: version of grep differs 3.11-4 (outside) -> 3.6-1 (inside) W: version of startpar differs 0.65-1+b1 (outside) -> 0.65-1 (inside) W: version of less differs 590-2 (outside) -> 487-0.1+b1 (inside) W: version of libpam0g differs 1.5.2-9.1+b1 (outside) -> 1.4.0-10 (inside) W: version of libdb5.3 differs 5.3.28+dfsg2-4+b1 (outside) -> 5.3.28+dfsg2-4 (inside) W: version of libcom-err2 differs 1.47.0-2+b1 (outside) -> 1.46.6-1 (inside) W: version of libkrb5support0 differs 1.20.1-5 (outside) -> 1.20.1-3 (inside) W: version of libk5crypto3 differs 1.20.1-5 (outside) -> 1.20.1-3 (inside) W: version of libkrb5-3 differs 1.20.1-5 (outside) -> 1.20.1-3 (inside) W: version of libgssapi-krb5-2 differs 1.20.1-5 (outside) -> 1.20.1-3 (inside) W: version of libpam-modules-bin differs 1.5.2-9.1+b1 (outside) -> 1.4.0-10 (inside) W: version of libpam-modules differs 1.5.2-9.1+b1 (outside) -> 1.4.0-10 (inside) W: version of passwd differs 1:4.13+dfsg1-3+b1 (outside) -> 1:4.13+dfsg1-3 (inside) W: hurd is not installed on the outside W: version of login differs 1:4.13+dfsg1-3+b1 (outside) -> 1:4.13+dfsg1-3 (inside) W: version of gpgv differs 2.2.40-1.1+b1 (outside) -> 2.2.40-1.1+hurd.1 (inside) W: version of liblz4-1 differs 1.9.4-1+b2 (outside) -> 1.9.4-1 (inside) W: version of libidn2-0 differs 2.3.4-1+b2 (outside) -> 2.3.4-1+b1 (inside) W: version of libtasn1-6 differs 4.19.0-3+b2 (outside) -> 4.19.0-3 (inside) W: version of libgnutls30 differs 3.8.2-1 (outside) -> 3.8.1-4+b1 (inside) I think the most gaping version differences are: - coreutils: last successful build in 2022 and fails to configure now (might be fixable by passing '--disable-year2038 to ./configure) - pam: last successful build in 2021 and fails with "THIS CODE IS KNOWN TO WORK ONLY ON LINUX" and "error: sys/prctl.h: No such file or directory" - grep: last successful build in 2021 and fails its testsuite with "grep: memory exhausted" Of those three, only pam seems to have a patch (#1029097). Thanks! cheers, josch
Attachment:
signature.asc
Description: signature