[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1106975: marked as done (calife: add libcrypt-dev to Build-Depends)

Your message dated Thu, 28 Aug 2025 21:51:09 +0000
with message-id <E1urkWT-000wKM-0k@fasolo.debian.org>
and subject line Bug#1106975: fixed in calife 1:3.0.6-1
has caused the Debian Bug report #1106975,
regarding calife: 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 owner@bugs.debian.org
immediately.)


-- 
1106975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106975
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: calife
Version: 1:3.0.1-6
Severity: normal
User: helmutg@debian.org
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: calife
Source-Version: 1:3.0.6-1
Done: Andreas Tille <tille@debian.org>

We believe that the bug you reported is fixed in the latest version of
calife, 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 1106975@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <tille@debian.org> (supplier of updated calife 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 28 Aug 2025 23:04:02 +0200
Source: calife
Architecture: source
Version: 1:3.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Closes: 1106975
Changes:
 calife (1:3.0.6-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * QA upload.
   * New upstream version
   * Maintain package in Debian team on Salsa
   * Add Homepage
   * Fix watch file
   * Drop debian/README.debian since redundant
   * d/copyright: DEP5
   * Add libcrypt-dev to Build-Depends
     Closes: #1106975
   * d/rules: Add hardening options
   * Standards-Version: 4.7.2 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Try to make autoreconf work
   * Pristine-tar=true
 .
   [ Nicolas Schodet ]
   * Add fix-ac-define.patch and enable autoreconf at build time
   * Add fix-linux-build.patch, to fix Linux build.
     Thanks to Ahmad Khalifa for the patch
   * Install new README*.md files
   * Add use-cppflags.patch, to make hardening work
Checksums-Sha1:
 3e9c7213a518f299e10858882cc5fdc728cea3d4 1864 calife_3.0.6-1.dsc
 1fe9d366db32533227e4ba00ee4e543e0b3d0e40 98768 calife_3.0.6.orig.tar.xz
 09be6b0c9e19f2230477f69778b5b5da8fca36aa 5856 calife_3.0.6-1.debian.tar.xz
 57eff4b52cd0f870db7f052efbafb52fb3b166bf 6031 calife_3.0.6-1_amd64.buildinfo
Checksums-Sha256:
 f476e740cb3c16eed3956d58308070324977bdf7eea072f54d91163cd32b2029 1864 calife_3.0.6-1.dsc
 f09b5c73439bab14a7ff1438b8f22a8da6216a5caf0ef8467f85467b2217357e 98768 calife_3.0.6.orig.tar.xz
 87ef2ec1377c72de60e735d2bc14464c7c30105bc58a181a1427aff677fef52b 5856 calife_3.0.6-1.debian.tar.xz
 ce61d1eff81c21bebc900c100a8f3d050989e715cea3e4b7d08876d180dd6fb9 6031 calife_3.0.6-1_amd64.buildinfo
Files:
 bb9f66db1d4f1b4b9c92e579e6548136 1864 admin optional calife_3.0.6-1.dsc
 cd9762d41db90cad6d614de43197c693 98768 admin optional calife_3.0.6.orig.tar.xz
 0ae4b677a38213c389d7e9945025588d 5856 admin optional calife_3.0.6-1.debian.tar.xz
 61bf69f51a80ed416bd4347a8bf55bb3 6031 admin optional calife_3.0.6-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiwxKMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF2Ng//TwcoMfxqKgvlJdmauBMcxmATNgsrZvdm
k0Fce2wSNn6rTe4uyUE7zKS68yAepIEy9ign2TxHu3QBa1cMlN/qLytetibBP1Sz
MWdlLLvQZ5iwcLth9Oz22jykOobuTrvDRkL0/+17g+CC5tB7JSnYLNx7HA2/6diF
TM0XB1MJIPUkzWEMC9wyLFR49suapdPaxpiU+wkWX7Q+rCSrKEvFz9Cih42qBFYe
YsrJ2bDtuSVU+I6eqe9LgmAX8KYr74Ua6LPgUKjp3UB5+A+fgFBUm+oZFwiWoy3c
6qFhxp4jmaA+V+lNvZbRcAmOilpxeu03W2J/++P6x6Hwj8tZ+m1yI3U/fRlLtN/A
RjCSDA5cbpUjqkc0/ay0uvHZlVaFVCXlfbLPiBq/foZWIy1qQah21kwMF+8bHQft
wg9rJSCZeyX9x+uO2QddSiE7GHlZpy9nxVXJqk9EF6Dzi51z8YWz0FNXMAs+S4Ma
+VShRWkJY1FsKpOCMmFe7dOftdQTXAvVOltpANyBF3CFhELN8PzkIpPGReLkolWO
0vIPvXyc+YP0YQd2HlVYNVibAqB5NHGn68i8dPD0lEmxHKswrK8NV/6Pjkr7aEhA
u3iCcG1IZyeWbLCBw3fyqe8B1WAneIIWzaPPYk4SRjKdavbwVS4MwjHDNBLnV+n2
2Um2Y5lCxnE=
=Jdg7
-----END PGP SIGNATURE-----

Attachment: pgpW5q2jcHVbE.pgp
Description: PGP signature


--- End Message ---
Reply to: