Re: Proposal: drop libcrypt-dev dependency from libc6-dev

[gregor herrmann]

On Thu, 10 Apr 2025 07:37:32 +0200, Helmut Grohne wrote:

I sorted those logs and
you may now find them at
https://people.debian.org/~helmutg/glibc-no-crypt/logs/.

Thanks.

Beyond that, 11
packages build a perl extension module for testing purposes and
therefore need "Build-Depends: perl-xs-dev <!nocheck>".

I learned something new :)

For the perl-related changes we
might skip filing the bugs and consider mass-committing the changes for
a later upload.

At first glance that sounds reasonable (and save us from the work of correlating and closing bugs in packages). At second glance, i.e. after looking at <https://people.debian.org/~helmutg/glibc-no-crypt/logs/needs-perl-xs-dev/>, I note that many packages there don't match the 'lib.+-perl' pattern, i.e. are not maintained by the Debian Perl Team, and from the remaining ones, (without checking them) I also don't recognize quite a few package names. ¹

Cheers,
gregor




--
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe

I think the "mass" for "mass-commiting" would not be high enough to rely on this mechanism, so I guess including them in the MBF makes more sense. ¹ I'm not surprised that this problem mainly affects non-team-maintained packages, as we've been using perl-xs-dev since quite some time … `-

signature.asc
Description: Digital Signature