[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1061994: marked as done (cvm: NMU diff for 64-bit time_t transition)



Your message dated Tue, 27 Feb 2024 23:50:07 +0000
with message-id <E1rf7D5-003OZr-0W@fasolo.debian.org>
and subject line Bug#1061994: fixed in cvm 0.97-3.1
has caused the Debian Bug report #1061994,
regarding cvm: 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 owner@bugs.debian.org
immediately.)


-- 
1061994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061994
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: cvm
Version: 0.97-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-arm@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
cvm 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 cvm
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cvm-0.97/debian/changelog cvm-0.97/debian/changelog
--- cvm-0.97/debian/changelog	2022-05-27 19:24:32.000000000 +0000
+++ cvm-0.97/debian/changelog	2024-01-30 19:15:06.000000000 +0000
@@ -1,3 +1,10 @@
+cvm (0.97-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle <mwhudson@debian.org>  Tue, 30 Jan 2024 19:15:06 +0000
+
 cvm (0.97-3) unstable; urgency=medium
 
   * QA upload.
diff -Nru cvm-0.97/debian/control cvm-0.97/debian/control
--- cvm-0.97/debian/control	2022-05-27 19:24:32.000000000 +0000
+++ cvm-0.97/debian/control	2024-01-30 19:15:06.000000000 +0000
@@ -75,7 +75,10 @@
  .
  This package includes cvm binaries to interact with PostgreSQL databases.
 
-Package: libcvm1
+Package: libcvm1t64
+Provides: ${t64:Provides}
+Replaces: libcvm1
+Breaks: libcvm1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -99,7 +102,7 @@
 Package: libcvm1-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, libcvm1 (= ${binary:Version})
+Depends: ${misc:Depends}, ${shlibs:Depends}, libcvm1t64 (= ${binary:Version})
 Provides: libcvm-dev, cvm-dev
 Conflicts: libcvm-dev, cvm-dev
 Recommends: cvm
@@ -117,4 +120,4 @@
  and is much simpler to implement on both sides than PAM and the authmod
  framework.
  .
- This package includes development files for compiling against libcvm1
+ This package includes development files for compiling against libcvm1t64
diff -Nru cvm-0.97/debian/libcvm1.install cvm-0.97/debian/libcvm1.install
--- cvm-0.97/debian/libcvm1.install	2022-05-27 19:24:32.000000000 +0000
+++ cvm-0.97/debian/libcvm1.install	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-/usr/lib/*.so.*
diff -Nru cvm-0.97/debian/libcvm1.lintian-overrides cvm-0.97/debian/libcvm1.lintian-overrides
--- cvm-0.97/debian/libcvm1.lintian-overrides	2022-05-27 19:24:32.000000000 +0000
+++ cvm-0.97/debian/libcvm1.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-libcvm1: package-name-doesnt-match-sonames *
diff -Nru cvm-0.97/debian/libcvm1t64.install cvm-0.97/debian/libcvm1t64.install
--- cvm-0.97/debian/libcvm1t64.install	1970-01-01 00:00:00.000000000 +0000
+++ cvm-0.97/debian/libcvm1t64.install	2022-05-27 19:24:32.000000000 +0000
@@ -0,0 +1 @@
+/usr/lib/*.so.*
diff -Nru cvm-0.97/debian/libcvm1t64.lintian-overrides cvm-0.97/debian/libcvm1t64.lintian-overrides
--- cvm-0.97/debian/libcvm1t64.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
+++ cvm-0.97/debian/libcvm1t64.lintian-overrides	2024-01-30 19:15:06.000000000 +0000
@@ -0,0 +1,2 @@
+libcvm1t64: package-name-doesnt-match-sonames *
+libcvm1t64: package-name-doesnt-match-sonames libcvm1

--- End Message ---
--- Begin Message ---
Source: cvm
Source-Version: 0.97-3.1
Done: Michael Hudson-Doyle <mwhudson@debian.org>

We believe that the bug you reported is fixed in the latest version of
cvm, 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 1061994@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Hudson-Doyle <mwhudson@debian.org> (supplier of updated cvm 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 27 Feb 2024 23:24:25 +0000
Source: cvm
Architecture: source
Version: 0.97-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Michael Hudson-Doyle <mwhudson@debian.org>
Closes: 1061994
Changes:
 cvm (0.97-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1061994
Checksums-Sha1:
 e8ffc9f05ff4854ca47f20105f4c2d03772dda4c 2124 cvm_0.97-3.1.dsc
 45a209e8bac315f4443432169f4eb6dd00d5ac05 15428 cvm_0.97-3.1.debian.tar.xz
 2e9f5a00d9c4853b25cdd69d632ef41e7bb6db24 7230 cvm_0.97-3.1_source.buildinfo
Checksums-Sha256:
 8c4b40e9ac057ad5e81bf15d751af3e5eaafa285a664e17c3fd4d384ee31476e 2124 cvm_0.97-3.1.dsc
 c0f79ec048d17a94889239caccfb7be5bd0d1c3d76b323674a5ef5a003ac4ab9 15428 cvm_0.97-3.1.debian.tar.xz
 a055cc8b80e9061d7d4cae04daec5d92c62c80995b0256531043d2c7124c3140 7230 cvm_0.97-3.1_source.buildinfo
Files:
 8a01241f7252971e05f9a0153c531f4a 2124 admin optional cvm_0.97-3.1.dsc
 56aa6c4db85e86e6eb9f43768fa0ef2b 15428 admin optional cvm_0.97-3.1.debian.tar.xz
 8fdd3de899b4b98fb0b60f61cf1cf2be 7230 admin optional cvm_0.97-3.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCAAyFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXebzkUHG13aHVkc29u
QGRlYmlhbi5vcmcACgkQEd9ClMyjmJNkCA/+PneWNUmHqlk3yQhKRpw0D1qtS4Cm
0MLzDcoX+dv41dF9iXU/so3cdU1Cgpn4CBGtd2q53PWGLZgbxlSgfg57Eo6J+3FJ
nM5NzN+zccFDBWMhZ004PoWevD3iCfZuETFt7UIJ6K13BttMDCtNUEDXJq2nCsM1
2PHEiSKcMkQXfbenJeHA0EM2xEbtdAtQkAqmcjgl80HotM5mxtz9XKu/kE8gna1D
efZ0jPlPSqHHyREfDbhr9if4s1NyF3gu3VgPdelmI+ag0O+E3nzr3fmbFidOAJqR
b8mQzv4P5iDv4nldlXrv2vtng+sL1dZzllsfI3UDt6lXQAuinOCa3EVjOeto/Fff
lQynYqmOwmI5/WMLfU1mNhPciKLBpsmSKyahVv5ukGM3Es92Kn1bBtSPx6I4JDzh
E8q6sCVm2TsbrC15xe+nYFSDu1xLFDTdsvexCS3c6OmKmX2mJTolPnUPu/OTpGbG
3owC8abkjNzM8/Kpu6vwl/eG8fDQKrmC9qaHR6C44wGdqU+pAXyK4bVkSVzEhfeL
bCWu1FZMhFssIFnds2kgBiex2twGlnZAXCgj16YjNLrn/sHARVK00nCoveGzgZg+
0v5JZkzibxNt82WYSLrHj6dV36J68eVOfSiMOOROeSOa8ToNydUpxwkBEWdTLzDb
dVBFLnpkjKKab9o=
=1J9J
-----END PGP SIGNATURE-----

Attachment: pgpYaX4xKYxT6.pgp
Description: PGP signature


--- End Message ---

Reply to: