Your message dated Fri, 01 Mar 2024 06:04:27 +0000
with message-id <e1rfw0r-00ems1...@fasolo.debian.org>
and subject line Bug#1062498: fixed in liboop 1.0.1-2.2
has caused the Debian Bug report #1062498,
regarding liboop: 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.)
--
1062498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liboop
Version: 1.0.1-2.1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@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
liboop 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 liboop
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 liboop-1.0.1/debian/changelog liboop-1.0.1/debian/changelog
--- liboop-1.0.1/debian/changelog 2021-01-02 15:48:15.000000000 +0000
+++ liboop-1.0.1/debian/changelog 2024-02-01 17:26:54.000000000 +0000
@@ -1,3 +1,10 @@
+liboop (1.0.1-2.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vor...@debian.org> Thu, 01 Feb 2024 17:26:54 +0000
+
liboop (1.0.1-2.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru liboop-1.0.1/debian/control liboop-1.0.1/debian/control
--- liboop-1.0.1/debian/control 2018-09-30 20:09:14.000000000 +0000
+++ liboop-1.0.1/debian/control 2024-02-01 17:26:53.000000000 +0000
@@ -8,13 +8,14 @@
Standards-Version: 3.9.8
Homepage: http://www.lysator.liu.se/liboop/
-Package: liboop4
+Package: liboop4t64
+Breaks: liboop4 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
-Provides: liboop
-Replaces: liboop3
+Provides: ${t64:Provides}, liboop
+Replaces: liboop4, liboop3
Description: Event loop management library
Liboop is a low-level event loop management library for POSIX-based
operating systems. It supports the development of modular, multiplexed
@@ -28,7 +29,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: liboop4 (= ${binary:Version}), ${misc:Depends}
+Depends: liboop4t64 (= ${binary:Version}), ${misc:Depends}
Description: Event loop management library - development files
Liboop is a low-level event loop management library for POSIX-based
operating systems. It supports the development of modular, multiplexed
diff -Nru liboop-1.0.1/debian/liboop4.install
liboop-1.0.1/debian/liboop4.install
--- liboop-1.0.1/debian/liboop4.install 2018-09-30 20:09:14.000000000 +0000
+++ liboop-1.0.1/debian/liboop4.install 1970-01-01 00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/liboop*.so.*
diff -Nru liboop-1.0.1/debian/liboop4.symbols
liboop-1.0.1/debian/liboop4.symbols
--- liboop-1.0.1/debian/liboop4.symbols 2017-01-11 19:03:35.000000000 +0000
+++ liboop-1.0.1/debian/liboop4.symbols 1970-01-01 00:00:00.000000000 +0000
@@ -1,49 +0,0 @@
-liboop-adns.so.3 liboop4 #MINVER#
- oop_adns_cancel@Base 1.0~
- oop_adns_delete@Base 1.0~
- oop_adns_new@Base 1.0~
- oop_adns_submit@Base 1.0~
- oop_adns_submit_reverse@Base 1.0~
-liboop-glib2.so.0 liboop4 #MINVER#
- oop_glib_delete@Base 1.0~
- oop_glib_new@Base 1.0~
- oop_glib_return@Base 1.0~
-liboop-rl.so.0 liboop4 #MINVER#
- oop_readline_cancel@Base 1.0~
- oop_readline_register@Base 1.0~
-liboop-tcl.so.0 liboop4 #MINVER#
- oop_tcl_done@Base 1.0~
- oop_tcl_new@Base 1.0~
-liboop.so.4 liboop4 #MINVER#
- OOP_RD_STYLE_BLOCK@Base 1.0~
- OOP_RD_STYLE_GETLINE@Base 1.0~
- OOP_RD_STYLE_IMMED@Base 1.0~
- _oop_continue@Base 1.0~
- _oop_error@Base 1.0~
- oop_fd_nonblock@Base 1.0~
- oop_free@Base 1.0~
- oop_malloc@Base 1.0~
- oop_rd_cancel@Base 1.0~
- oop_rd_delete@Base 1.0~
- oop_rd_delete_kill@Base 1.0~
- oop_rd_delete_tidy@Base 1.0~
- oop_rd_errmsg@Base 1.0~
- oop_rd_new@Base 1.0~
- oop_rd_new_fd@Base 1.0~
- oop_rd_read@Base 1.0~
- oop_readable_fd@Base 1.0~
- oop_readable_mem@Base 1.0~
- oop_realloc@Base 1.0~
- oop_select_delete@Base 1.0~
- oop_select_new@Base 1.0~
- oop_select_set@Base 1.0~
- oop_signal_delete@Base 1.0~
- oop_signal_new@Base 1.0~
- oop_signal_new_flags@Base 1.0.1~
- oop_signal_source@Base 1.0~
- oop_sys_delete@Base 1.0~
- oop_sys_new@Base 1.0~
- oop_sys_run@Base 1.0~
- oop_sys_run_once@Base 1.0~
- oop_sys_source@Base 1.0~
- sys_sig_owner@Base 1.0~
diff -Nru liboop-1.0.1/debian/liboop4t64.install
liboop-1.0.1/debian/liboop4t64.install
--- liboop-1.0.1/debian/liboop4t64.install 1970-01-01 00:00:00.000000000
+0000
+++ liboop-1.0.1/debian/liboop4t64.install 2018-09-30 20:09:14.000000000
+0000
@@ -0,0 +1 @@
+usr/lib/*/liboop*.so.*
diff -Nru liboop-1.0.1/debian/liboop4t64.lintian-overrides
liboop-1.0.1/debian/liboop4t64.lintian-overrides
--- liboop-1.0.1/debian/liboop4t64.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
+++ liboop-1.0.1/debian/liboop4t64.lintian-overrides 2024-02-01
17:26:53.000000000 +0000
@@ -0,0 +1 @@
+liboop4t64: package-name-doesnt-match-sonames liboop4
diff -Nru liboop-1.0.1/debian/liboop4t64.symbols
liboop-1.0.1/debian/liboop4t64.symbols
--- liboop-1.0.1/debian/liboop4t64.symbols 1970-01-01 00:00:00.000000000
+0000
+++ liboop-1.0.1/debian/liboop4t64.symbols 2024-02-01 17:26:53.000000000
+0000
@@ -0,0 +1,49 @@
+liboop-adns.so.3 liboop4t64 #MINVER#
+ oop_adns_cancel@Base 1.0~
+ oop_adns_delete@Base 1.0~
+ oop_adns_new@Base 1.0~
+ oop_adns_submit@Base 1.0~
+ oop_adns_submit_reverse@Base 1.0~
+liboop-glib2.so.0 liboop4 #MINVER#
+ oop_glib_delete@Base 1.0~
+ oop_glib_new@Base 1.0~
+ oop_glib_return@Base 1.0~
+liboop-rl.so.0 liboop4 #MINVER#
+ oop_readline_cancel@Base 1.0~
+ oop_readline_register@Base 1.0~
+liboop-tcl.so.0 liboop4 #MINVER#
+ oop_tcl_done@Base 1.0~
+ oop_tcl_new@Base 1.0~
+liboop.so.4 liboop4 #MINVER#
+ OOP_RD_STYLE_BLOCK@Base 1.0~
+ OOP_RD_STYLE_GETLINE@Base 1.0~
+ OOP_RD_STYLE_IMMED@Base 1.0~
+ _oop_continue@Base 1.0~
+ _oop_error@Base 1.0~
+ oop_fd_nonblock@Base 1.0~
+ oop_free@Base 1.0~
+ oop_malloc@Base 1.0~
+ oop_rd_cancel@Base 1.0~
+ oop_rd_delete@Base 1.0~
+ oop_rd_delete_kill@Base 1.0~
+ oop_rd_delete_tidy@Base 1.0~
+ oop_rd_errmsg@Base 1.0~
+ oop_rd_new@Base 1.0~
+ oop_rd_new_fd@Base 1.0~
+ oop_rd_read@Base 1.0~
+ oop_readable_fd@Base 1.0~
+ oop_readable_mem@Base 1.0~
+ oop_realloc@Base 1.0~
+ oop_select_delete@Base 1.0~
+ oop_select_new@Base 1.0~
+ oop_select_set@Base 1.0~
+ oop_signal_delete@Base 1.0~
+ oop_signal_new@Base 1.0~
+ oop_signal_new_flags@Base 1.0.1~
+ oop_signal_source@Base 1.0~
+ oop_sys_delete@Base 1.0~
+ oop_sys_new@Base 1.0~
+ oop_sys_run@Base 1.0~
+ oop_sys_run_once@Base 1.0~
+ oop_sys_source@Base 1.0~
+ sys_sig_owner@Base 1.0~
--- End Message ---
--- Begin Message ---
Source: liboop
Source-Version: 1.0.1-2.2
Done: Steve Langasek <vor...@debian.org>
We believe that the bug you reported is fixed in the latest version of
liboop, 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 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve Langasek <vor...@debian.org> (supplier of updated liboop 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 05:38:17 +0000
Source: liboop
Architecture: source
Version: 1.0.1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Magnus Holmgren <holmg...@debian.org>
Changed-By: Steve Langasek <vor...@debian.org>
Closes: 1062498
Changes:
liboop (1.0.1-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1062498
Checksums-Sha1:
28c94a3067aa4f7e9daa22ae3bc04e0f50fff62a 2213 liboop_1.0.1-2.2.dsc
5e160ed32be1f917aac46629373ec7adc3869bc4 9812 liboop_1.0.1-2.2.debian.tar.xz
751f943b63bf59945ad022ff429633bbed68d974 7957 liboop_1.0.1-2.2_source.buildinfo
Checksums-Sha256:
382314f57c4249acba65423cc081735de508fc46ac5ce483db07e1f2bd24f461 2213
liboop_1.0.1-2.2.dsc
3dfab9bd59fbf785bb26e7361bd97d499da1ddad29d7758c42a78bedc2afda03 9812
liboop_1.0.1-2.2.debian.tar.xz
fc9cd8da9723f4afa530786d77767ddf66a4f7238961ec82ef04062dd9ac0e24 7957
liboop_1.0.1-2.2_source.buildinfo
Files:
af6dee878c0b7e1d59228d21fb4e562c 2213 libs optional liboop_1.0.1-2.2.dsc
d33f5767286225ddc9fc931bd42bf0d8 9812 libs optional
liboop_1.0.1-2.2.debian.tar.xz
f2777f03bd33f4aecdea0fbfa0eb993f 7957 libs optional
liboop_1.0.1-2.2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXhad4SHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9Bo0QAJJDKpmgA9TYSmk+DjkcyM7RwAGsjALX
6hhhPPsnPjn9kpl10aS5t2fJEFLTxxKX66znzZcXVc0C/yGS7No5s+TterYlcB/7
er6LfSF3oo9R/XEm5TXUzVzcX4hkLJJGhkD5B1XLneWTSDIszjZRkI5XcvRvwIT7
QLs14a4d7Z7xI7NwLCi0WJLCTok7S4AllwPmcW9A6dgyPeUTVThO+zuNTP7Mo8KK
G7FdiXxlWCQLxPmQktFs40puL7PQhf+s1hmvoFByIK+WZGINAD+VRt5V4ZnNMeeu
1aLXigGa9SDDax78XQybXHZM621wPITMTaP+Cob199DFvDYxajZuWqEFzlMi23BK
Y5zva5AM86WVg425ojH5qBHr45ON3E4idPsJmDS78nC5cmEXZJqPIDGPZz0CfkKl
AoxEOA3yBDGD+we8boZ9VBT6DV0qu1eI/bmiFF3MvUX62ohMcZAIYtzQAmhFCdh9
QoKXY3Z2cE5BzxH0ZKJEl/Qak4/WVwX7PMFWFjYnK9enHXnza6G1HNyViaOidhrP
PNDx3eqy3sw4f9KVtoosnwMFOyuCPM0olkdxKS+wEVOzBW4PLJgakDUiCB1c24aE
vSz19DjR7xTJTjkXnf/U3QeYx2cJl+LF7p9y6tQIMapqkISCfqirl4h3DE1u/cUP
xlnKvj1hLhml
=a5tO
-----END PGP SIGNATURE-----
pgpvlQ60lki01.pgp
Description: PGP signature
--- End Message ---
