Your message dated Sat, 27 Mar 2021 16:33:44 +0000 with message-id <e1lqbse-000eqn...@fasolo.debian.org> and subject line Bug#985311: fixed in libxcrypt 1:4.4.18-2 has caused the Debian Bug report #985311, regarding libxcrypt migration blocker: inappropriate Build-Dependency: libltdl-dev during freeze to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: libxcrypt Version: 1:4.4.18-1 Severity: serious libxcrypt introduced a new dependency cycle: src:libxcrypt Build-Depends on libltdl-dev (new) libltdl-dev is built from src:libtool src:libtool implicitly Build-Depends on libc6-dev libc6-dev depends on libxcrypt-dev libxcrypt-dev is built from src:libxcrypt The change in Build-Depends is inappropriate at this point of the freeze. Please revert and discuss how the change can be performed in a way that does not break architecture bootstrap. I think that libxcrypt really only needs /usr/share/aclocal/ltdl.m4. This file happens to be part of libtool, but it is otherwise architecture-independent and could be moved to an Arch:all package in principle. Doing so would unbreak cross bootstrap, but I don't understand the effects on a native bootstrap. As a workaround, I propose vendoring ltdl.m4. It is not uncommon to vendor m4 files for autoconf. While this usually makes updating them hard, this seems to be an exceptional case where such vendoring could be justifiable. As a long term solution, I propose demoting the libc6-dev -> libxcrypt-dev dependency to Recommends. Doing so shrinks the expectation of what build-essential provides. In any case, now is the wrong time to add this dependency. I'm filing it at rc severity to prevent testing migration during the bullseye freeze. Once bullseye is released, I no longer see a reason for it being rc even if it remains unsolved. That should give enough time to evaluate options and keep bullseye bootstrappable. Helmut
--- End Message ---
--- Begin Message ---Source: libxcrypt Source-Version: 1:4.4.18-2 Done: Marco d'Itri <m...@linux.it> We believe that the bug you reported is fixed in the latest version of libxcrypt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri <m...@linux.it> (supplier of updated libxcrypt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 27 Mar 2021 17:11:11 +0100 Source: libxcrypt Architecture: source Version: 1:4.4.18-2 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri <m...@linux.it> Changed-By: Marco d'Itri <m...@linux.it> Closes: 985311 985372 Changes: libxcrypt (1:4.4.18-2) unstable; urgency=medium . * Stop depending on libltdl-dev and instead just include in the package the relevant part of /usr/share/aclocal/ltdl.m4. (Closes: #985311) * Include upstream commit 86d1e4e to fix cross-compilation. (Closes: #985372) Checksums-Sha1: a51a329938be1fed722d23af54865929d9e4e573 1463 libxcrypt_4.4.18-2.dsc 41c5a5f65e9e9ae60da4348737c6df17e6af7972 7184 libxcrypt_4.4.18-2.debian.tar.xz cca4ddc2029d565b0023eb2123a867b0710916bd 6400 libxcrypt_4.4.18-2_amd64.buildinfo Checksums-Sha256: 52fc0204433da9c0a53034db0e70f0418cb671cd6e2e50518cac702ddb7af0de 1463 libxcrypt_4.4.18-2.dsc 1c6c4bd9e14c5022c8897a922391caa2c8b1a34dff1cd59d3bd2f229166c7247 7184 libxcrypt_4.4.18-2.debian.tar.xz 4fd5ccbd3d5751d473f93a740c58b5613095d9ad391bdd3b5dc8818ca0aadca4 6400 libxcrypt_4.4.18-2_amd64.buildinfo Files: 371bc42bbd5ec040e67e9ad266b1a59e 1463 admin optional libxcrypt_4.4.18-2.dsc a91e40a40099a2a22886c0b6688a01e6 7184 admin optional libxcrypt_4.4.18-2.debian.tar.xz cf4ef27e7b4e0751375432eaf0f3c306 6400 admin optional libxcrypt_4.4.18-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCYF9cYQAKCRDLPsM64d7X gdOzAQCURoG/0VesrfUZf24tUDBfFEiJjR/UQwwRX9LmAWz8qQD+I4OjHqS8AN+X bTGQrkHd77AUwKUOcNUNidhJ0Xy7yg4= =+/uI -----END PGP SIGNATURE-----
--- End Message ---
