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

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

Your message dated Thu, 29 Feb 2024 10:04:47 +0000
with message-id <E1rfdHT-00AhVJ-IB@fasolo.debian.org>
and subject line Bug#1062226: fixed in libast 0.7-9.1
has caused the Debian Bug report #1062226,
regarding libast: 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.)


-- 
1062226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062226
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libast
Version: 0.7-9
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
libast 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 libast
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 libast-0.7/debian/changelog libast-0.7/debian/changelog
--- libast-0.7/debian/changelog	2018-02-12 18:34:56.000000000 +0000
+++ libast-0.7/debian/changelog	2024-01-31 19:48:10.000000000 +0000
@@ -1,3 +1,10 @@
+libast (0.7-9.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vorlon@debian.org>  Wed, 31 Jan 2024 19:48:10 +0000
+
 libast (0.7-9) unstable; urgency=medium
 
   * QA upload.
diff -Nru libast-0.7/debian/control libast-0.7/debian/control
--- libast-0.7/debian/control	2017-07-19 21:52:07.000000000 +0000
+++ libast-0.7/debian/control	2024-01-31 19:48:10.000000000 +0000
@@ -6,12 +6,14 @@
 Standards-Version: 4.0.0
 Homepage: http://www.eterm.org/
 
-Package: libast2
+Package: libast2t64
+Provides: ${t64:Provides}
+Breaks: libast2 (<< ${source:Version})
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libast1
-Replaces: libast1
+Replaces: libast2, libast1
 Description: Library of Assorted Spiffy Things
  LibAST is the Library of Assorted Spiffy Things.  It contains many
  spiffy things, and it is a library.  Thus, the ever-so-creative name.
@@ -25,10 +27,10 @@
 Package: libast2-dev
 Architecture: any
 Section: libdevel
-Depends: ${misc:Depends}, libimlib2-dev, libc6-dev, libast2 (= ${binary:Version})
+Depends: ${misc:Depends}, libimlib2-dev, libc6-dev, libast2t64 (= ${binary:Version})
 Provides: libast1-dev, libast-dev
 Conflicts: libast1-dev, libast-dev
-Description: libast2 development files
+Description: libast2t64 development files
  Headers, static libraries and documentation for developing software
  that uses libast2.
  .
diff -Nru libast-0.7/debian/libast2.install libast-0.7/debian/libast2.install
--- libast-0.7/debian/libast2.install	2011-08-25 20:12:44.000000000 +0000
+++ libast-0.7/debian/libast2.install	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*/libast.so.*
diff -Nru libast-0.7/debian/libast2t64.install libast-0.7/debian/libast2t64.install
--- libast-0.7/debian/libast2t64.install	1970-01-01 00:00:00.000000000 +0000
+++ libast-0.7/debian/libast2t64.install	2011-08-25 20:12:44.000000000 +0000
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*/libast.so.*
diff -Nru libast-0.7/debian/libast2t64.lintian-overrides libast-0.7/debian/libast2t64.lintian-overrides
--- libast-0.7/debian/libast2t64.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
+++ libast-0.7/debian/libast2t64.lintian-overrides	2024-01-31 19:48:10.000000000 +0000
@@ -0,0 +1 @@
+libast2t64: package-name-doesnt-match-sonames libast2

--- End Message ---
--- Begin Message --- 
Source: libast
Source-Version: 0.7-9.1
Done: Lukas Märdian <slyon@debian.org>

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

Debian distribution maintenance software
pp.
Lukas Märdian <slyon@debian.org> (supplier of updated libast 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: Thu, 29 Feb 2024 08:44:16 +0000
Source: libast
Architecture: source
Version: 0.7-9.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Lukas Märdian <slyon@debian.org>
Closes: 1062226
Changes:
 libast (0.7-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1062226
Checksums-Sha1:
 5273b2e5e66a3d947589c4cd6c737e9407212f9d 1857 libast_0.7-9.1.dsc
 3d32b877bce632a9a6b99e7fddb812beb0dd28d9 4816 libast_0.7-9.1.debian.tar.xz
 2cbf67e6f087576eecedc5cc57eb6a71762e9081 11881 libast_0.7-9.1_source.buildinfo
Checksums-Sha256:
 ec813f925584f61d3ce6175985397003ecd57b2d33a21b50a49afd1165769695 1857 libast_0.7-9.1.dsc
 20d4e049d6295ceb30e0fc44a0876fd08c86e2b54964c2779560d7cbe4f313a1 4816 libast_0.7-9.1.debian.tar.xz
 ff56881747937911fb7f7fda21a5276e463231c4e01ac21e3f7f0065ead1e93d 11881 libast_0.7-9.1_source.buildinfo
Files:
 1d5bb12de5197a205ccecc99be94b4be 1857 libs optional libast_0.7-9.1.dsc
 71828b7d27f888cb9f991a78b17739bd 4816 libs optional libast_0.7-9.1.debian.tar.xz
 c4a0bdb4326a453d73af3ddd97056556 11881 libs optional libast_0.7-9.1_source.buildinfo

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

iQJFBAEBCgAvFiEE496GmCL5m2y8NfJ5v322IrMDrIsFAmXgRAsRHHNseW9uQGRl
Ymlhbi5vcmcACgkQv322IrMDrIs8whAApivMAC29LfVZanYPhxW4m3vNc5Ty5uFq
alUlrw73S5rkdPvZ9mH7RtM80n7j4/DkXVEBP9n26Yzlib1NZW11+CG/fB78PEI6
IP/qACur6zuuqgmttlxe/ossIf+xZvK81jH6GZyctx1djnD8HrLapTvLwcbdXF9W
FvS/zU+8H54p+qkt1GOhmfRFzMlID/9ojoG4VGyBGB1uzw/RZ6ZY4CRvQyTxmAM+
q36q+cAQDWhaLNKCbZDrCM4Y3TfSwmjAn1KQJVGvQp4vXBGq8ii4afsBTXG6lxwa
RiZh3IFUFRTbvMlnxQo5IaeGu2409xeT/AQJERgfu7yDyhBzkJQxeQtf9fnJjFXC
V/AfhWtJCIuZnPDU5xFXNDp3b8BnJbJmAz6lPjK2I3i3owmyY8ZF79OYWpfZK+G7
tnBWzQUDPj0gmjtJ56KbQXYDJop1tqWGaRpkQwpdtEEQ6QKm1eV3uf0HawHw0AHL
FfKIhsWDtdF2uIjQX/j0+aDcjUkEbHD/D41vytFtc9+J1WEohVn+qgG2uf3IVKJg
kYfZM3bw1POAOj005De0ECRydkmIMToIxlyo5hfzj1jCLtl31ukzP+H98T9C/GXE
f6+kG8S1RzlGylewMpUroCppfYIYZ1OzX3JiGqbmTh6a0gPqbuIlCGY3aK60CP3/
aG0O7WczGrM=
=XFKN
-----END PGP SIGNATURE-----

Attachment: pgpHZWs_Zqfh8.pgp
Description: PGP signature


--- End Message ---
Reply to: