Your message dated Thu, 21 Mar 2024 10:31:30 +0100
with message-id <20240321093130.36tezlpg4gefk...@notk.org>
and subject line No ABI change due to time_t
has caused the Debian Bug report #1062521,
regarding lcm: 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.)


-- 
1062521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lcm
Version: 1.3.1+repack1-7
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
lcm 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 lcm
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/8 CPU threads; PREEMPT)
Kernel taint flags: 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: unable to detect
diff -Nru lcm-1.3.1+repack1/debian/changelog lcm-1.3.1+repack1/debian/changelog
--- lcm-1.3.1+repack1/debian/changelog  2023-12-06 20:48:38.000000000 +0000
+++ lcm-1.3.1+repack1/debian/changelog  2024-02-01 18:25:16.000000000 +0000
@@ -1,3 +1,10 @@
+lcm (1.3.1+repack1-7.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs <gin...@debian.org>  Thu, 01 Feb 2024 18:25:16 +0000
+
 lcm (1.3.1+repack1-7) unstable; urgency=medium
 
   * QA upload.
diff -Nru lcm-1.3.1+repack1/debian/control lcm-1.3.1+repack1/debian/control
--- lcm-1.3.1+repack1/debian/control    2023-12-06 00:27:57.000000000 +0000
+++ lcm-1.3.1+repack1/debian/control    2024-02-01 18:25:16.000000000 +0000
@@ -12,7 +12,10 @@
 Vcs-Browser: https://salsa.debian.org/debian/lcm
 Rules-Requires-Root: no
 
-Package: liblcm1
+Package: liblcm1t64
+Provides: ${t64:Provides}
+Replaces: liblcm1
+Breaks: liblcm1 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Lightweight Communications and Marshalling
@@ -26,7 +29,7 @@
 
 Package: liblcm-dev
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
          liblcm-bin
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
@@ -39,7 +42,7 @@
 
 Package: liblcm-bin
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
  targeted at real-time systems where high-bandwidth and low latency are
@@ -51,7 +54,7 @@
 
 Package: liblcm-java
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
          liblcm-bin
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
diff -Nru lcm-1.3.1+repack1/debian/liblcm1.install 
lcm-1.3.1+repack1/debian/liblcm1.install
--- lcm-1.3.1+repack1/debian/liblcm1.install    2023-12-06 00:27:57.000000000 
+0000
+++ lcm-1.3.1+repack1/debian/liblcm1.install    1970-01-01 00:00:00.000000000 
+0000
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru lcm-1.3.1+repack1/debian/liblcm1t64.install 
lcm-1.3.1+repack1/debian/liblcm1t64.install
--- lcm-1.3.1+repack1/debian/liblcm1t64.install 1970-01-01 00:00:00.000000000 
+0000
+++ lcm-1.3.1+repack1/debian/liblcm1t64.install 2023-12-06 00:27:57.000000000 
+0000
@@ -0,0 +1 @@
+usr/lib/*/*.so.*
diff -Nru lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides 
lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides
--- lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides       1970-01-01 
00:00:00.000000000 +0000
+++ lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides       2024-02-01 
18:25:16.000000000 +0000
@@ -0,0 +1 @@
+liblcm1t64: package-name-doesnt-match-sonames liblcm1

--- End Message ---
--- Begin Message ---
I was able to have the analysis running for this package and no ABI
impact was found. As such, there is no need to transition the package
libraries for t64.

--- End Message ---

Reply via email to