Your message dated Wed, 28 Feb 2024 23:50:52 +0000
with message-id <[email protected]>
and subject line Bug#1063156: fixed in myproxy 6.2.16-1.1
has caused the Debian Bug report #1063156,
regarding myproxy: 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.)


-- 
1063156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063156
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: myproxy
Version: 6.2.14-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: [email protected]
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
myproxy 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 myproxy
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-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: 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: unable to detect
diff -Nru myproxy-6.2.14/debian/changelog myproxy-6.2.14/debian/changelog
--- myproxy-6.2.14/debian/changelog     2022-07-05 20:53:00.000000000 +0000
+++ myproxy-6.2.14/debian/changelog     2024-02-05 13:29:21.000000000 +0000
@@ -1,3 +1,10 @@
+myproxy (6.2.14-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs <[email protected]>  Mon, 05 Feb 2024 13:29:21 +0000
+
 myproxy (6.2.14-2) unstable; urgency=medium
 
   * Drop old debug symbol migration from 2017
diff -Nru myproxy-6.2.14/debian/control myproxy-6.2.14/debian/control
--- myproxy-6.2.14/debian/control       2022-05-12 06:57:04.000000000 +0000
+++ myproxy-6.2.14/debian/control       2024-02-05 13:29:21.000000000 +0000
@@ -34,7 +34,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends:
- libmyproxy6 (= ${binary:Version}),
+ libmyproxy6t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Description: Credential Management Service Client
@@ -45,13 +45,14 @@
  Users run myproxy-logon to authenticate and obtain credentials, including
  trusted CA certificates and Certificate Revocation Lists (CRLs).
 
-Package: libmyproxy6
+Package: libmyproxy6t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: any
 Multi-Arch: same
-Replaces:
+Replaces:libmyproxy6, 
  libmyproxy-doc (<< 6.2.4-2~)
-Breaks:
+Breaks:libmyproxy6 (<< ${source:Version}), 
  libmyproxy-doc (<< 6.2.4-2~)
 Pre-Depends:
  ${misc:Pre-Depends}
@@ -76,7 +77,7 @@
 Pre-Depends:
  ${misc:Pre-Depends}
 Depends:
- libmyproxy6 (= ${binary:Version}),
+ libmyproxy6t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends},
  voms-clients | voms-clients-java
@@ -95,7 +96,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
- libmyproxy6 (= ${binary:Version}),
+ libmyproxy6t64 (= ${binary:Version}),
  libglobus-common-dev (>= 14),
  libglobus-gssapi-gsi-dev (>= 9),
  libglobus-gss-assist-dev (>= 8),
@@ -122,7 +123,7 @@
 Pre-Depends:
  ${misc:Pre-Depends}
 Depends:
- libmyproxy6 (= ${binary:Version}),
+ libmyproxy6t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends},
  adduser,
@@ -142,7 +143,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends:
- libmyproxy6 (= ${binary:Version}),
+ libmyproxy6t64 (= ${binary:Version}),
  myproxy-server (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends},
diff -Nru myproxy-6.2.14/debian/libmyproxy6.install 
myproxy-6.2.14/debian/libmyproxy6.install
--- myproxy-6.2.14/debian/libmyproxy6.install   2020-12-12 15:26:26.000000000 
+0000
+++ myproxy-6.2.14/debian/libmyproxy6.install   1970-01-01 00:00:00.000000000 
+0000
@@ -1,5 +0,0 @@
-/usr/lib/*/libmyproxy.so.*
-/usr/share/doc/myproxy/PROTOCOL
-/usr/share/doc/myproxy/README.sasl
-/usr/share/doc/myproxy/REPOSITORY
-/usr/share/doc/myproxy/VERSION
diff -Nru myproxy-6.2.14/debian/libmyproxy6.shlibs 
myproxy-6.2.14/debian/libmyproxy6.shlibs
--- myproxy-6.2.14/debian/libmyproxy6.shlibs    2018-03-02 17:17:37.000000000 
+0000
+++ myproxy-6.2.14/debian/libmyproxy6.shlibs    1970-01-01 00:00:00.000000000 
+0000
@@ -1 +0,0 @@
-libmyproxy 6 libmyproxy6 (>= 6)
diff -Nru myproxy-6.2.14/debian/libmyproxy6t64.install 
myproxy-6.2.14/debian/libmyproxy6t64.install
--- myproxy-6.2.14/debian/libmyproxy6t64.install        1970-01-01 
00:00:00.000000000 +0000
+++ myproxy-6.2.14/debian/libmyproxy6t64.install        2020-12-12 
15:26:26.000000000 +0000
@@ -0,0 +1,5 @@
+/usr/lib/*/libmyproxy.so.*
+/usr/share/doc/myproxy/PROTOCOL
+/usr/share/doc/myproxy/README.sasl
+/usr/share/doc/myproxy/REPOSITORY
+/usr/share/doc/myproxy/VERSION
diff -Nru myproxy-6.2.14/debian/libmyproxy6t64.lintian-overrides 
myproxy-6.2.14/debian/libmyproxy6t64.lintian-overrides
--- myproxy-6.2.14/debian/libmyproxy6t64.lintian-overrides      1970-01-01 
00:00:00.000000000 +0000
+++ myproxy-6.2.14/debian/libmyproxy6t64.lintian-overrides      2024-02-05 
13:29:21.000000000 +0000
@@ -0,0 +1 @@
+libmyproxy6t64: package-name-doesnt-match-sonames libmyproxy6
diff -Nru myproxy-6.2.14/debian/libmyproxy6t64.shlibs 
myproxy-6.2.14/debian/libmyproxy6t64.shlibs
--- myproxy-6.2.14/debian/libmyproxy6t64.shlibs 1970-01-01 00:00:00.000000000 
+0000
+++ myproxy-6.2.14/debian/libmyproxy6t64.shlibs 2024-02-05 13:29:21.000000000 
+0000
@@ -0,0 +1 @@
+libmyproxy 6 libmyproxy6t64 (>= 6)

