Bug#1062696: libverto: NMU diff for 64-bit time_t transition
An overlooked hard-coded dependency in debian/control has made libverto
uninstallable. Please find the debdiff for an updated NMU attached.
On Fri, Feb 02, 2024 at 06:18:40PM +, Steve Langasek wrote:
> Source: libverto
> Version: 0.3.1-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
> libverto 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 libverto
> 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'), (500, 'stable'), (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 libverto-0.3.1/debian/changelog libverto-0.3.1/debian/changelog
> --- libverto-0.3.1/debian/changelog 2020-06-08 13:37:48.0 +
> +++ libverto-0.3.1/debian/changelog 2024-02-02 18:18:10.0 +
> @@ -1,3 +1,10 @@
> +libverto (0.3.1-1.1) experimental; urgency=medium
> +
> + * Non-maintainer upload.
> + * Rename libraries for 64-bit time_t transition.
> +
> + -- Steve Langasek Fri, 02 Feb 2024 18:18:10 +
> +
> libverto (0.3.1-1) unstable; urgency=medium
>
>[ Debian Janitor ]
> diff -Nru libverto-0.3.1/debian/control libverto-0.3.1/debian/control
> --- libverto-0.3.1/debian/control 2020-06-08 13:34:34.0 +
> +++ libverto-0.3.1/debian/control 2024-02-02 18:18:10.0 +
> @@ -12,7 +12,7 @@
> Package: libverto-dev
> Section: libdevel
> Architecture: any
> -Depends: ${misc:Depends}, libverto1 (= ${binary:Version}), libverto-glib1 (=
> ${binary:Version}), libverto-libev1 (= ${binary:Version})
> +Depends: ${misc:Depends}, libverto1t64 (= ${binary:Version}),
> libverto-glib1t64 (= ${binary:Version}), libverto-libev1t64 (=
> ${binary:Version})
> Description: Event loop abstraction for Libraries - Development
> Libverto exists to isolate libraries from the particular event loop
> chosen by an application. Libverto provides an asynchronous
> @@ -22,7 +22,10 @@
> .
> This package includes development libraries.
>
> -Package: libverto1
> +Package: libverto1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto1
> +Breaks: libverto1 (<< ${source:Version})
> Section: libs
> Architecture: any
> PRe-Depends: ${misc:Pre-Depends}
> @@ -37,7 +40,10 @@
> .
> This package includes the main runtime library.
>
> -Package: libverto-libev1
> +Package: libverto-libev1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto-libev1
> +Breaks: libverto-libev1 (<< ${source:Version})
> Section: libs
> Architecture: any
> PRe-Depends: ${misc:Pre-Depends}
> @@ -52,7 +58,10 @@
> .
> This package includes support for the libev event loop.
>
> -Package: libverto-glib1
> +Package: libverto-glib1t64
> +Provides: ${t64:Provides}
> +Replaces: libverto-glib1
> +Breaks: libverto-glib1 (<< ${source:Version})
> Section: libs
> Architecture: any
> PRe-Depends: ${misc:Pre-Depends}
> diff -Nru libverto-0.3.1/debian/libverto-glib1.install
> libverto-0.3.1/debian/libverto-glib1.install
> --- libverto-0.3.1/debian/libverto-glib1.install 2014-05-29
> 00:36:01.0 +
> +++ libverto-0.3.1/debian
Bug#1062696: libverto: NMU diff for 64-bit time_t transition
Source: libverto
Version: 0.3.1-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
libverto 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 libverto
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'), (500, 'stable'), (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 libverto-0.3.1/debian/changelog libverto-0.3.1/debian/changelog
--- libverto-0.3.1/debian/changelog 2020-06-08 13:37:48.0 +
+++ libverto-0.3.1/debian/changelog 2024-02-02 18:18:10.0 +
@@ -1,3 +1,10 @@
+libverto (0.3.1-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Fri, 02 Feb 2024 18:18:10 +
+
libverto (0.3.1-1) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru libverto-0.3.1/debian/control libverto-0.3.1/debian/control
--- libverto-0.3.1/debian/control 2020-06-08 13:34:34.0 +
+++ libverto-0.3.1/debian/control 2024-02-02 18:18:10.0 +
@@ -12,7 +12,7 @@
Package: libverto-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends}, libverto1 (= ${binary:Version}), libverto-glib1 (=
${binary:Version}), libverto-libev1 (= ${binary:Version})
+Depends: ${misc:Depends}, libverto1t64 (= ${binary:Version}),
libverto-glib1t64 (= ${binary:Version}), libverto-libev1t64 (=
${binary:Version})
Description: Event loop abstraction for Libraries - Development
Libverto exists to isolate libraries from the particular event loop
chosen by an application. Libverto provides an asynchronous
@@ -22,7 +22,10 @@
.
This package includes development libraries.
-Package: libverto1
+Package: libverto1t64
+Provides: ${t64:Provides}
+Replaces: libverto1
+Breaks: libverto1 (<< ${source:Version})
Section: libs
Architecture: any
PRe-Depends: ${misc:Pre-Depends}
@@ -37,7 +40,10 @@
.
This package includes the main runtime library.
-Package: libverto-libev1
+Package: libverto-libev1t64
+Provides: ${t64:Provides}
+Replaces: libverto-libev1
+Breaks: libverto-libev1 (<< ${source:Version})
Section: libs
Architecture: any
PRe-Depends: ${misc:Pre-Depends}
@@ -52,7 +58,10 @@
.
This package includes support for the libev event loop.
-Package: libverto-glib1
+Package: libverto-glib1t64
+Provides: ${t64:Provides}
+Replaces: libverto-glib1
+Breaks: libverto-glib1 (<< ${source:Version})
Section: libs
Architecture: any
PRe-Depends: ${misc:Pre-Depends}
diff -Nru libverto-0.3.1/debian/libverto-glib1.install
libverto-0.3.1/debian/libverto-glib1.install
--- libverto-0.3.1/debian/libverto-glib1.install2014-05-29
00:36:01.0 +
+++ libverto-0.3.1/debian/libverto-glib1.install1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libverto-glib.so.*
diff -Nru libverto-0.3.1/debian/libverto-glib1t64.install
libverto-0.3.1/debian/libverto-glib1t64.install
--- libverto-0.3.1/debian/libverto-glib1t64.install 1970-01-01
00:00:00.0 +
+++ libverto-0.3.1/debian/libverto-glib1t64.install 2014-05-29
00:36:01.0 +
@@ -0,0 +1 @@
+usr/lib/*/libverto-glib.s
