This is a multi-part MIME message sent by reportbug.


Source: libcdk5
Version: 5.0.20180306-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
libcdk5 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 libcdk5
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 libcdk5-5.0.20180306/debian/changelog libcdk5-5.0.20180306/debian/changelog
--- libcdk5-5.0.20180306/debian/changelog 2018-07-08 12:01:56.000000000 +0000
+++ libcdk5-5.0.20180306/debian/changelog 2024-01-31 20:15:03.000000000 +0000
@@ -1,3 +1,10 @@
+libcdk5 (5.0.20180306-3.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:15:03 +0000
+
libcdk5 (5.0.20180306-3) unstable; urgency=medium

* debian/tests/control:
diff -Nru libcdk5-5.0.20180306/debian/control libcdk5-5.0.20180306/debian/control
--- libcdk5-5.0.20180306/debian/control 2018-07-08 11:42:11.000000000 +0000
+++ libcdk5-5.0.20180306/debian/control 2024-01-31 20:15:03.000000000 +0000
@@ -8,12 +8,14 @@
Vcs-Git: https://salsa.debian.org/debian/libcdk5.git
Vcs-Browser: https://salsa.debian.org/debian/libcdk5

-Package: libcdk5nc6
+Package: libcdk5nc6t64
+Provides: ${t64:Provides}
+Breaks: libcdk5nc6 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Depends: ${misc:

On 2024-01-31 20:15 +0000, Steve Langasek wrote:

Source: libcdk5
Version: 5.0.20180306-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-arm@lists.debian.org
Usertags: time-t

Dear maintainer,

Not the maintainer here, I think he is rather inactive these days.

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
libcdk5 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 libcdk5
which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW.

As you likely have noticed, an upload to experimental was not possible
because a newer version is already there. What is the backup plan?

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.

This package already has an ABI tag from a previous transition[1], and I
think it would be better to replace it rather than add another one on
top of it, i.e. rename the library package to libcdk5t64 rather than libcdknc6t64. See the attached patch (against the original version in unstable), I have tested that it builds and that libcdk5t64 correctly
Provides: libcdk5nc6 (= 5.0.20180306-3.1).

diff -Nru libcdk5-5.0.20180306/debian/libcdk5nc6t64.lintian-overrides libcdk5-5.0.20180306/debian/libcdk5nc6t64.lintian-overrides
--- libcdk5-5.0.20180306/debian/libcdk5nc6t64.lintian-overrides 1970-01-01 00:00:00.000000000 +0000
+++ libcdk5-5.0.20180306/debian/libcdk5nc6t64.lintian-overrides 2024-01-31 20:15:03.000000000 +0000
@@ -0,0 +1,2 @@
+libcdk5nc6t64: package-name-doesnt-match-sonames libcdk5
+libcdk5nc6t64: package-name-doesnt-match-sonames libcdk5nc6

This adds another override rather than replacing the current one. My
patch fixes that as well.

Cheers,
Sven


1. https://bugs.debian.org/892280


diff -Nru libcdk5-5.0.20180306/debian/changelog libcdk5-5.0.20180306/debian/changelog
--- libcdk5-5.0.20180306/debian/changelog 2018-07-08 14:01:56.000000000 +0200
+++ libcdk5-5.0.20180306/debian/changelog 2024-01-31 21:15:03.000000000 +0100
@@ -1,3 +1,10 @@
+libcdk5 (5.0.20180306-3.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:15:03 +0000
+
libcdk5 (5.0.20180306-3) unstable; urgency=medium

* debian/tests/control:
diff -Nru libcdk5-5.0.20180306/debian/control libcdk5-5.0.20180306/debian/control
--- libcdk5-5.0.20180306/debian/control 2018-07-08 13:42:11.000000000 +0200
+++ libcdk5-5.0.20180306/debian/control 2024-01-31 21:15:03.000000000 +010
0
@@ -8,12 +8,15 @@
Vcs-Git: https://salsa.debian.org/debian/libcdk5.git
Vcs-Browser: https://salsa.debian.org/debian/libcdk5

-Package: libcdk5nc6
+Package: libcdk5t64
+Provides: ${t64:Provides}
+Breaks: libcdk5nc6 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Depends: ${misc:D

On Thu, Feb 01, 2024 at 07:54:08PM +0100, Sven Joachim wrote:

On 2024-01-31 20:15 +0000, Steve Langasek wrote:

Source: libcdk5
Version: 5.0.20180306-3

...

upstream is about 6 years newer.

As you likely have noticed, an upload to experimental was not possible because a newer version is already there. What is the backup plan?

...and that's still a few years out of date.

(aside from soname, no ABI changes that I recall - upgrading is recommended)

--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net

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

iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmW8ApAACgkQzCr0RyFn vgNi1wv+PyyuDp5iZhTFHyUNS1qHaN/Uw84DcyhF17KeuDzPw4I1OR+fiPNFSMhf mPcyClXQ++us++YxG00Be8iFRIayy1U/N/SkkA4N4/Nwsrlii/258M0q4cvQeG45 KsCwvxPJn4Hfj8tFjuCUwYQf4hhMpyJGA97BBiXEGo6PUKCd8hoLjBS3jayx+V6m 0ePbng09orVwbA9hNK1N7FyS3aHQc7TNIZUAQd4AS+UXjd7cjq3YytiYOoHvPhYn nN/Gxsio77kp91jNHu5h7xZvFEJBOfgHXm0S5wwoNdAWEadb9eSxUgiwnV2+271s 2GCBPjupQjbZmVJSmXvqiX9zHqgICYsqw8kbNBabS10xN/5vE9mVY2fscSCiijB8 Tav9yUi/0+tSyYreDfr7fwOkmIVupcZZMoGZ1SsWxhHxIEaom/RVzyk+mfKiKuKA E03NpB91MZ87CHI0BdW2/0015iQka13C3fBMibnM6Q5UmfCwJwyudyEvvFdieE9b
7pI8dZXl
=m9Wy
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Thu, 29 Feb 2024 16:38:16 +0000
with message-id <E1rfjQG-00C0AZ-QM@fasolo.debian.org>
and subject line Bug#1062246: fixed in libcdk5 5.0.20180306-3.1
has caused the Debian Bug report #1062246,
regarding libcdk5: 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.)


--
1062246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062246
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 31 Jan 2024 20:16:00 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-111.0 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FOURLA,FROMDEVELOPER,
FVGT_m_MULTI_ODD,HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_NONE,SPF_NONE,
T_SCC_BODY_TEXT_LINE,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 949; hammy, 150; neutral, 287; spammy,
0. spammytokens: hammytokens:0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O,
0.000-+--trixie, 0.000-+--langasek, 0.000-+--Langasek
Return-path: <vorlon@homer.dodds.net>
Received: from becquer.dodds.net ([207.224.24.209]:385