--- End Message ---
--- Begin Message ---
Source: myproxy
Source-Version: 6.2.16-1.1
Done: Benjamin Drung <[email protected]>

We believe that the bug you reported is fixed in the latest version of
myproxy, 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.
Benjamin Drung <[email protected]> (supplier of updated myproxy 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 21:41:43 +0000
Source: myproxy
Architecture: source
Version: 6.2.16-1.1
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert <[email protected]>
Changed-By: Benjamin Drung <[email protected]>
Closes: 1063156
Changes:
 myproxy (6.2.16-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libraries for 64-bit time_t transition.  Closes: #1063156
Checksums-Sha1:
 47d08479176118a42d3abd942684cdd487df0b1d 2656 myproxy_6.2.16-1.1.dsc
 249c635d5aadf803e78fce6830dd48362a430cf1 9116 myproxy_6.2.16-1.1.debian.tar.xz
 06d6c36c8de4a91d4bc3dda8fc22b6f196812321 8375 
myproxy_6.2.16-1.1_source.buildinfo
Checksums-Sha256:
 3fc508a8b06e644f1735491ff38b06c7c3fd1d6d738196876df2169d2c4f6343 2656 
myproxy_6.2.16-1.1.dsc
 3f1eec62f8cc264da2280954c4e9dcc5b5a4bb6a948eaa08bbe61929a1286bcd 9116 
myproxy_6.2.16-1.1.debian.tar.xz
 671818f77cbefb33bc46be426ba2da97f293f8bafe6ca9925301cfb280b08c79 8375 
myproxy_6.2.16-1.1_source.buildinfo
Files:
 31ce23de319ad9ffd597ac623b14cc8a 2656 net optional myproxy_6.2.16-1.1.dsc
 3ef9bcd29dc4570b55e5f337cf0462a4 9116 net optional 
myproxy_6.2.16-1.1.debian.tar.xz
 12cc0a8578f6d3c98e1828b463e8db85 8375 net optional 
myproxy_6.2.16-1.1_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXfqKsACgkQFZ61xO/I
d0xLfBAAtfVkoIHQMHCw75ZR09RqGtDT38qLkjI4tQI4wJtVxKatDW5fVQW9Db7L
rLIg0F0NYq6DX3+whAL3IMO+lJGzG/tfmhUGE9274amjqPYci0ed4B63T+6J0NIU
Vp+RQP+0fjd74Cdj2fJl/LVHGyhfGYmThDVOh+Cwx5p5T8HMgiXZwNeKjWisXycG
lGjGccs3pYQjbok0kDV21Dr/Oil3v94obphoTVN2TBkEyPyI+D7aTlTG8usLyr9R
msWdnaECRjM7HhVQDPVYOw6nc8NiAlP3X3slQVMc5BSRTzXsEtcpuxSPFwm1K+9F
LBna8x7NJY3ro9PpZrjmUyU7vpH2Le+FfI4JCLiy3/IJhho550cFoVETVSbKcVlt
+x0F3AQ9uC0KD2vaXTbluwPc9RkceSVty8ctU/yznkASMoLOLrYQANJ/SG45YQ24
/TaTK86laxrkHdgIBxqOGaniKv1mWqgEXq8zMeTjNKzJfMj9jr4CkXDHhk8rQchT
6EOSPgc/ySHEOwS+xGlduCsjrKSaJmOkYb742ujdvTyB/j1d/BSgKuWcAtQDYtb5
CybcNQtIaSGdP6lRUiyrid7QqOzNqyA0lBWX4eAo+lg39m8JU10MZgvGZw5JWCfG
hDYC3qsQxjlBULeOB0ujqp5KDs9A0MJR6RdbVqWkfCVK/BxL5V4=
=XMxE
-----END PGP SIGNATURE-----

Attachment: pgp4F2mneqY4u.pgp
Description: PGP signature


--- End Message ---

Reply via email to