[DRE-maint] Bug#1102979: ruby3.1: depend on libcrypt-dev explicitly

[Antonio Terceiro]

Control: tag -1 + wontfix

On Sun, Apr 13, 2025 at 03:04:17PM +0200, Helmut Grohne wrote:
> Source: ruby3.1
> Version: 3.1.2-8.5
> Tags: patch
> User: helmutg at debian.org
> Usertags: libcrypt-pkgconf
> 
> ruby3.1 uses libxcrypt during build, but it also exposes this header to 
> its downstreams by including -lcrypt in its pkgconf .pc.  There is an 
> effort[1] to drop libcrypt-dev from the build-essential package set. 
> This will not happen during the trixie freeze, but some months into the 
> forky cycle. Once dropped, ruby3.1 and reverse dependencies of 
> ruby3.1-dev will fail to build from source.  While looking into it, I 
> noticed that the .pc file also contains -lz without a matching 
> dependency. I'm attaching a patch to make these dependencies explicit. 
> It is safe for inclusion into trixie, but it does not warrant an upload 
> of its own at this time of the freeze.

Thanks for you patch. However we are fixing the last bits to be able to
remove ruby3.1 from unstable, so we are not planning a new upload.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20250416/65a8aa7b/attachment-0001.sig>