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

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

Your message dated Wed, 28 Feb 2024 11:08:49 +0000
with message-id <E1rfHnt-005gDK-9s@fasolo.debian.org>
and subject line Bug#1062253: fixed in libcm256cc 1.1.0-4.1
has caused the Debian Bug report #1062253,
regarding libcm256cc: 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.)


-- 
1062253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062253
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libcm256cc
Version: 1.1.0-4
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
libcm256cc 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 libcm256cc
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 libcm256cc-1.1.0/debian/changelog libcm256cc-1.1.0/debian/changelog
--- libcm256cc-1.1.0/debian/changelog	2023-07-21 04:20:22.000000000 +0000
+++ libcm256cc-1.1.0/debian/changelog	2024-01-31 20:20:39.000000000 +0000
@@ -1,3 +1,10 @@
+libcm256cc (1.1.0-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vorlon@debian.org>  Wed, 31 Jan 2024 20:20:39 +0000
+
 libcm256cc (1.1.0-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru libcm256cc-1.1.0/debian/control libcm256cc-1.1.0/debian/control
--- libcm256cc-1.1.0/debian/control	2023-07-21 04:20:22.000000000 +0000
+++ libcm256cc-1.1.0/debian/control	2024-01-31 20:20:39.000000000 +0000
@@ -13,7 +13,10 @@
 Vcs-Browser: https://salsa.debian.org/debian-hamradio-team/libcm256cc
 Vcs-Git: https://salsa.debian.org/debian-hamradio-team/libcm256cc.git
 
-Package: libcm256cc1
+Package: libcm256cc1t64
+Provides: ${t64:Provides}
+Replaces: libcm256cc1
+Breaks: libcm256cc1 (<< ${source:Version})
 Section: libs
 Architecture: amd64 arm64 armhf i386 hurd-i386 kfreebsd-amd64 kfreebsd-i386 x32
 Multi-Arch: same
@@ -29,7 +32,7 @@
 Architecture: amd64 arm64 armhf i386 hurd-i386 kfreebsd-amd64 kfreebsd-i386 x32
 Multi-Arch: same
 Depends:
- libcm256cc1 (= ${binary:Version}),
+ libcm256cc1t64 (= ${binary:Version}),
  ${misc:Depends},
 Description: Fast GF(256) Cauchy MDS Block Erasure Codec in C++ (headers)
  cm256cc is a simple library for erasure codes. From given data it generates
diff -Nru libcm256cc-1.1.0/debian/libcm256cc1.install libcm256cc-1.1.0/debian/libcm256cc1.install
--- libcm256cc-1.1.0/debian/libcm256cc1.install	2023-07-21 04:20:22.000000000 +0000
+++ libcm256cc-1.1.0/debian/libcm256cc1.install	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru libcm256cc-1.1.0/debian/libcm256cc1t64.install libcm256cc-1.1.0/debian/libcm256cc1t64.install
--- libcm256cc-1.1.0/debian/libcm256cc1t64.install	1970-01-01 00:00:00.000000000 +0000
+++ libcm256cc-1.1.0/debian/libcm256cc1t64.install	2023-07-21 04:20:22.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/*.so.*
diff -Nru libcm256cc-1.1.0/debian/libcm256cc1t64.lintian-overrides libcm256cc-1.1.0/debian/libcm256cc1t64.lintian-overrides
--- libcm256cc-1.1.0/debian/libcm256cc1t64.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
+++ libcm256cc-1.1.0/debian/libcm256cc1t64.lintian-overrides	2024-01-31 20:20:39.000000000 +0000
@@ -0,0 +1 @@
+libcm256cc1t64: package-name-doesnt-match-sonames libcm256cc1

--- End Message ---
--- Begin Message --- 
Source: libcm256cc
Source-Version: 1.1.0-4.1
Done: Benjamin Drung <bdrung@debian.org>

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

Debian distribution maintenance software
pp.
Benjamin Drung <bdrung@debian.org> (supplier of updated libcm256cc 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: SHA512

Format: 1.8
Date: Wed, 28 Feb 2024 10:28:49 +0000
Source: libcm256cc
Architecture: source
Version: 1.1.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Benjamin Drung <bdrung@debian.org>
Closes: 1062253
Changes:
 libcm256cc (1.1.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1062253
Checksums-Sha1:
 97bb5ee1e638c436778ec209fee0adb3c1705277 2245 libcm256cc_1.1.0-4.1.dsc
 8781f786dfb796473db28eae432a153c51b24268 3912 libcm256cc_1.1.0-4.1.debian.tar.xz
 6884a94216e8fcec2f43375409cda7f709bec39a 7011 libcm256cc_1.1.0-4.1_source.buildinfo
Checksums-Sha256:
 b9882324f5a51edec72a7fb9c2f1c39b88a9327f2cd95fd0549dceb85c164ef1 2245 libcm256cc_1.1.0-4.1.dsc
 3c7facc89ce402e511f234e2b071d268d1428d463d09a165f42d95e00e3538f0 3912 libcm256cc_1.1.0-4.1.debian.tar.xz
 7dae47476960ce9cac56dca7ad8f7d0c612fd248eeef7301f803394a9f840bb1 7011 libcm256cc_1.1.0-4.1_source.buildinfo
Files:
 673f33ac7847f1b66cebd28ab9339cad 2245 hamradio optional libcm256cc_1.1.0-4.1.dsc
 08026ec5ad8f8c3b9f02acb233d9c247 3912 hamradio optional libcm256cc_1.1.0-4.1.debian.tar.xz
 8deb0999e327ba3b4916e859f88a77b8 7011 hamradio optional libcm256cc_1.1.0-4.1_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXfCvAACgkQFZ61xO/I
d0xHuA//VqN/68lYkCXTc/U6+9F7kbpLPRyy8sMIoi2jqR6oaAg/c/sRHqAGGRQk
r1oogJLNXGA2wqSTSILXLqaF1vu+WPuL6qHsNN2qLcvfEy3AJEc81hQ+LtK+jJA0
APVy5Iz6N6oByfX1PbbN3y6RSQ+46xVprDIPW5yvoGWEJQWa7bzCt8lXFepQcvjR
V4XP3ZRpE9VLFYSt4hDQ5yOB0wKgufPNerMOjkp1yKdcf02DnmbmWWaFAOE/peHU
/PNc8hIrq66CJJt2kKwP4zFGm7cmJq/kYBf086Eudv3n8ZZ+VP8+QxcQNg9iKq8W
UZ5NcJSkuPL9xD+AKyGQsbqF6hcyzfZ1FDIHqNYZcXnQIt5zkgSdpTnGrDw1xSZG
xoYelFIfQn3difMHOnoaMSySgagIsjwLOCqg5TRWtFQJqy9mcXl8MCgqDkZepZB7
bx5kcx5KjqH4IJgKxSlJBSXEWe+Y782fPi5USDADYoG8QYX4Ac8GJ8cEkEmucHGa
55MQuoEWsbXY9whJlau7xvD6kbzo85uHPVy+JtEA14UZc9WcO/HrT2VMCS9RzSsU
2EKY7d/PR6W9iuqtq0KhFeetIklDhmZ+fHUpzW0VtPTFyYVDCCLq2m5OvX47cCPn
zTAOhiO7VmDaFLvN2DDMEucm/G8qx+AcWvUqXJjZJmK/CerY/Ds=
=xrDy
-----END PGP SIGNATURE-----

Attachment: pgpzl_1pX6TZT.pgp
Description: PGP signature


--- End Message ---
Reply to: