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

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

Your message dated Wed, 28 Feb 2024 12:25:41 +0000
with message-id <E1rfJ0H-005wVa-H6@fasolo.debian.org>
and subject line Bug#1062294: fixed in libfixbuf 2.4.1+ds-2.1
has caused the Debian Bug report #1062294,
regarding libfixbuf: 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.)


-- 
1062294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062294
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libfixbuf
Version: 2.4.1+ds-2
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
libfixbuf 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 libfixbuf
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 libfixbuf-2.4.1+ds/debian/changelog libfixbuf-2.4.1+ds/debian/changelog
--- libfixbuf-2.4.1+ds/debian/changelog	2022-11-02 22:26:09.000000000 +0000
+++ libfixbuf-2.4.1+ds/debian/changelog	2024-02-01 00:29:09.000000000 +0000
@@ -1,3 +1,10 @@
+libfixbuf (2.4.1+ds-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vorlon@debian.org>  Thu, 01 Feb 2024 00:29:09 +0000
+
 libfixbuf (2.4.1+ds-2) unstable; urgency=medium
 
   * QA upload.
diff -Nru libfixbuf-2.4.1+ds/debian/control libfixbuf-2.4.1+ds/debian/control
--- libfixbuf-2.4.1+ds/debian/control	2022-11-02 22:26:09.000000000 +0000
+++ libfixbuf-2.4.1+ds/debian/control	2024-02-01 00:29:09.000000000 +0000
@@ -29,7 +29,10 @@
  ipfixDump is a command line tool for printing the contents of an IPFIX
  file as text.
 
-Package: libfixbuf9
+Package: libfixbuf9t64
+Provides: ${t64:Provides}
+Replaces: libfixbuf9
+Breaks: libfixbuf9 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
@@ -47,7 +50,7 @@
 
 Package: libfixbuf-dev
 Architecture: any
-Depends: libfixbuf9 (= ${binary:Version}), ${misc:Depends}, libglib2.0-dev
+Depends: libfixbuf9t64 (= ${binary:Version}), ${misc:Depends}, libglib2.0-dev
 Breaks: libfixbuf3-dev (<< 2)
 Replaces: libfixbuf3-dev (<< 2)
 Multi-Arch: same
diff -Nru libfixbuf-2.4.1+ds/debian/libfixbuf9.install libfixbuf-2.4.1+ds/debian/libfixbuf9.install
--- libfixbuf-2.4.1+ds/debian/libfixbuf9.install	2022-11-02 22:26:09.000000000 +0000
+++ libfixbuf-2.4.1+ds/debian/libfixbuf9.install	1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/libfixbuf.so.9*
diff -Nru libfixbuf-2.4.1+ds/debian/libfixbuf9t64.install libfixbuf-2.4.1+ds/debian/libfixbuf9t64.install
--- libfixbuf-2.4.1+ds/debian/libfixbuf9t64.install	1970-01-01 00:00:00.000000000 +0000
+++ libfixbuf-2.4.1+ds/debian/libfixbuf9t64.install	2022-11-02 22:26:09.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/libfixbuf.so.9*
diff -Nru libfixbuf-2.4.1+ds/debian/libfixbuf9t64.lintian-overrides libfixbuf-2.4.1+ds/debian/libfixbuf9t64.lintian-overrides
--- libfixbuf-2.4.1+ds/debian/libfixbuf9t64.lintian-overrides	1970-01-01 00:00:00.000000000 +0000
+++ libfixbuf-2.4.1+ds/debian/libfixbuf9t64.lintian-overrides	2024-02-01 00:29:09.000000000 +0000
@@ -0,0 +1 @@
+libfixbuf9t64: package-name-doesnt-match-sonames libfixbuf9

--- End Message ---
--- Begin Message --- 
Source: libfixbuf
Source-Version: 2.4.1+ds-2.1
Done: Benjamin Drung <bdrung@debian.org>

We believe that the bug you reported is fixed in the latest version of
libfixbuf, 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 1062294@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 libfixbuf 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 11:57:18 +0000
Source: libfixbuf
Architecture: source
Version: 2.4.1+ds-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Benjamin Drung <bdrung@debian.org>
Closes: 1062294
Changes:
 libfixbuf (2.4.1+ds-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1062294
Checksums-Sha1:
 b7134ff0d168aabd4f391ca27cd8130f289f518c 2195 libfixbuf_2.4.1+ds-2.1.dsc
 ea807a996679841f80b961a40da3d292cfff4889 5192 libfixbuf_2.4.1+ds-2.1.debian.tar.xz
 cdeed45fe48cae79dfce9e025e04226e537a7507 7215 libfixbuf_2.4.1+ds-2.1_source.buildinfo
Checksums-Sha256:
 e131e9a9c72e0322a1204eaa4a89db11c02c7d759cc5567e66b3aab291b2c582 2195 libfixbuf_2.4.1+ds-2.1.dsc
 60d80e5783fb838003dfe521e48d52ef895507ddbfe6b70a4994c1e30c3eda0b 5192 libfixbuf_2.4.1+ds-2.1.debian.tar.xz
 40baf0083ec587ff76ef41d9600bd52e97913a2715a10309ad06f725f108bb53 7215 libfixbuf_2.4.1+ds-2.1_source.buildinfo
Files:
 3b5001d19f7437c427f568c6320af33a 2195 net optional libfixbuf_2.4.1+ds-2.1.dsc
 a47e84873fecb1091e718b11932e22f0 5192 net optional libfixbuf_2.4.1+ds-2.1.debian.tar.xz
 4dcecb46417c0f6b0c0354838e3c8849 7215 net optional libfixbuf_2.4.1+ds-2.1_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXfH60ACgkQFZ61xO/I
d0zuUw//SYmiCreM988XgkVIBwqDgZ7Vg1BV4P38/0DzERdBCY3Z25xXiMxxYaL5
PJ2LsNM6EcQUbCZAQfD9IsTQVwav3SuJOJmTJ3WD/XgLu/MrGPujLlknpZkTlw1p
VGNZiD5II3hnk1abHS8exqlHra1+FcHtEQe93hZwpdzaT+zzCK9CVIKzn6+r9G4q
x5RDga5FEGgprq15oSjQvdLEfDCCIVy3A5cNTBbp5CXYF2gKMp6NQozfn6FmeZ+r
G2yvaSbPKndSSn42d00EYFezJu/kfLZcejVDwFTr/u9ZaKczhbtXmICHnrUdRUe6
SB4H9qM5KqxilR9RWJqqt0yT9YYFsMtgmfFY/bRZQCVnjMaHnRHDrLk7g+cMseqU
/b87f/5mYhCObWvEjRVe3kh6cp1qHlugz9ub22CFRoO1GqeCD4waPejx/HxL5pYS
RDGhLZgMmO11vew+LQ9Lq9R/xLAYu7oI1GhARPbqmCKHFOBtii2BEh+WytjLqIAQ
X1WX4QlogrhbFTY1PDcPLVo7RMdR6vEv0H2eLZEQQV4SFus5kDBYB+YM+DHLLz6R
5q5/kt+nScneaCkn0b8OqF+UZOMteQY9UbdKkUXopFFF+U/ii3KZmUqsuWvXvzJq
YZI46xKvIWfhfUpS+Iv2WjXBJ2F/hkRRaeZZ5UO0r1eXFYQfoKg=
=/q4h
-----END PGP SIGNATURE-----

Attachment: pgpXiFwvQuC6Z.pgp
Description: PGP signature


--- End Message ---
Reply to: