Your message dated Tue, 16 Sep 2025 04:04:51 +0000
with message-id <[email protected]>
and subject line Bug#1106980: fixed in guile-3.0 3.0.10+really3.0.10-5
has caused the Debian Bug report #1106980,
regarding guile-3.0: add libcrypt-dev to Build-Depends
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 [email protected]
immediately.)
--
1106980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: guile-3.0
Version: 3.0.10+really3.0.10-4
Severity: normal
User: [email protected]
Usertags: libcrypt-direct
Hello,
please add "libcrypt-dev" to Build-Depends. Presently, libcrypt-dev is
transitively build-essential, because libc6-dev depends on it. There is an
effort[1] to drop this dependency with the result of removing libcrypt-dev from
the build-essential package set. This package was identified as needing an
explicit dependency on libcrypt-dev for one or more of several reasons:
* It failed building in an archive-rebuild with the dependency dropped.
* One of its binary packages issues a binary package dependency on libcrypt1.
* Inspection of source identified "#include <crypt.h>" or -lcrypt.
Rarely, the dependency is of indirect nature. The most common cae is perl
extension modules. For those, a different bug has been filed requesting a
perl-xs-dev dependency instead. As other classes have been excluded from this
filing, it is expected that a direct "Build-Depnds: libcrypt-dev" is indeed
necessary. Once the libcrypt-dev dependency issued by libc6-dev is dropped,
this package will fail to build or build with its crypt-related functionality
disabled. This change will not happen in the trixie cycle but some months into
the forky cycle. Please add the additional dependency in time. Whilst the
additional dependency is safe for inclusion in trixie, it should be added in
the forky cycle to avoid disrupting the trixie release.
Thank you
Helmut
[1] https://lists.debian.org/debian-devel/2025/04/msg00113.html
--- End Message ---
--- Begin Message ---
Source: guile-3.0
Source-Version: 3.0.10+really3.0.10-5
Done: Rob Browning <[email protected]>
We believe that the bug you reported is fixed in the latest version of
guile-3.0, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rob Browning <[email protected]> (supplier of updated guile-3.0 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 15 Sep 2025 21:54:56 -0500
Source: guile-3.0
Architecture: source
Version: 3.0.10+really3.0.10-5
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning <[email protected]>
Changed-By: Rob Browning <[email protected]>
Closes: 1096788 1102606 1102911 1106980
Changes:
guile-3.0 (3.0.10+really3.0.10-5) unstable; urgency=medium
.
* debian/rules: just always try df -h. Instead of avoiding df -h on
hurd-*, just try it everywhere ignoring failures. The previous filter
wasn't quite right, and it turns out, wasn't appropriate anyway. It
looks like the issue is with the buildd's environment, not hurd-* in
general.
.
* debian/rules: compile with -std=gnu17 for GCC 15. Guile's not yet
compatible with C23, now the default in GCC 15, so for the time being,
explicitly restore the GCC 14 default with -std=gnu17. Thanks to
Matthias Klose for reporting the problem. (Closes: 1096788)
.
* Remove debian/source/lintian-overrides.in. Lintan considers the
existence of that path to be an error, so remove it and just generate
the corresponding lintian-overrides content directly.
.
* debian/control: add explicit libcrypt-dev Build-Depends. Thanks to
Helmut Grohne for reporting the issue. (Closes: 1106980, 1102911)
.
* guile-libs.lintian-overrides: add missing brackets.
.
* debian/rules: compile with -ffat-lto-objects to avoid over-stripping.
Without that, dh_strip leaves libguile-3.0.a with no code sections:
https://lintian.debian.org/tags/no-code-sections.html
.
* Fix in-tree cross-compilation builds. Add
0025-build-Fix-in-tree-cross-compilation-build.patch to address the
issue. (Closes: 1102606)
.
* debian/copyright: refresh.
Checksums-Sha1:
db9c01e3dfd6300a493192edac6e646ea0b8842a 2232
guile-3.0_3.0.10+really3.0.10-5.dsc
d6f9e87f33355773f5400b49aeff1590ff55b0e5 46672
guile-3.0_3.0.10+really3.0.10-5.debian.tar.xz
8d5cfbb3f4a9ec3f1182395f7e0b9a18cbfe6d0d 8022
guile-3.0_3.0.10+really3.0.10-5_amd64.buildinfo
Checksums-Sha256:
a5ab235cf29ac1e5c16315c004c69d99237e70a1588b4fb840edfa1e882e1e9d 2232
guile-3.0_3.0.10+really3.0.10-5.dsc
e480d0eddb268e3082431ebdd249964ef252be2b5c469d53a853897ec72e4698 46672
guile-3.0_3.0.10+really3.0.10-5.debian.tar.xz
28848f28570acf547df3c6457e72b6369997b730d5729b05b4eb93b8ad2710be 8022
guile-3.0_3.0.10+really3.0.10-5_amd64.buildinfo
Files:
49a797bdac6fd6d43e0ad896eb752a18 2232 interpreters optional
guile-3.0_3.0.10+really3.0.10-5.dsc
0a29be0437ae718a5f93839d79692d03 46672 interpreters optional
guile-3.0_3.0.10+really3.0.10-5.debian.tar.xz
c7c3a869cc13522522af06472e2fa024 8022 interpreters optional
guile-3.0_3.0.10+really3.0.10-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCgAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmjI3dYVHHJsYkBkZWZh
dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxa8kP+wbEJVN8+sWqKVU9DCJcMKXBAcd8
gtuQmABLnssQ3nvoEWfmwM3dT3+kisObExsTuOg2OLkW8VCYFxX5osBaB0/iiw0a
VSYmXA5gzpQLDt7FoWDP59l5K/V70Le9HVcFmQ4GQgVdOmvsbOo1aeC4aBxyB//O
fGd7lyB9HE5JPmn6bhh+e7B5Q5ojzlgTOUTutI22wpikIDIubh392c/KiuXxP9hL
YKpOcQ7RXmz7ERS6U8aoELuaTYu+Bw2gCRDl4oGCmHRkgONVsmrkirnv0ud0mbga
ZDPaclNTUCjlwLWYGLWvswBiXGMykKmL5FhJYSTHtSrdDQ3JbLaj0ZD4NdcEuAkE
7RpUytjv0+tbnXnCp2lj+fl4xB0CCv492GJH7nCK/o8nN4vOdnyhOxxWEGj1VSek
fIrxRYNrMNj1NrlnRyncN4S+pt4kINqeLHDpwQGcstFbsLKzTMbEmh2bPK8ikHB0
7WfzMGXGSMz8S5Up4kmJJkts1QcdPar7PN1m4YZ/tTcfmuPfqJBVLtXznNrsiP1P
ZBd81OAASfeiqiJlbahlLLsohBmBsuSwCU+mb/n9uaRMgIw+bc+NVw8H4y0Tyk6M
RFIbpjF2yiz3U6w7XJBWIoleJL9qNdrLLTLGxr8h/WNVUTmqvN6z/dBL8/M0Ev6E
KKTzVw0ubsOj/Mxx
=414e
-----END PGP SIGNATURE-----
pgp3Fs5o5lYrB.pgp
Description: PGP signature
--- End Message ---
