Your message dated Sat, 31 May 2025 22:11:30 +0200
with message-id <20250531201130.ga3113...@subdivi.de>
and subject line Re: Bug#1107007: tightvnc: add libcrypt-dev to Build-Depends
has caused the Debian Bug report #1107007,
regarding tightvnc: 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 ow...@bugs.debian.org
immediately.)
--
1107007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tightvnc
Version: 1:1.3.10-9
Severity: normal
User: helm...@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 ---
Hi Sven,
On Sat, May 31, 2025 at 09:57:11PM +0200, Sven Geuer wrote:
> No need to add this as the fix to bug #1102457 [1] will remove the
> dependency. As already mentioned there, I intend to deal with it with
> the start of the forky cycle.
Sorry for having filed a duplicate. Closing.
Helmut
--- End Message ---
