Your message dated Fri, 01 Mar 2024 07:52:43 +0000
with message-id <e1rfxhd-00f5gw...@fasolo.debian.org>
and subject line Bug#1062738: fixed in libyang2 2.1.30-2.1
has caused the Debian Bug report #1062738,
regarding libyang2: 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.)


-- 
1062738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libyang2
Version: 2.1.30-2
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
libyang2 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 libyang2
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)

--- End Message ---
--- Begin Message ---
Source: libyang2
Source-Version: 2.1.30-2.1
Done: Steve Langasek <vor...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libyang2, 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 libyang2 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 07:25:05 +0000
Source: libyang2
Architecture: source
Version: 2.1.30-2.1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý <ond...@debian.org>
Changed-By: Steve Langasek <vor...@debian.org>
Closes: 1062738
Changes:
 libyang2 (2.1.30-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1062738
Checksums-Sha1:
 148f07c83aee272dcff5ae34acb9e0487a07a6ea 2214 libyang2_2.1.30-2.1.dsc
 205060dc9db93746c854d44481b50341d370785e 12244 
libyang2_2.1.30-2.1.debian.tar.xz
 222af19e154807071fb8ca801e8502af8f09d747 7654 
libyang2_2.1.30-2.1_source.buildinfo
Checksums-Sha256:
 92e938da8df4905363f3137b7ddbf824ca54135aa59d75fd4b09bc1adbcaa8c3 2214 
libyang2_2.1.30-2.1.dsc
 38752215d55ffdcf95986d348ad7cae3814c2365925104162a7cff16cc56eb9e 12244 
libyang2_2.1.30-2.1.debian.tar.xz
 c49d0445d402faecfbaaeed8d9b20dc7cb810c6665e155a13f296172a2cbd4a8 7654 
libyang2_2.1.30-2.1_source.buildinfo
Files:
 49a165c2e4de69c574f6d0020452a84d 2214 libs optional libyang2_2.1.30-2.1.dsc
 b7a8471ba1696a64762e1ee3f7363b42 12244 libs optional 
libyang2_2.1.30-2.1.debian.tar.xz
 f1d3e15489b2c7be765a2a433a21d3ca 7654 libs optional 
libyang2_2.1.30-2.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXhgv0SHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9WSwP+wSeZKMD6+CIulTOZcpB3er8rSCf/ww/
RO4fUSgdTehwm5JeOersmyhZ8JHliNUuVnYjaBESxXZl5dbWiYOimtbE+CdN5sRP
gXQ6ec5EBpjJds7dF0lo4/lvUzrFFfERZZMfjCO/v/+XEPu5FZqA2qELejehsK1J
0AtTb3a/NHyyXXjlsnQhLk/vU/O3cglj44xaAr1ShyIUoP5/C2hWjymqbLIeJ/7A
tZmUhEu21WHHzkOqClaJYlA1AWUGA2+e48VaCGbUx8FV6OfMqyEQGPaXrbun7A9j
2YbUBAEhTDgdx69fcnv3g69rpGlIU+XgF9d4F3BkFIGcRxb1GHgC3NN0COBQOXbp
SrcrR21awW8nk68jG6awUzU98WrdisJOBaC7m+Hq00iqxt22eo04oDDuikpneVfz
5sje4xDD88hWrw3WtFvtGiVMZsmZQgSMpivUQP4m4e7+Z0X/SjWsO4yK74UxZ504
EZNeAgPyEe6MshvVWXhpKCFyeNKPwrJTcN2rXdEFQBbqrSHTYr7iQyXfwzEKvyIY
UmgXfqG9tQX1rtDxdrgADRw0twr9Ag8muVXUZ0VOs32vzy9BYef7brJeZmiOkc3U
aacFtd93/V0iXdZfLzkjiGUjsPNknql00XJbWUUf/nlPcbJFWVHVP8Vv7B/sclcm
uX0FPpJFnWR6
=aO7l
-----END PGP SIGNATURE-----

Attachment: pgppZFFmCkZFx.pgp
Description: PGP signature


--- End Message ---

Reply via email to