Your message dated Sat, 18 Nov 2023 13:36:06 +0000
with message-id <[email protected]>
and subject line Bug#1055939: fixed in libgpg-error 1.47-3
has caused the Debian Bug report #1055939,
regarding libgpg-error: move libgpg-error.so.* to /usr
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.)
--
1055939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055939
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgpg-error
Version: 1.47-2
Severity: normal
Tags: patch
User: [email protected]
Usertags: dep17m2
We want to finalize the /usr-merge transition by moving files from / to
/usr. Until recently, this was prohibited by the file move moratorium.
It has now been delegated to https://wiki.debian.org/UsrMerge and we
actually can move albeit carefully.
https://subdivi.de/~helmut/dep17.html is a template of possible problems
to check for and that's what I did.
A very relevant scenario is the 2038 transition
https://wiki.debian.org/ReleaseGoals/64bit-time which renames libraries
with a t64 suffix. Fortunately, libgpg-errror is listed as not-affected.
Such renaming would cause the file loss scenario that the moratorium was
meant to prevent (DEP17 P1). If this happens, please upload to
experimental and wait at least three days. Multiarch (P7) is not an
issue, because the library is installed to an architecture-dependent
path. I locally verified that filesystem bootstrap (P8) continues wotk.
The debian-installer copes with libraries installed to
/usr/lib/<multiarch> (P10).
So I think, we're good to move ahead. I don't think it makes sense to
backport libgpg-error. If you consider doing that, don't use this patch
and use dh_movetousr instead. And remember to upload restructuring
changes during the trixie cycle to experimental first.
Helmut
diff --minimal -Nru libgpg-error-1.47/debian/changelog
libgpg-error-1.47/debian/changelog
--- libgpg-error-1.47/debian/changelog 2023-08-15 11:02:07.000000000 +0200
+++ libgpg-error-1.47/debian/changelog 2023-11-14 13:57:18.000000000 +0100
@@ -1,3 +1,10 @@
+libgpg-error (1.47-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Move libgpg-error.so.* to /usr. Closes: #-1
+
+ -- Helmut Grohne <[email protected]> Tue, 14 Nov 2023 13:57:18 +0100
+
libgpg-error (1.47-2) unstable; urgency=medium
* Team upload.
diff --minimal -Nru libgpg-error-1.47/debian/libgpg-error0-udeb.install
libgpg-error-1.47/debian/libgpg-error0-udeb.install
--- libgpg-error-1.47/debian/libgpg-error0-udeb.install 2023-07-30
13:52:55.000000000 +0200
+++ libgpg-error-1.47/debian/libgpg-error0-udeb.install 2023-11-14
13:56:57.000000000 +0100
@@ -1 +1 @@
-usr/lib/*/libgpg-error.so.* lib
+usr/lib/*/libgpg-error.so.*
diff --minimal -Nru libgpg-error-1.47/debian/libgpg-error0.install
libgpg-error-1.47/debian/libgpg-error0.install
--- libgpg-error-1.47/debian/libgpg-error0.install 2023-07-30
13:52:55.000000000 +0200
+++ libgpg-error-1.47/debian/libgpg-error0.install 2023-11-14
13:57:10.000000000 +0100
@@ -1 +1 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libgpg-error.so.* lib/${DEB_HOST_MULTIARCH}/
+usr/lib/${DEB_HOST_MULTIARCH}/libgpg-error.so.*
diff --minimal -Nru libgpg-error-1.47/debian/rules
libgpg-error-1.47/debian/rules
--- libgpg-error-1.47/debian/rules 2023-08-06 10:38:02.000000000 +0200
+++ libgpg-error-1.47/debian/rules 2023-11-14 13:56:43.000000000 +0100
@@ -31,9 +31,6 @@
override_dh_installdocs:
dh_installdocs -A README
-override_dh_link:
- dh_link -plibgpg-error-dev lib/$(DEB_HOST_MULTIARCH)/libgpg-error.so.0
usr/lib/$(DEB_HOST_MULTIARCH)/libgpg-error.so
-
### "arch-independent" Windows builds: ###
WIN_FLAGS=LDFLAGS="-Xlinker --no-insert-timestamp" CFLAGS="-g -Os
-fdebug-prefix-map=$(shell pwd)=." CPPFLAGS=
--- End Message ---
--- Begin Message ---
Source: libgpg-error
Source-Version: 1.47-3
Done: Andreas Metzler <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libgpg-error, 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.
Andreas Metzler <[email protected]> (supplier of updated libgpg-error 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: Sat, 18 Nov 2023 14:15:16 +0100
Source: libgpg-error
Architecture: source
Version: 1.47-3
Distribution: unstable
Urgency: low
Maintainer: Debian GnuPG Maintainers <[email protected]>
Changed-By: Andreas Metzler <[email protected]>
Closes: 1055939
Changes:
libgpg-error (1.47-3) unstable; urgency=low
.
[ Andreas Metzler ]
* Team upload
.
[ Helmut Grohne ]
* Move libgpg-error.so.* to /usr. Closes: #1055939
Checksums-Sha1:
fc70fb6b2ecd0f91f7cdcf41489e2fa0c8763e29 2896 libgpg-error_1.47-3.dsc
f21446642ae4802f50f39b32625311eaed2ea02a 18572
libgpg-error_1.47-3.debian.tar.xz
Checksums-Sha256:
350733b58bfa6f865597b41c51a16403aec5818fd70c35306c61decf62af7d15 2896
libgpg-error_1.47-3.dsc
3ba56dba7e31bf3bd771a89474a7581217ede3732c2fba8aca8629e6c4d92232 18572
libgpg-error_1.47-3.debian.tar.xz
Files:
d4a3bf966ebeaba4cf7385eb94282791 2896 libs optional libgpg-error_1.47-3.dsc
d183d91a4fe64b981faf4f9279179767 18572 libs optional
libgpg-error_1.47-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmVYuncACgkQpU8BhUOC
FIQ1aQ/+Kn5NYOlph0AFVkjt1Q8hqmUbR6uPh3yBpnyEIJJpegQkSUJA/NgsnAAQ
Y0VzRuB9ds79GfYlJ8AdM0FgAtpNmO7ztbIx6SeddxFg+GbxiHg3eUqAV/+bjAEa
iox1iIQrcc4w9U31YRvXKerJ4Aq6BWEfxRGtV5zvk+5vUTWEgwDiViSf8v5stPdp
P/VuCltFI9Ig4cbjQGVowKhdj37/ZrTAjXML5Ku/amV9Mxt432KFy/6MQ9+en/w1
7FmzB2gpebYmbyg5zBtu3rmvX+3pTQX14tCnfaiR0bRiS78gpUO5Ei3oFR3mh7Am
5f10Vo2IOGLJa0KB1Jd0lDxNxqTvHEDSmOdR05XfyUhb59BLeuraEwPRcl+vVmmt
c35gXMGobGOa3tBcM/7Y/fepoY7qewz61mVyF9YakLV+uAHiiO8AKGdfOijgZeJs
jaE/JX//s7wMEy3zPUfklBl3dRP2JcnfN2enjfPt0NQ+J5ZMAVXKMfcbzQf4EurP
ycA18mBattnaDnvEEaSdVTUBLdRCFXn1Il8fSVpOQdOWLy3v6fSEm2+kfizkIVAL
o8YxiO3riow325VfzpUGg+ioC4HkNoHFc7AYAQYXKc9+qgDc5HegSpuTafEjxjKV
ILOuIbwN3G2LoZXdjJF1v/fEwc+mCpgZXqQwDTrFzItGo1WgUH0=
=mZJF
-----END PGP SIGNATURE-----
--- End Message ---
