Bug#1062744: libzypp: NMU diff for 64-bit time_t transition

2024-02-29 Thread Steve Langasek
Sorry, for some reason a number of bugs failed to have their patches
attached.  Please find the debdiff from the experimental upload attached
now.

On Fri, Feb 02, 2024 at 11:01:04PM +, Steve Langasek wrote:
> Source: libzypp
> Version: 17.31.29-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
> libzypp 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 libzypp
> 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)
> 

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libzypp-17.31.31/debian/changelog libzypp-17.31.31/debian/changelog
--- libzypp-17.31.31/debian/changelog   2024-02-08 12:25:59.0 +
+++ libzypp-17.31.31/debian/changelog   2024-02-22 19:19:20.0 +
@@ -1,3 +1,10 @@
+libzypp (17.31.31-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Fri, 23 Feb 2024 
08:19:20 +1300
+
 libzypp (17.31.31-1) unstable; urgency=medium
 
   * Update upstream source from tag 'upstream/17.31.31'
diff -Nru libzypp-17.31.31/debian/control libzypp-17.31.31/debian/control
--- libzypp-17.31.31/debian/control 2024-02-08 12:25:57.0 +
+++ libzypp-17.31.31/debian/control 2024-02-22 19:19:20.0 +
@@ -45,7 +45,8 @@
 Vcs-Git: https://salsa.debian.org/pkg-rpm-team/libzypp.git
 Vcs-Browser: https://salsa.debian.org/pkg-rpm-team/libzypp
 
-Package: libzypp1722
+Package: libzypp1722t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Pre-Depends:
@@ -64,10 +65,10 @@
  lsof,
 Suggests:
  libzypp-doc (>= ${source:Version}),
-Breaks:
+Breaks:libzypp1722 (<< ${source:Version}), 
  libzypp (<< 17.22),
  zypper (<< 1.14),
-Replaces:
+Replaces:libzypp1722, 
  libzypp (<< 17.22),
 Description: openSUSE/SLES package management system (library)
  libzypp is the package management library that powers applications like
@@ -111,7 +112,7 @@
  libexpat-dev,
  libpopt-dev,
  libproxy-dev,
- libzypp1722 (= ${binary:Version}),
+ libzypp1722t64 (= ${binary:Version}),
 Description: openSUSE/SLES package management system library (development 
files)
  libzypp is the package management library that powers applications like
  YaST, zypper and the openSUSE/SLE implementation of PackageKit.
@@ -223,7 +224,7 @@
  ${misc:Depends},
  libjs-jquery,
 Suggests:
- libzypp1722,
+ libzypp1722t64,
  libzypp-dev,
 Description: openSUSE/SLES package management system library (documentation)
  libzypp is the package management library that powers applications like
diff -Nru libzypp-17.31.31/debian/libzypp1722.install 
libzypp-17.31.31/debian/libzypp1722.install
--- libzypp-17.31.31/debian/libzypp1722.install 

Bug#1062744: libzypp: NMU diff for 64-bit time_t transition

2024-02-07 Thread Luca Boccassi
Control: tags -1 -pending
Control: close -1

On Fri, 02 Feb 2024 23:01:04 + Steve Langasek 
wrote:
> Source: libzypp
> Version: 17.31.29-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
> libzypp 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 libzypp
> 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.

There are no mentions of 'time_t' in the public headers of this
library. The logs shows that it's a false positive, as the automated
tool simply wasn't able to build it:

https://adrien.dcln.fr/misc/armhf-time_t/2023-12-18/logs/libzypp-dev/base/log.txt

Closing as not applicable.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


Bug#1062744: libzypp: NMU diff for 64-bit time_t transition

2024-02-02 Thread Steve Langasek
Source: libzypp
Version: 17.31.29-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
libzypp 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 libzypp
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)