Your message dated Thu, 29 Feb 2024 00:03:49 +0000
with message-id <[email protected]>
and subject line Bug#1063012: fixed in unicorn-engine 2.0.1.post1-4.1
has caused the Debian Bug report #1063012,
regarding unicorn-engine: 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 [email protected]
immediately.)
--
1063012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063012
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: unicorn-engine
Version: 2.0.1.post1-4
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: [email protected]
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
unicorn-engine 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 unicorn-engine
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 unicorn-engine-2.0.1.post1/debian/changelog
unicorn-engine-2.0.1.post1/debian/changelog
--- unicorn-engine-2.0.1.post1/debian/changelog 2023-08-15 16:04:35.000000000
+0000
+++ unicorn-engine-2.0.1.post1/debian/changelog 2024-02-04 12:02:14.000000000
+0000
@@ -1,3 +1,10 @@
+unicorn-engine (2.0.1.post1-4.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <[email protected]> Sun, 04 Feb 2024 12:02:14 +0000
+
unicorn-engine (2.0.1.post1-4) unstable; urgency=medium
* Fix build error with pybuild in dh_auto_clean
diff -Nru unicorn-engine-2.0.1.post1/debian/control
unicorn-engine-2.0.1.post1/debian/control
--- unicorn-engine-2.0.1.post1/debian/control 2023-08-15 15:58:16.000000000
+0000
+++ unicorn-engine-2.0.1.post1/debian/control 2024-02-04 12:02:14.000000000
+0000
@@ -30,7 +30,10 @@
instrumentation hooks for various CPU events. This makes Unicorn well
suited for malware analysis and reverse engineering.
-Package: libunicorn2
+Package: libunicorn2t64
+Provides: ${t64:Provides}
+Replaces: libunicorn2
+Breaks: libunicorn2 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Depends:
@@ -47,7 +50,7 @@
Multi-Arch: same
Depends:
${misc:Depends},
- libunicorn2 (= ${binary:Version}),
+ libunicorn2t64 (= ${binary:Version}),
Description: ${source:Synopsis} (development headers)
${source:Extended-Description}
.
@@ -59,7 +62,7 @@
Depends:
${misc:Depends},
${python3:Depends},
- libunicorn2 (>= ${source:Upstream-Version}),
+ libunicorn2t64 (>= ${source:Upstream-Version}),
Description: ${source:Synopsis} (Python 3 bindings)
${source:Extended-Description}
.
diff -Nru unicorn-engine-2.0.1.post1/debian/libunicorn2.install
unicorn-engine-2.0.1.post1/debian/libunicorn2.install
--- unicorn-engine-2.0.1.post1/debian/libunicorn2.install 2022-11-04
12:58:08.000000000 +0000
+++ unicorn-engine-2.0.1.post1/debian/libunicorn2.install 1970-01-01
00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru unicorn-engine-2.0.1.post1/debian/libunicorn2t64.install
unicorn-engine-2.0.1.post1/debian/libunicorn2t64.install
--- unicorn-engine-2.0.1.post1/debian/libunicorn2t64.install 1970-01-01
00:00:00.000000000 +0000
+++ unicorn-engine-2.0.1.post1/debian/libunicorn2t64.install 2022-11-04
12:58:08.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru unicorn-engine-2.0.1.post1/debian/libunicorn2t64.lintian-overrides
unicorn-engine-2.0.1.post1/debian/libunicorn2t64.lintian-overrides
--- unicorn-engine-2.0.1.post1/debian/libunicorn2t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ unicorn-engine-2.0.1.post1/debian/libunicorn2t64.lintian-overrides
2024-02-04 12:02:14.000000000 +0000
@@ -0,0 +1 @@
+libunicorn2t64: package-name-doesnt-match-sonames libunicorn2
--- End Message ---
--- Begin Message ---
Source: unicorn-engine
Source-Version: 2.0.1.post1-4.1
Done: Steve Langasek <[email protected]>
We believe that the bug you reported is fixed in the latest version of
unicorn-engine, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve Langasek <[email protected]> (supplier of updated unicorn-engine 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 Feb 2024 21:11:59 +0000
Source: unicorn-engine
Architecture: source
Version: 2.0.1.post1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Timo Röhling <[email protected]>
Changed-By: Steve Langasek <[email protected]>
Closes: 1063012
Changes:
unicorn-engine (2.0.1.post1-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1063012
Checksums-Sha1:
cda01248bcb1b9636e7c8f4d042045a6d6ac1572 2876
unicorn-engine_2.0.1.post1-4.1.dsc
270253f5e6998a30e55b27847e7ee6577536bc53 11236
unicorn-engine_2.0.1.post1-4.1.debian.tar.xz
6db65ce732227d02030bfd8f9aa81f805ec6fbdb 10647
unicorn-engine_2.0.1.post1-4.1_source.buildinfo
Checksums-Sha256:
94749a92ab688cdc64de66e8efa89642fb96b98c427dac39acd26c608e6faecd 2876
unicorn-engine_2.0.1.post1-4.1.dsc
612d1809c716eaae8c906271a0dd9a9f9cd26606280471bbcec12793bdea787f 11236
unicorn-engine_2.0.1.post1-4.1.debian.tar.xz
450a097d89fb0b715a678b2b33529081728539fab45a30135783cb4f96801a4e 10647
unicorn-engine_2.0.1.post1-4.1_source.buildinfo
Files:
80f713fee02c9521629e5009f7b98598 2876 libs optional
unicorn-engine_2.0.1.post1-4.1.dsc
c07dbc5f455e52e8df18ef0238416d76 11236 libs optional
unicorn-engine_2.0.1.post1-4.1.debian.tar.xz
bab171a81cb11bb8f59774a00faa76e7 10647 libs optional
unicorn-engine_2.0.1.post1-4.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXfovESHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9UnUP/iDRlVEn2HDsdgiyzucyYQI2WvcrCd5m
rHw4XmJ6hIZlEKSCFdY6pb9jTW1yGBoTU6rSY6zeepYxWX834SbF6jr+sQQjMaRb
pMgxRZMvOJsoM95+MKF680YRqh5okb8VrnuiRGDvJRoD01kD/PF7wQh5rno6wGPc
7uhvmRQ5JVW76WAtVz454UWfRO0ChAFjf1jUJdNO21lBENrQFxseXrTl1Uec1j74
MfZnFf4TnXM6bontme/DxyVPpCtI+NpCElHM8Sa8i1rwmJGavGoKzby8KnPGe6xX
s2w3RTI/W/kOLJ+ByXuNyx+EgICzECOV2wGklmVyGSftVDmm/a2Cc6sDqd1KNslT
OcBnspexqSK9U2TM/NNmK6lohMtZ24KlMLF9FPx4qLPnBcGdic/OfhCI+wr5sXO5
Kb7Ag7nptu/h8bLnGF03LPAk8cITbd4k2tkAtnLaEgihCzuHlv74ZieARoboC/I/
R93W7lKoPRKDa9Fz+JJXTTsDD3CofPGPxjfQHl1xT511DPvlTlX+Y0P0jdUZjkuX
7hS6NFCakM5K9oc5xpbm9qj1AL0c7bYwyuMalR5XOzfhfIErtqJt5PruLhU6aSDO
cOBCcEuUecdJYpht8zC0klo5dKWMVz9k4YqEUOPEXTjt7pyREGkz/x0DBvcRXsxl
ek9jfzeGqqCO
=b6q0
-----END PGP SIGNATURE-----
pgphXE01SytbB.pgp
Description: PGP signature
--- End Message ---
