Your message dated Fri, 01 Mar 2024 12:36:52 +0000
with message-id <e1rg28c-00geb5...@fasolo.debian.org>
and subject line Bug#1063128: fixed in libfreefare 0.4.0-2.2
has caused the Debian Bug report #1063128,
regarding libfreefare: 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.)
--
1063128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfreefare
Version: 0.4.0-2.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
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
libfreefare 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 libfreefare
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')
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 libfreefare-0.4.0/debian/changelog libfreefare-0.4.0/debian/changelog
--- libfreefare-0.4.0/debian/changelog 2021-01-05 10:29:39.000000000 +0000
+++ libfreefare-0.4.0/debian/changelog 2024-02-05 07:54:32.000000000 +0000
@@ -1,3 +1,10 @@
+libfreefare (0.4.0-2.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vor...@debian.org> Mon, 05 Feb 2024 07:54:32 +0000
+
libfreefare (0.4.0-2.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru libfreefare-0.4.0/debian/control libfreefare-0.4.0/debian/control
--- libfreefare-0.4.0/debian/control 2013-12-26 04:31:31.000000000 +0000
+++ libfreefare-0.4.0/debian/control 2024-02-05 07:54:32.000000000 +0000
@@ -8,7 +8,10 @@
Vcs-Git: git://anonscm.debian.org/collab-maint/libnfc.git
Vcs-Browser:
http://anonscm.debian.org/gitweb/?p=collab-maint/libfreefare.git;a=summary
-Package: libfreefare0
+Package: libfreefare0t64
+Provides: ${t64:Provides}
+Replaces: libfreefare0
+Breaks: libfreefare0 (<< ${source:Version})
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -23,7 +26,7 @@
Package: libfreefare-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends}, libfreefare0 (= ${binary:Version}), libnfc-dev
+Depends: ${misc:Depends}, libfreefare0t64 (= ${binary:Version}), libnfc-dev
Suggests: libfreefare-doc
Multi-Arch: same
Description: MIFARE card manipulations library (development files)
@@ -35,7 +38,7 @@
Package: libfreefare-bin
Section: utils
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libfreefare0 (>=
${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libfreefare0t64 (>=
${binary:Version})
Description: MIFARE card manipulations binaries
The libfreefare project aims to provide a convenient API for MIFARE
card manipulations.
diff -Nru libfreefare-0.4.0/debian/libfreefare0.install
libfreefare-0.4.0/debian/libfreefare0.install
--- libfreefare-0.4.0/debian/libfreefare0.install 2013-12-24
23:04:54.000000000 +0000
+++ libfreefare-0.4.0/debian/libfreefare0.install 1970-01-01
00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/libfreefare.so.*
diff -Nru libfreefare-0.4.0/debian/libfreefare0t64.install
libfreefare-0.4.0/debian/libfreefare0t64.install
--- libfreefare-0.4.0/debian/libfreefare0t64.install 1970-01-01
00:00:00.000000000 +0000
+++ libfreefare-0.4.0/debian/libfreefare0t64.install 2013-12-24
23:04:54.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/libfreefare.so.*
diff -Nru libfreefare-0.4.0/debian/libfreefare0t64.lintian-overrides
libfreefare-0.4.0/debian/libfreefare0t64.lintian-overrides
--- libfreefare-0.4.0/debian/libfreefare0t64.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
+++ libfreefare-0.4.0/debian/libfreefare0t64.lintian-overrides 2024-02-05
07:54:32.000000000 +0000
@@ -0,0 +1 @@
+libfreefare0t64: package-name-doesnt-match-sonames libfreefare0
--- End Message ---
--- Begin Message ---
Source: libfreefare
Source-Version: 0.4.0-2.2
Done: Benjamin Drung <bdr...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libfreefare, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Benjamin Drung <bdr...@debian.org> (supplier of updated libfreefare 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2024 12:21:18 +0000
Source: libfreefare
Architecture: source
Version: 0.4.0-2.2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu <iwama...@debian.org>
Changed-By: Benjamin Drung <bdr...@debian.org>
Closes: 1063128
Changes:
libfreefare (0.4.0-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1063128
Checksums-Sha1:
86ecdbc6c8b7016cfacd900f6878c54258d52b12 2172 libfreefare_0.4.0-2.2.dsc
0247ab5292ef81d2bc43f6f30821d25306e0ed91 3924
libfreefare_0.4.0-2.2.debian.tar.xz
449257c1d36dc8641234954b076569ffbb38f07d 6451
libfreefare_0.4.0-2.2_source.buildinfo
Checksums-Sha256:
41a7bf0c50889eac53d3db06667b72b4a8f31597922a945979a6b16e77954eed 2172
libfreefare_0.4.0-2.2.dsc
05b7cf6e81e309622e206bde624e8ee2a31570d4ad850343ac50bdadfd165c5b 3924
libfreefare_0.4.0-2.2.debian.tar.xz
84e70ed2fa4cf5f641178929997111e6584c902ed3b10a7adcd51bd6715ecefa 6451
libfreefare_0.4.0-2.2_source.buildinfo
Files:
9c471a3c38c431a7e97f7af111a9d064 2172 libs extra libfreefare_0.4.0-2.2.dsc
7696f61f2e4a1fbfabb690841d5439e3 3924 libs extra
libfreefare_0.4.0-2.2.debian.tar.xz
d770a5454a0aea7744154ff96d50a418 6451 libs extra
libfreefare_0.4.0-2.2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXhyFMACgkQFZ61xO/I
d0xuaQ/9FR+Gecuny3UCuRkDH2jTDSHzWMRaLijKre9W35zRyq/Pm/HVyv99rjJw
B02WU1IXXE9H/z10LiM3gQFOyb771RuogFvt5C5jmQCLD6K3XozIwt0ix1+Pd2X4
344Ggue0IGMxtnhvnmXTG3V5syG2iqs1JqTolCdEZkr/E+4bbqNAOmGEX5AEUHPU
y5Z3ckbfeFYLGV98jvn2GsJUwbZqQ0y9m4zSKfLu8DG6S6wOBPUp2AonzejQU52D
DbyIHjlYzAzC8961hrW8MWdQMMphmsT9wSZgul2pu/ZZsGE0InhnTACRHXRZz46T
R0BeyRUAwzPKbMv8tzvyc6NkzcGwFA5E+UrMjsU7zS09d1+q1XEUoXEbfESzOxqv
OZwMjxyN0tKoT2GHLpBMDjvx05jfGG2dRw7pXauI+miN/HkGlT0v2wVhwQ8iJNN5
hYHKtqx3g6gJmTZkfIvNu7bKXYq/5LenZzumRfZJgZlNjxEv5dFwOAn6iUZAQVT/
txKeqrPCpatoWWJdpWM+gPOl5IWKn+qbuh5LqhIEgfiXpK2XHfWWAMnkMNo8oAv5
yYLjGObAeHw4Shl6smCgypLVhtE2dVNGTsP1YOXsFNa1F2BzJ/LYUthXvLUyFbYf
CPdKd2UC1CWq4zcPjR2lTcaWVp+6ncpLm+dY+1ru5iJdWNBnKLc=
=kpJQ
-----END PGP SIGNATURE-----
pgpyy6S1ptmlo.pgp
Description: PGP signature
--- End Message ---
