Your message dated Wed, 28 Feb 2024 16:04:46 +0000
with message-id <[email protected]>
and subject line Bug#1062050: fixed in ceres-solver 2.2.0+dfsg-4.1
has caused the Debian Bug report #1062050,
regarding ceres-solver: 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 [email protected]
immediately.)
--
1062050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062050
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ceres-solver
Version: 2.2.0+dfsg-4
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: [email protected]
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
ceres-solver 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 ceres-solver
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'), (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 ceres-solver-2.2.0+dfsg/debian/changelog
ceres-solver-2.2.0+dfsg/debian/changelog
--- ceres-solver-2.2.0+dfsg/debian/changelog 2023-11-25 14:50:29.000000000
+0000
+++ ceres-solver-2.2.0+dfsg/debian/changelog 2024-01-31 08:07:21.000000000
+0000
@@ -1,3 +1,10 @@
+ceres-solver (2.2.0+dfsg-4.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <[email protected]> Wed, 31 Jan 2024 08:07:21 +0000
+
ceres-solver (2.2.0+dfsg-4) unstable; urgency=medium
* Dropping (build-)dependency on atlas, using blas instead (Closes: #1056666)
diff -Nru ceres-solver-2.2.0+dfsg/debian/control
ceres-solver-2.2.0+dfsg/debian/control
--- ceres-solver-2.2.0+dfsg/debian/control 2023-11-24 22:27:54.000000000
+0000
+++ ceres-solver-2.2.0+dfsg/debian/control 2024-01-31 08:07:21.000000000
+0000
@@ -31,7 +31,7 @@
Architecture: any
Multi-Arch: same
Section: libdevel
-Depends: libceres4 (= ${binary:Version}),
+Depends: libceres4t64 (= ${binary:Version}),
${misc:Depends},
libblas-dev,
libgoogle-glog-dev,
@@ -51,7 +51,10 @@
.
This package contains the development header files.
-Package: libceres4
+Package: libceres4t64
+Provides: ${t64:Provides}
+Replaces: libceres4
+Breaks: libceres4 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
diff -Nru ceres-solver-2.2.0+dfsg/debian/libceres4.install
ceres-solver-2.2.0+dfsg/debian/libceres4.install
--- ceres-solver-2.2.0+dfsg/debian/libceres4.install 2023-10-24
05:21:34.000000000 +0000
+++ ceres-solver-2.2.0+dfsg/debian/libceres4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru ceres-solver-2.2.0+dfsg/debian/libceres4.lintian-overrides
ceres-solver-2.2.0+dfsg/debian/libceres4.lintian-overrides
--- ceres-solver-2.2.0+dfsg/debian/libceres4.lintian-overrides 2023-10-24
05:22:05.000000000 +0000
+++ ceres-solver-2.2.0+dfsg/debian/libceres4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,2 +0,0 @@
-# We won't issue a symbols file for this C++ library, using shlibs instead.
-libceres4: no-symbols-control-file usr/lib/*/libceres.so.*
diff -Nru ceres-solver-2.2.0+dfsg/debian/libceres4t64.install
ceres-solver-2.2.0+dfsg/debian/libceres4t64.install
--- ceres-solver-2.2.0+dfsg/debian/libceres4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ ceres-solver-2.2.0+dfsg/debian/libceres4t64.install 2023-10-24
05:21:34.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru ceres-solver-2.2.0+dfsg/debian/libceres4t64.lintian-overrides
ceres-solver-2.2.0+dfsg/debian/libceres4t64.lintian-overrides
--- ceres-solver-2.2.0+dfsg/debian/libceres4t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ ceres-solver-2.2.0+dfsg/debian/libceres4t64.lintian-overrides
2024-01-31 08:07:21.000000000 +0000
@@ -0,0 +1,3 @@
+# We won't issue a symbols file for this C++ library, using shlibs instead.
+libceres4t64: no-symbols-control-file usr/lib/*/libceres.so.*
+libceres4t64: package-name-doesnt-match-sonames libceres4
--- End Message ---
--- Begin Message ---
Source: ceres-solver
Source-Version: 2.2.0+dfsg-4.1
Done: Steve Langasek <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ceres-solver, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve Langasek <[email protected]> (supplier of updated ceres-solver 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 Feb 2024 09:05:56 +0000
Source: ceres-solver
Architecture: source
Version: 2.2.0+dfsg-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
<[email protected]>
Changed-By: Steve Langasek <[email protected]>
Closes: 1062050
Changes:
ceres-solver (2.2.0+dfsg-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1062050
Checksums-Sha1:
1f641b66f2beb3d60e06cca75e85d7b0d2856e22 2570 ceres-solver_2.2.0+dfsg-4.1.dsc
c4e7181202d3c845f89dd109e2d71e22b0e7d310 10468
ceres-solver_2.2.0+dfsg-4.1.debian.tar.xz
7aec360c9e5794b5c53edb6de06f06a0b12cc60d 8585
ceres-solver_2.2.0+dfsg-4.1_source.buildinfo
Checksums-Sha256:
871e345e4712e634a67f91665894bc7cdd5b2d4949c4f04b259cfa2c79c60e43 2570
ceres-solver_2.2.0+dfsg-4.1.dsc
068e3e5d6c7c288e842cba208478604d4b222cbcf178758c15d27cf63851cbdf 10468
ceres-solver_2.2.0+dfsg-4.1.debian.tar.xz
11b2f0f10b300c503569aa103f00bd2947a0a4fa659256f531f107ed137c1750 8585
ceres-solver_2.2.0+dfsg-4.1_source.buildinfo
Files:
3697c78381b087d2e7c71a96b0354ad6 2570 math optional
ceres-solver_2.2.0+dfsg-4.1.dsc
c9082f367f407c1ed594b8406722da27 10468 math optional
ceres-solver_2.2.0+dfsg-4.1.debian.tar.xz
8e017758f07876d15e8c87e97c4372b0 8585 math optional
ceres-solver_2.2.0+dfsg-4.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXfUMUSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9SSQP/R81fMidHcwbk4PkwSGQD2m+eliUuIm1
fQVfUWOct4O87Nt/+Rmq3yfuQ8ZViqjvigG3tTYZXAF8VFA7Noch34zM83X/smm6
AfjbqXH1wnLWB46T+hxO3etF6c8Y0icTYgMK2WkRTcGtCpnnUEnv5yiZ2xMZU79j
mt8CPr6wzcS6W350VNa/IUhUm6ankaPUi+IWy4DQQPK5T5Lsdwk5dM/HvWwStB9g
8VoMFm+rUIK67mvHEzjh4BHc5ky08pbPNPQq/hYo8aiQ3+tOhfB6TnSY8ykxFHwt
NkE93B92krXBX3YW0Od8BOpWrARoVWY66mmPz/j8a96+p2vmHDy0EOndAlzgbub6
TfJ+fQHFICFMnW2civ4xDk3+7wf41pIuo1fWAinpFTb+zIoGM6BIzg25roxsCl8G
FQ+iJmkt2tGbaL7ZwGsCH12ysyPKfminywdS9i5BaAzkzrqf7hexwzsi+0ELsu2k
BLf3PJN/PEcKLP4zgRHqitvpI01TNp+hg1sP6dRi74GHgRedtNPn7jj8ERKN/460
NxsA7xMoptOyHVJ6xFFsEF/sNuI+eS7AO3mSsfYPwBtzC1PEu+KZP5uXgY7IT439
MgIiMc39QOLHseX8y3lh9qFPQ0genl6sK6QZ0ZboTyj6hlD0HNeBiDJ5v8a7HWst
CXJ06npyFPVZ
=7KhZ
-----END PGP SIGNATURE-----
pgpSDsefkYIum.pgp
Description: PGP signature
--- End Message ---
