Your message dated Fri, 25 Apr 2025 06:48:29 +0000
with message-id <e1u8crn-003den...@fasolo.debian.org>
and subject line Bug#1095937: Removed package(s) from unstable
has caused the Debian Bug report #1102979,
regarding ruby3.1: depend on libcrypt-dev explicitly
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.)
--
1102979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby3.1
Version: 3.1.2-8.5
Tags: patch
User: helm...@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.
Helmut
diff -Nru ruby3.1-3.1.2/debian/changelog ruby3.1-3.1.2/debian/changelog
--- ruby3.1-3.1.2/debian/changelog 2025-01-10 15:56:56.000000000 +0100
+++ ruby3.1-3.1.2/debian/changelog 2025-04-13 14:58:40.000000000 +0200
@@ -1,3 +1,10 @@
+ruby3.1 (3.1.2-8.6) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Explicitly depend on libcrypt-dev. (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Sun, 13 Apr 2025 14:58:40 +0200
+
ruby3.1 (3.1.2-8.5) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ruby3.1-3.1.2/debian/control ruby3.1-3.1.2/debian/control
--- ruby3.1-3.1.2/debian/control 2024-08-26 15:00:57.000000000 +0200
+++ ruby3.1-3.1.2/debian/control 2025-04-13 14:58:32.000000000 +0200
@@ -10,6 +10,7 @@
debhelper-compat (= 13),
dpkg-dev (>= 1.22.6),
file,
+ libcrypt-dev,
libffi-dev,
libgdbm-compat-dev,
libgdbm-dev,
@@ -79,8 +80,10 @@
Package: ruby3.1-dev
Multi-Arch: same
Architecture: any
-Depends: libgmp-dev,
+Depends: libcrypt-dev,
+ libgmp-dev,
libruby3.1t64 (= ${binary:Version}),
+ zlib1g-dev,
${misc:Depends},
${shlibs:Depends}
Recommends: ruby3.1-doc
--- End Message ---
--- Begin Message ---
Version: 3.1.2-8.5+rm
Dear submitter,
as the package ruby3.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1095937
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
