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

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



Your message dated Wed, 28 Feb 2024 13:12:13 +0000
with message-id <E1rfJjJ-00669o-Pg@fasolo.debian.org>
and subject line Bug#1062370: fixed in libibtk 0.0.14-13.1
has caused the Debian Bug report #1062370,
regarding libibtk: 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.)


-- 
1062370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062370
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libibtk
Version: 0.0.14-13
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
libibtk 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 libibtk
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 libibtk-0.0.14/debian/changelog libibtk-0.0.14/debian/changelog
--- libibtk-0.0.14/debian/changelog	2023-09-14 13:05:55.000000000 +0000
+++ libibtk-0.0.14/debian/changelog	2024-02-01 07:29:53.000000000 +0000
@@ -1,3 +1,10 @@
+libibtk (0.0.14-13.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vorlon@debian.org>  Thu, 01 Feb 2024 07:29:53 +0000
+
 libibtk (0.0.14-13) unstable; urgency=medium
 
   * QA upload.
diff -Nru libibtk-0.0.14/debian/control libibtk-0.0.14/debian/control
--- libibtk-0.0.14/debian/control	2023-09-14 13:05:55.000000000 +0000
+++ libibtk-0.0.14/debian/control	2024-02-01 07:29:53.000000000 +0000
@@ -8,12 +8,15 @@
 Package: libibtk-dev
 Section: libdevel
 Architecture: any
-Depends: libibtk0, libc6-dev
+Depends: libibtk0t64, libc6-dev
 Description: Insomnia's Basic ToolKit: Development Libraries and Header Files
  IBTK is used by The General ATI TV and Overlay Software (GATOS) suite 
  for capturing video.
 
-Package: libibtk0
+Package: libibtk0t64
+Provides: ${t64:Provides}
+Replaces: libibtk0
+Breaks: libibtk0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends}
diff -Nru libibtk-0.0.14/debian/libibtk0.dirs libibtk-0.0.14/debian/libibtk0.dirs
--- libibtk-0.0.14/debian/libibtk0.dirs	2023-09-14 13:05:22.000000000 +0000
+++ libibtk-0.0.14/debian/libibtk0.dirs	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib
diff -Nru libibtk-0.0.14/debian/libibtk0.files libibtk-0.0.14/debian/libibtk0.files
--- libibtk-0.0.14/debian/libibtk0.files	2023-09-14 13:05:55.000000000 +0000
+++ libibtk-0.0.14/debian/libibtk0.files	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/libibtk.so.*
diff -Nru libibtk-0.0.14/debian/libibtk0t64.dirs libibtk-0.0.14/debian/libibtk0t64.dirs
--- libibtk-0.0.14/debian/libibtk0t64.dirs	1970-01-01 00:00:00.000000000 +0000
+++ libibtk-0.0.14/debian/libibtk0t64.dirs	2023-09-14 13:05:22.000000000 +0000
@@ -0,0 +1 @@
+usr/lib
diff -Nru libibtk-0.0.14/debian/libibtk0t64.files libibtk-0.0.14/debian/libibtk0t64.files
--- libibtk-0.0.14/debian/libibtk0t64.files	1970-01-01 00:00:00.000000000 +0000
+++ libibtk-0.0.14/debian/libibtk0t64.files	2023-09-14 13:05:55.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/libibtk.so.*
diff -Nru libibtk-0.0.14/debian/libibtk0t64.lintian-overrides libibtk-0.0.14/debian/libibtk0t64.lintian-overrides
--- libibtk-0.0.14/debian/libibtk0t64.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
+++ libibtk-0.0.14/debian/libibtk0t64.lintian-overrides	2024-02-01 07:29:53.000000000 +0000
@@ -0,0 +1 @@
+libibtk0t64: package-name-doesnt-match-sonames libibtk0

--- End Message ---
--- Begin Message ---
Source: libibtk
Source-Version: 0.0.14-13.1
Done: Benjamin Drung <bdrung@debian.org>

We believe that the bug you reported is fixed in the latest version of
libibtk, 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 1062370@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 libibtk 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 12:48:43 +0000
Source: libibtk
Architecture: source
Version: 0.0.14-13.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Benjamin Drung <bdrung@debian.org>
Closes: 1062370
Changes:
 libibtk (0.0.14-13.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1062370
Checksums-Sha1:
 1f8d0d8c5e96f1af43dfab29fa8b2f9aff288297 1805 libibtk_0.0.14-13.1.dsc
 b12a71f17f503920a34b65ff747b5ffee556d869 5808 libibtk_0.0.14-13.1.debian.tar.xz
 af71de0d0fae12faf445b8912c03e73ed340069d 6604 libibtk_0.0.14-13.1_source.buildinfo
Checksums-Sha256:
 97ff9c3301e1bf639ccec0cdb7647e032863d021bd17f09805c7e10711f24d13 1805 libibtk_0.0.14-13.1.dsc
 afa4b416ad5f2801a95fc6083f70962a349d046285bd0ad48cd85b0090ba40cc 5808 libibtk_0.0.14-13.1.debian.tar.xz
 f1f75f98fec26e17d78ebf85b402925db8bc78a6386cac2e6e43135c214d660a 6604 libibtk_0.0.14-13.1_source.buildinfo
Files:
 ae9a44eae54b0114a3cee1c71ab515a9 1805 libs optional libibtk_0.0.14-13.1.dsc
 64fa609f9bdf7d729071ed810d83f3f3 5808 libs optional libibtk_0.0.14-13.1.debian.tar.xz
 034e17d8b88cb65f8c3bb62b169718bf 6604 libs optional libibtk_0.0.14-13.1_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXfK7kACgkQFZ61xO/I
d0zbPw/9HIBE70UaYh9D8uMODwHG+DmotqOB6ozNH36rYBaX3OlJUHzdzTrpxNZd
ORniNAvhuFyDu2m9RaveyQDlBDdHYuDvke5HIVdv1EKzc82yH9QqdHjbvJ8f7rfZ
92/efjzVRl5c9OeWX90IsEdeok0PpBXUaA7G4lrlM2RYssdQTOn/bO4edyaC6X+q
DGUkBzvDG+cfpyl2FBqXlm7TLTt3+Pr9wiUcTTW+2rHQV3XLR7EsMKeZrGs/hENH
q+4I90h5QsSI7AtXTwRkneofjPaNaRZfSbOd+kWc7RqoicFiD1CCN6VjTNuTT/5J
7IahUarK5Ay4v0q7AY0zR94aiW+l6NQwC+KcYytY1E9Tl5ED2wuntiss5cFfA4Fd
Fk2mjuR4faeXhYJYgyr6c1Mg7EQJ+Ma5PsT8saPJLY570sNbrZObpL4MWPnQh6+P
Tga3i8zuqe8nNuWRJgby140TM2fB9NnjDzz6o56n/9a0a830Wi0fQan7XlH1uPb8
QSmjic2hQBnuoyqAE7esneuPWFEjRNjGy+8AtWYn/wwmRTmsOqqLEQs13Ha/Rlyj
YQ9KNKilWnrd8WE9hFhdwD7iFHDUKRM0laWZCvds8UwPb7rK2LYm5U2ASmUCGfCF
ltihB/mE6LZ//NGWMA90YB7qrpDjxF2gdHKWIbPeEo1ofa89BX0=
=wTPi
-----END PGP SIGNATURE-----

Attachment: pgpGnq2vNulQ0.pgp
Description: PGP signature


--- End Message ---

Reply to: