Your message dated Wed, 17 Dec 2025 05:22:24 +0000
with message-id <[email protected]>
and subject line Bug#1107005: fixed in jdim 0.10.1-1.1
has caused the Debian Bug report #1107005,
regarding jdim: 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.)
--
1107005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107005
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jdim
Version: 0.10.1-1
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: jdim
Source-Version: 0.10.1-1.1
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
jdim, 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.
Adrian Bunk <[email protected]> (supplier of updated jdim 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: Tue, 02 Dec 2025 23:15:42 +0200
Source: jdim
Architecture: source
Version: 0.10.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Hideki Yamane <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1107005
Changes:
jdim (0.10.1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Build-Depends: libcrypt-dev. (Closes: #1107005)
Checksums-Sha1:
312f0698974d430de34017f537f0469c7946ecac 1987 jdim_0.10.1-1.1.dsc
51e11983b2a0317160a0990aca8bcd93dac1b51e 4716 jdim_0.10.1-1.1.debian.tar.xz
Checksums-Sha256:
a50f1f5436d6e265c2164bebf551de81dfa10e562b77d26d41755437390169b4 1987
jdim_0.10.1-1.1.dsc
af9d239efcd7f4092ab38a6208ee35e7a8d8c11bf5addec0fb607b346f6fc08b 4716
jdim_0.10.1-1.1.debian.tar.xz
Files:
2a8ab223b7184e1756734b8d3d986750 1987 net optional jdim_0.10.1-1.1.dsc
b99427f8e9d222d55d1057abecbef5c5 4716 net optional
jdim_0.10.1-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmkvk/EACgkQiNJCh6LY
mLE+hBAAlSmm8XbFKrRsh+ZU0jRbGQfGu1Tb9+OSYwCKYSETZIFB5A9GpaW3YOOh
7/QJK2Q3mgsYIgpYZljNp8pCnMrY36qD23QO7EAvDq8ViW31DJhKh9IZscSAcWWd
APrnL0Ak+TKQjpA2WL+75ZaUkd8ZHkP2vhcsZp2aNVE3aED6U+E8amA5PyG/jG/d
mke8hMsnbnIKCwUCp5y6FtkCXqRA9cfWLbsp5RbEGmuIFpenQPbIrw1cowPTI3i/
gK9BdB46NLiYmAlxvlzAUs3/k0T3larn8UxSROpKGn23jIocPcrmTDOdVLqOza2M
WJ58F8gZ6Fkg1qDAaT4xdKHYFXqLzQhXDyqJBueaAPzkZ1OZuwYSYKj81zfikQtL
b24PCHu25qbmnZ5IrrM1K1tRLyw1wkU7i3TKVOh+aRBCbuu+zME6Lp/uj1i1pgiH
xB2ZwVxvS1sLyzfQn1SeaGATYDEzi57kwFRxnVE2MlBbYyOd/y8NakAlRoPtdJBV
Vyx44HLDyl5dSfNUoKFkYehsBzR3u6/0B3k8L6pDqdvhtpWK4scU0DBbpt1az5iB
DgvkP7XHj2BKHj969ircFne/RSRDqXz4LrddO0riq59uKo3L0OlesIRKVMeKf3Dz
bxaL6l3hIUfu+TMwGWpzkcUVUjr7kWgV9tO2fs0wNeDTHXM1m/8=
=XOj8
-----END PGP SIGNATURE-----
pgp7U93QRdnuZ.pgp
Description: PGP signature
--- End Message ---
