Source: ruby3.3 Version: 3.3.8-1 Tags: patch User: [email protected] Usertags: libcrypt-pkgconf
ruby3.3 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.3 and reverse dependencies of ruby3.3-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. Helmut
diff -Nru ruby3.3-3.3.8/debian/changelog ruby3.3-3.3.8/debian/changelog --- ruby3.3-3.3.8/debian/changelog 2025-04-10 20:59:06.000000000 +0200 +++ ruby3.3-3.3.8/debian/changelog 2025-04-13 15:05:27.000000000 +0200 @@ -1,3 +1,10 @@ +ruby3.3 (3.3.8-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Explicitly depend on libcrypt-dev. (Closes: #-1) + + -- Helmut Grohne <[email protected]> Sun, 13 Apr 2025 15:05:27 +0200 + ruby3.3 (3.3.8-1) unstable; urgency=medium * New upstream release. diff -Nru ruby3.3-3.3.8/debian/control ruby3.3-3.3.8/debian/control --- ruby3.3-3.3.8/debian/control 2025-04-10 20:59:06.000000000 +0200 +++ ruby3.3-3.3.8/debian/control 2025-04-13 15:05:25.000000000 +0200 @@ -9,6 +9,7 @@ coreutils (>= 7.5), debhelper-compat (= 13), file, + libcrypt-dev, libffi-dev, libgdbm-compat-dev, libgdbm-dev, @@ -78,8 +79,10 @@ Package: ruby3.3-dev Multi-Arch: same Architecture: any -Depends: libgmp-dev, +Depends: libcrypt-dev, + libgmp-dev, libruby3.3 (= ${binary:Version}), + zlib1g-dev, ${misc:Depends}, ${shlibs:Depends} Recommends: ruby3.3-doc
