Your message dated Thu, 29 Feb 2024 09:32:15 +0000
with message-id <e1rfclz-00azrm...@fasolo.debian.org>
and subject line Bug#1063277: fixed in xmedcon 0.23.0-gtk3+dfsg-1.1
has caused the Debian Bug report #1063277,
regarding xmedcon: 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.)


-- 
1063277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmedcon
Version: 0.23.0-gtk3+dfsg-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
xmedcon 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 xmedcon
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 xmedcon-0.23.0-gtk3+dfsg/debian/changelog 
xmedcon-0.23.0-gtk3+dfsg/debian/changelog
--- xmedcon-0.23.0-gtk3+dfsg/debian/changelog   2023-02-05 18:35:32.000000000 
+0000
+++ xmedcon-0.23.0-gtk3+dfsg/debian/changelog   2024-02-06 00:12:40.000000000 
+0000
@@ -1,3 +1,11 @@
+xmedcon (0.23.0-gtk3+dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Bump build-dependency on d-shlibs for --t64 support.
+
+ -- Steve Langasek <vor...@debian.org>  Tue, 06 Feb 2024 00:12:40 +0000
+
 xmedcon (0.23.0-gtk3+dfsg-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru xmedcon-0.23.0-gtk3+dfsg/debian/control 
xmedcon-0.23.0-gtk3+dfsg/debian/control
--- xmedcon-0.23.0-gtk3+dfsg/debian/control     2023-02-05 18:35:32.000000000 
+0000
+++ xmedcon-0.23.0-gtk3+dfsg/debian/control     2024-02-06 00:12:40.000000000 
+0000
@@ -5,7 +5,7 @@
 Section: graphics
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
-               d-shlibs,
+               d-shlibs (>= 0.106),
                libgdk-pixbuf-2.0-dev,
                libgtk-3-dev,
                zlib1g-dev,
@@ -17,7 +17,10 @@
 Homepage: https://xmedcon.sourceforge.net/
 Rules-Requires-Root: no
 
-Package: libmdc3
+Package: libmdc3t64
+Provides: ${t64:Provides}
+Replaces: libmdc3
+Conflicts: libmdc3 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
@@ -36,7 +39,7 @@
 Package: libmdc-dev
 Architecture: any
 Section: libdevel
-Depends: libmdc3 (= ${binary:Version}),
+Depends: libmdc3t64 (= ${binary:Version}),
          ${misc:Depends}
 Provides: libmdc2-dev
 Description: Medical Image (DICOM, ECAT, ...) conversion tool (development)
diff -Nru xmedcon-0.23.0-gtk3+dfsg/debian/libmdc3t64.lintian-overrides 
xmedcon-0.23.0-gtk3+dfsg/debian/libmdc3t64.lintian-overrides
--- xmedcon-0.23.0-gtk3+dfsg/debian/libmdc3t64.lintian-overrides        
1970-01-01 00:00:00.000000000 +0000
+++ xmedcon-0.23.0-gtk3+dfsg/debian/libmdc3t64.lintian-overrides        
2024-02-06 00:12:40.000000000 +0000
@@ -0,0 +1 @@
+libmdc3t64: package-name-doesnt-match-sonames libmdc3
diff -Nru xmedcon-0.23.0-gtk3+dfsg/debian/rules 
xmedcon-0.23.0-gtk3+dfsg/debian/rules
--- xmedcon-0.23.0-gtk3+dfsg/debian/rules       2023-02-05 18:35:32.000000000 
+0000
+++ xmedcon-0.23.0-gtk3+dfsg/debian/rules       2024-02-06 00:12:40.000000000 
+0000
@@ -22,6 +22,7 @@
 override_dh_install:
        dh_install
        d-shlibmove --commit \
+                   --t64 \
                    --multiarch \
                    --devunversioned \
                    --exclude-la \

--- End Message ---
--- Begin Message ---
Source: xmedcon
Source-Version: 0.23.0-gtk3+dfsg-1.1
Done: Steve Langasek <vor...@debian.org>

We believe that the bug you reported is fixed in the latest version of
xmedcon, 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.
Steve Langasek <vor...@debian.org> (supplier of updated xmedcon 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 07:37:28 +0000
Source: xmedcon
Architecture: source
Version: 0.23.0-gtk3+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Steve Langasek <vor...@debian.org>
Closes: 1063277
Changes:
 xmedcon (0.23.0-gtk3+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1063277
Checksums-Sha1:
 6f283f726345001b6ff02c32b16d983b6593f99d 2328 xmedcon_0.23.0-gtk3+dfsg-1.1.dsc
 55910cac5f8408736b5a3cac33f9f5f0bbae8739 13148 
xmedcon_0.23.0-gtk3+dfsg-1.1.debian.tar.xz
 f70c97ec384fac24692697fb74b027788f3dee27 15683 
xmedcon_0.23.0-gtk3+dfsg-1.1_source.buildinfo
Checksums-Sha256:
 f23f12544d440761e43511f1cf7a5a27a22bfeead15445281d3c3f218d0661e1 2328 
xmedcon_0.23.0-gtk3+dfsg-1.1.dsc
 210f449fb15097fd3a731386d108f30ae6983c2c9b873f935759a0db3e0ca1d1 13148 
xmedcon_0.23.0-gtk3+dfsg-1.1.debian.tar.xz
 318111e5f51511133079a85871915d232d25cf5be18808c079b559c90ab49b45 15683 
xmedcon_0.23.0-gtk3+dfsg-1.1_source.buildinfo
Files:
 fbc27a1c1e9cdc53b5b50886f91f8597 2328 graphics optional 
xmedcon_0.23.0-gtk3+dfsg-1.1.dsc
 bafec4bd356ebc8b43fb28d28db5e3b2 13148 graphics optional 
xmedcon_0.23.0-gtk3+dfsg-1.1.debian.tar.xz
 77134b008bc9cb8a1d32957d94d15d0f 15683 graphics optional 
xmedcon_0.23.0-gtk3+dfsg-1.1_source.buildinfo

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

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXgNGkSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM92CEP/RgT283+kKWkjURuUVKJJ41z5XiZ9nry
C3UOEdhBPCxQPUQ9Q6OGOJB5qcnIo10mF0wqI19b7kSxPdRgLPd5U4nF6Cwc/Qs3
KF6q/QWw6hpxCE4mVAECz1i0ETbLheHi8/L//LFORGCxN5qQsepQ/PgITXMKc3WZ
H0168u1PmuEdSqAg64U+wmP/qU59nOXtH4phdmanAituGW6F8t++U5d0JGhUNWlc
ACxKHCG1GhK5JH6cQ1ikxftMtBlYTkPEpeRcMnsgcS8lgssC0vBmWN4PUudeD6Cq
Gs8mkJ/WJDdiyfBNjzDnT0gUAXjQk8ZHG79Px2NQE+uyt4/2yXifWWDx0Fij30IF
SBYEGCmW1DwXA/XWaxcZ7QSgM25It3eCP1vUu9OOzOHTwhAS0tHWqFFg6PzcOy6C
URefT+gvsbU8QjyAOoh7dAr+VZE3yk079spy0O+mnuPsW8e+XSV5/9CVsKfNKBdu
W6l0Kq2GrABh7aElg5yS8chOOM3+61olTlOoEYeJWHSLO353Xf25du2nSoybem8O
BHjGm2AL5sPN324mhsMla/8U74USy3D4CXYpaiJUyccdEpJLJKxKaTlA4yznbTN5
E5FmrKhUVxBuH4kWxhDpzuWZgGe+ZU+5rzaTOhPr5K85lz4/bpg1iCMZy0FLbtgu
eSsQCd533nSO
=tgOh
-----END PGP SIGNATURE-----

Attachment: pgpfygLD_iO_x.pgp
Description: PGP signature


--- End Message ---

Reply via email to