Your message dated Thu, 29 Feb 2024 19:43:24 +0000
with message-id <e1rfmjq-00cwvc...@fasolo.debian.org>
and subject line Bug#1063200: fixed in pagmo 2.19.0-3.1
has caused the Debian Bug report #1063200,
regarding pagmo: 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.)


-- 
1063200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pagmo
Version: 2.19.0-3
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
pagmo 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 pagmo
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.2.0-39-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, 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 pagmo-2.19.0/debian/changelog pagmo-2.19.0/debian/changelog
--- pagmo-2.19.0/debian/changelog       2023-10-25 11:49:17.000000000 -0300
+++ pagmo-2.19.0/debian/changelog       2024-02-05 13:53:24.000000000 -0300
@@ -1,3 +1,10 @@
+pagmo (2.19.0-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro <kanash...@debian.org>  Mon, 05 Feb 2024 13:53:24 -0300
+
 pagmo (2.19.0-3) unstable; urgency=medium
 
   * Fixing the clean target (Closes: #1048278)
diff -Nru pagmo-2.19.0/debian/control pagmo-2.19.0/debian/control
--- pagmo-2.19.0/debian/control 2023-06-23 05:25:35.000000000 -0300
+++ pagmo-2.19.0/debian/control 2024-02-05 13:53:24.000000000 -0300
@@ -16,7 +16,10 @@
 Vcs-Git: https://salsa.debian.org/science-team/pagmo.git
 Rules-Requires-Root: no
 
-Package: libpagmo9
+Package: libpagmo9t64
+Provides: ${t64:Provides}
+Replaces: libpagmo9
+Breaks: libpagmo9 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends},
@@ -33,7 +36,7 @@
 Section: libdevel
 Architecture: any
 Depends: ${misc:Depends},
-         libpagmo9 (= ${binary:Version}),
+         libpagmo9t64 (= ${binary:Version}),
          libeigen3-dev,
          libboost-serialization-dev,
          libtbb-dev
diff -Nru pagmo-2.19.0/debian/libpagmo9.install 
pagmo-2.19.0/debian/libpagmo9.install
--- pagmo-2.19.0/debian/libpagmo9.install       2023-02-01 18:39:07.000000000 
-0300
+++ pagmo-2.19.0/debian/libpagmo9.install       1969-12-31 21:00:00.000000000 
-0300
@@ -1 +0,0 @@
-usr/lib/*/libpagmo.so.*
diff -Nru pagmo-2.19.0/debian/libpagmo9.lintian-overrides 
pagmo-2.19.0/debian/libpagmo9.lintian-overrides
--- pagmo-2.19.0/debian/libpagmo9.lintian-overrides     2023-02-01 
18:39:07.000000000 -0300
+++ pagmo-2.19.0/debian/libpagmo9.lintian-overrides     1969-12-31 
21:00:00.000000000 -0300
@@ -1,2 +0,0 @@
-# We won't issue symbols files for this C++ library, using shlibs instead
-no-symbols-control-file usr/lib/*/libpagmo.so.*
diff -Nru pagmo-2.19.0/debian/libpagmo9t64.install 
pagmo-2.19.0/debian/libpagmo9t64.install
--- pagmo-2.19.0/debian/libpagmo9t64.install    1969-12-31 21:00:00.000000000 
-0300
+++ pagmo-2.19.0/debian/libpagmo9t64.install    2023-02-01 18:39:07.000000000 
-0300
@@ -0,0 +1 @@
+usr/lib/*/libpagmo.so.*
diff -Nru pagmo-2.19.0/debian/libpagmo9t64.lintian-overrides 
pagmo-2.19.0/debian/libpagmo9t64.lintian-overrides
--- pagmo-2.19.0/debian/libpagmo9t64.lintian-overrides  1969-12-31 
21:00:00.000000000 -0300
+++ pagmo-2.19.0/debian/libpagmo9t64.lintian-overrides  2024-02-05 
13:53:24.000000000 -0300
@@ -0,0 +1,3 @@
+# We won't issue symbols files for this C++ library, using shlibs instead
+no-symbols-control-file usr/lib/*/libpagmo.so.*
+libpagmo9t64: package-name-doesnt-match-sonames libpagmo9

--- End Message ---
--- Begin Message ---
Source: pagmo
Source-Version: 2.19.0-3.1
Done: Benjamin Drung <bdr...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pagmo, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung <bdr...@debian.org> (supplier of updated pagmo 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: Thu, 29 Feb 2024 19:16:42 +0000
Source: pagmo
Architecture: source
Version: 2.19.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Benjamin Drung <bdr...@debian.org>
Closes: 1063200
Changes:
 pagmo (2.19.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1063200
Checksums-Sha1:
 8e1b3db44ba2bd948be5871ce76f58f8dde59c2b 2132 pagmo_2.19.0-3.1.dsc
 a3adae9ec1fbab8636ffd206d5a3c4a16e26a377 5304 pagmo_2.19.0-3.1.debian.tar.xz
 b0808c7a7fc94130d9152dd31359044d20daf7fd 8482 pagmo_2.19.0-3.1_source.buildinfo
Checksums-Sha256:
 9f3c4707a6336eb92f81b8d52244a4aaef1a432850f23ede09e3896f096f9784 2132 
pagmo_2.19.0-3.1.dsc
 2a48367a44a8a99c3eb827ca372ed92e75b3665ade8b00e97661f12cde4e35a6 5304 
pagmo_2.19.0-3.1.debian.tar.xz
 c18de3cdd0c7d07048c318773c03cf24be7497be2d7cbfc2fd7c702ef026e58b 8482 
pagmo_2.19.0-3.1_source.buildinfo
Files:
 b8ef7d3340591fa198ecff4819c050ed 2132 science optional pagmo_2.19.0-3.1.dsc
 28a8f592df8cf4b3c9bf3beddf107ab3 5304 science optional 
pagmo_2.19.0-3.1.debian.tar.xz
 62a6202182501767d5437f58d5ff286c 8482 science optional 
pagmo_2.19.0-3.1_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXg2IYACgkQFZ61xO/I
d0wmZQ//QAoBzm941YfxkY1CGVB9U6mWx3n/rXYjQr0DdF8mVwOuzE1A50Ed+0uf
3wkGCjqYnwiGHqfZDF8fEH/01aeAlH1jF+F5XcVNZbdszzFWub6kS9EKu8XUMRgQ
OSkdxH5R2imJtMFlhedTcLao1mZGl+iqdlXIC3nHGLBXIpuuphv9Ps1jIYkNi8St
nNaRbY42kuq/+0G9SHScmH9RpDCiGvZLtNhb4taMyZ2cxzsM62SaMN8HZ0vOPMmq
b1FJTRRqxkfSjPbMZrzZbs4GwG94dsv8nBTvLTRx0ybTKPRnSIw1C8Teds0bWHDa
uK5mukT3CF8Ik3o5uLyMzBrTYqZ9ikP09j69fP8HNGDO1n4hhyNCUcj1IU/Brv9U
/wjoissJtUbJ9k1/6uFwJy9SzIP1yZyrW3h/YqcZ5LXvJyhegCX7BFAPqxRdQ/Wn
/7D9cOBtSvKM3XECACOK4rFWCf75hLJEiGhqZZogXPUWbQEk+G1zzniEoRZdLiKi
8FwSGHiJfcAuX80NIdVmQQSa7aU8NhZRP+7S4px4qHEspqDZlZkir4u19sNnYNPW
RopK0haRbUY8tqg4OFIUCmPrIkHMPNwv7ICh1kNTNYEvkIPg+GMLwdLyg8yZd1Ko
YwEWLBQ8lnyVKgKQFWTC2dsVT3QwmPYpoRSdgCMxIBRRBjvElVE=
=8oze
-----END PGP SIGNATURE-----

Attachment: pgpdsJJoKUs01.pgp
Description: PGP signature


--- End Message ---

Reply via email to