Your message dated Sun, 1 Jun 2025 07:20:39 +0200
with message-id <20250601052039.ga3393...@subdivi.de>
and subject line Re: Bug#1106918: steam-installer: add libcrypt-dev to
Build-Depends
has caused the Debian Bug report #1106918,
regarding steam-installer: 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.)
--
1106918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: steam-installer
Version: 1:1.0.0.82~ds-4
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 Simon,
On Sat, May 31, 2025 at 10:30:36PM +0100, Simon McVittie wrote:
> I think this might be a false positive for steam-installer: the dependency
> on libcrypt1 is hard-coded, because nothing in steam-installer actually
> depends on it. (Instead, it downloads proprietary binaries from Valve
> on-demand at runtime, some of which do require libcrypt, or at least *might*
> require it - it's not entirely obvious, because of libcrypt's status as
> formerly part of glibc.)
Thanks for looking closer. Indeed, this is one of the packages where
only the "has a libcrypt1" signal applies.
> I think the best way to approach this would be to wait until there's a
> libc-dev in experimental that has dropped this dependency during the forky
> cycle, try rebuilding steam-installer against it and see what happens. If
> there is genuinely a problem then adding the B-D would be an easy change to
> make.
It did not show up as problematic in the archive rebuild. Thus closing.
Helmut
--- End Message ---
