Your message dated Thu, 29 Feb 2024 10:04:13 +0000
with message-id <e1rfdgv-00ahno...@fasolo.debian.org>
and subject line Bug#1062221: fixed in libapr-memcache 0.7.0-3.1
has caused the Debian Bug report #1062221,
regarding libapr-memcache: NMU diff for 64-bit time_t transition
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.)
--
1062221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapr-memcache
Version: 0.7.0-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
libapr-memcache as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for libapr-memcache
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libapr-memcache-0.7.0/debian/changelog
libapr-memcache-0.7.0/debian/changelog
--- libapr-memcache-0.7.0/debian/changelog 2014-02-23 09:52:03.000000000
+0000
+++ libapr-memcache-0.7.0/debian/changelog 2024-01-31 19:43:20.000000000
+0000
@@ -1,3 +1,10 @@
+libapr-memcache (0.7.0-3.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vor...@debian.org> Wed, 31 Jan 2024 19:43:20 +0000
+
libapr-memcache (0.7.0-3) unstable; urgency=low
* debian/rules removed unneeded export command from rules file
diff -Nru libapr-memcache-0.7.0/debian/control
libapr-memcache-0.7.0/debian/control
--- libapr-memcache-0.7.0/debian/control 2014-02-23 09:52:03.000000000
+0000
+++ libapr-memcache-0.7.0/debian/control 2024-01-31 19:43:20.000000000
+0000
@@ -9,7 +9,10 @@
Vcs-Browser:
http://anonscm.debian.org/gitweb/?p=collab-maint/libapr-memcache0.git;a=summary
-Package: libapr-memcache0
+Package: libapr-memcache0t64
+Provides: ${t64:Provides}
+Replaces: libapr-memcache0
+Breaks: libapr-memcache0 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
@@ -27,7 +30,7 @@
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, libapr-memcache0 (= ${binary:Version})
+Depends: ${misc:Depends}, libapr-memcache0t64 (= ${binary:Version})
Description: memcache client - development libraries
apr_memcache is a client written in C for memcached, the memory object
cache daemon. It uses the Apache Portable Runtime to provide pooled
diff -Nru libapr-memcache-0.7.0/debian/libapr-memcache0.install
libapr-memcache-0.7.0/debian/libapr-memcache0.install
--- libapr-memcache-0.7.0/debian/libapr-memcache0.install 2014-02-23
09:52:03.000000000 +0000
+++ libapr-memcache-0.7.0/debian/libapr-memcache0.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,2 +0,0 @@
-usr/lib/*/lib*.so.*
-
diff -Nru libapr-memcache-0.7.0/debian/libapr-memcache0t64.install
libapr-memcache-0.7.0/debian/libapr-memcache0t64.install
--- libapr-memcache-0.7.0/debian/libapr-memcache0t64.install 1970-01-01
00:00:00.000000000 +0000
+++ libapr-memcache-0.7.0/debian/libapr-memcache0t64.install 2014-02-23
09:52:03.000000000 +0000
@@ -0,0 +1,2 @@
+usr/lib/*/lib*.so.*
+
diff -Nru libapr-memcache-0.7.0/debian/libapr-memcache0t64.lintian-overrides
libapr-memcache-0.7.0/debian/libapr-memcache0t64.lintian-overrides
--- libapr-memcache-0.7.0/debian/libapr-memcache0t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ libapr-memcache-0.7.0/debian/libapr-memcache0t64.lintian-overrides
2024-01-31 19:43:20.000000000 +0000
@@ -0,0 +1 @@
+libapr-memcache0t64: package-name-doesnt-match-sonames libapr-memcache0
--- End Message ---
--- Begin Message ---
Source: libapr-memcache
Source-Version: 0.7.0-3.1
Done: Lukas Märdian <sl...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libapr-memcache, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lukas Märdian <sl...@debian.org> (supplier of updated libapr-memcache package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 29 Feb 2024 08:40:12 +0000
Source: libapr-memcache
Architecture: source
Version: 0.7.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Bastiaan Franciscus van den Dikkenberg <b...@dikkenberg.net>
Changed-By: Lukas Märdian <sl...@debian.org>
Closes: 1062221
Changes:
libapr-memcache (0.7.0-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1062221
Checksums-Sha1:
37a52607cf38f1e72bcfc3a3dd30d0aa1d2bc6e0 2152 libapr-memcache_0.7.0-3.1.dsc
fda70e094d3d132beadc32aef3b6e67ec0b37b0d 3928
libapr-memcache_0.7.0-3.1.debian.tar.xz
b7de26e52af68c75bcd908616ae28d119ae2f0b5 7332
libapr-memcache_0.7.0-3.1_source.buildinfo
Checksums-Sha256:
a1946df0e0f395a916fa5750c74cc5ff86f209f2bd3a0af332dcdc607bc25224 2152
libapr-memcache_0.7.0-3.1.dsc
7561c59a6bb57f53b0f187923272fc28b73cad6f53f5f3540f6445aeb68b314f 3928
libapr-memcache_0.7.0-3.1.debian.tar.xz
e55bb26e6871ccaee412c64268286acd9eff8e26965ccb8f9e85a63cb9ca358a 7332
libapr-memcache_0.7.0-3.1_source.buildinfo
Files:
a102d6c54e8f2910f0ad4fe755fb7699 2152 libs extra libapr-memcache_0.7.0-3.1.dsc
43413a46796a2fb286dd26565ed5d534 3928 libs extra
libapr-memcache_0.7.0-3.1.debian.tar.xz
86fd87932fd6de91270bc15d987600ea 7332 libs extra
libapr-memcache_0.7.0-3.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE496GmCL5m2y8NfJ5v322IrMDrIsFAmXgQwARHHNseW9uQGRl
Ymlhbi5vcmcACgkQv322IrMDrIspRRAAg8nBYTtXC7NYu/UnJC7tGGMlHq4N7bgX
PhsBgJ/bRBXf95eUBe7c4nF9/LYBMBuRa8c6NqIo6MYz5JQo1xTDUD+0dNtNZOiV
o5sKNg/rswP2vuZNvuB3YarNBdLy3MKcYx7xzLMsC8KeqEBrCvKAgxyOKDmDaVaF
1kxd2zC1He6MWmPyc11Iks2NpkH/1huAv5X7q0ieLdEG5F7TulIEuHbqupc4u+5o
SLMT+znI4pSVSsZs6t0IbWVWxzC5v8ypu0tPqGks87fCqvXQYhTrgjb4qGqD0dM8
MPKR36z83PQSa4sFANU32pObfiUq0mn02E7RRSHcsXa7hxpFScDPrYa0nFCBasuH
XNo2IhifBJiDP11K5tcN8iZpUmE27eXPweVFJYW2HHOiF2dUfoU7Q2sF9aBYOs6l
gxkxloOCG2lrsPwJJaU9/G7zEdggdIL9hJsFVseZGhZqD7Cc8HXiC+Fk2ACA202y
SwVa+j+gRqagZx6i7ptFUD+TlirSszsIwNlDae/e66hzCHGwaZnDzV0NeGBrQIsi
rL5mnrAC/xRLd1nQH+/t/fxafQnkYo6O//G867dF4Ax4VxHSazSoFTocajCMH0gX
ZPgiVtjSunQwtgGM7lnZ6nja76S0m7hetXG38eHxeglQvdX8omPNr3pe2E2IJFoU
8ZnulLMOUD8=
=2tZJ
-----END PGP SIGNATURE-----
pgppKM13fgFFp.pgp
Description: PGP signature
--- End Message ---
