Source: plasma-workspace Version: 4:6.3.2-2 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
