Your message dated Wed, 25 Feb 2026 17:48:16 +0000
with message-id <[email protected]>
and subject line Bug#1127142: fixed in libgpg-error 1.59-3
has caused the Debian Bug report #1127142,
regarding libgpg-error: autopkgtest regression with wine/10.0~repack-12
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.)
--
1127142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127142
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgpg-error,wine
Control: found -1 libgpg-error/1.58-2
Control: found -1 wine/10.0~repack-12
Control: block 1121773 by -1
Severity: serious
Tags: forky sid
Justification: https://release.debian.org/testing/rc_policy.txt 6a
User: [email protected]
Usertags: breaks needs-update
(This is very similar to a corresponding bug that I opened for
src:libassuan and src:wine)
Since wine was updated to 10.0~repack-12, it no longer provides
/usr/lib/wine/wine64. Instead, it's now /usr/bin/wine64 or
/usr/lib/${DEB_HOST_MULTIARCH}/wine/wine. Similarly, the
wineserver is now /usr/lib/${DEB_HOST_MULTIARCH}/wine/wineserver.
This breaks assumptions made by the autopkgtest in libgpg-error, causing
the new wine version to be unable to migrate to testing, which in turn
results in #1124433 not getting fixed in testing.
If this is an intentional interface change, then debian/tests/windows in
src:libgpg-error will need updating to use more appropriate paths.
Perhaps the Wine maintainers could suggest a patch?
Even if this was an intentional interface change, it might be a good
idea to special-case wine:amd64 and wine:i386 to provide enough symlinks
in /usr/lib/wine/ that the libgpg-error test will still pass: that would
allow this bug to be reassigned to src:libgpg-error at a lower severity,
and the compatibility symlinks could be removed when libgpg-error and
other affected packages (dxvk, libassuan) have been updated.
Or, if this was not an intentional interface change, perhaps wine should
special-case wine:amd64 and wine:i386 to provide those symlinks in the
longer term?
I've usertagged this as both "breaks" and "needs-update" because it
isn't obvious to me whether changes are desired in libgpg-error, in wine,
or both, but at least one of these two packages will need changes before
a version of wine with the new paths can migrate.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: libgpg-error
Source-Version: 1.59-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: Wed, 25 Feb 2026 18:29:44 +0100
Source: libgpg-error
Architecture: source
Version: 1.59-3
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuPG Maintainers <[email protected]>
Changed-By: Andreas Metzler <[email protected]>
Closes: 1127142
Changes:
libgpg-error (1.59-3) experimental; urgency=medium
.
* Workaround wine10 changes in autopkgtest (Closes: #1127142)
Checksums-Sha1:
181c1d8f4063eb566e0d7d6321a25a5bd4914e7f 2961 libgpg-error_1.59-3.dsc
711ffa5add57ac2b02f50ce3677b48171d668bc3 20012
libgpg-error_1.59-3.debian.tar.xz
58b243030e4bb5ee2a537a445866934ff328cab1 4596
libgpg-error_1.59-3_source.buildinfo
Checksums-Sha256:
991ee49e7d01fc9252dbe8d10650835f819f0ab77e3a1b597f9d8a3e3262cb7f 2961
libgpg-error_1.59-3.dsc
92a32f5fed25d3dfd0a1dd6e992c6bbafe37247eeaeadd79d898270431206adb 20012
libgpg-error_1.59-3.debian.tar.xz
963053dc317699f77cf441e2f2ae7ac49887ebb1288ff36ec97cb98b79cb38c2 4596
libgpg-error_1.59-3_source.buildinfo
Files:
16882869ba1895b6e181cdd348261d1a 2961 libs optional libgpg-error_1.59-3.dsc
6ba2b79753d3220e4ec56f1b2bd9e319 20012 libs optional
libgpg-error_1.59-3.debian.tar.xz
99dc355f982c283e84e0aea7c7ba6123 4596 libs optional
libgpg-error_1.59-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmmfMlwACgkQpU8BhUOC
FIRvhQ/7B7+zSjkQFCwgZIB0e3NQVtZd6KX30AzB5tWyb80z82vAQPPjgBPPsj53
YD9LL34orpYJo+IgWT1NLRzVas8g2I8g5+AWokoLFNU6E6IubiPNnOEJEed389Ck
pDhK57+wIeXRpmLH+SFJW40DxdTW7ilyDzcCXRtk8NaqfSrUiYmFOpflL+pdKu8X
gNaFG4adIvKqVVVo8/A0Mp2iUWcz1fssETNNLyR7+kMMSVA2xoQmfqoNtBjOQE6K
W1O0xrsCXRKCDHIWKVmK24jRqf/ww39HVIVS6y/2QRYRnhC8GkdOjSFCz816xzSl
J9hnDkNNVRkW1V3QsZM7rVSa6e04b+XFgQ1HRLz1Vr6xZJZHJguqn20Caf84Kk/4
RZLMgVf4qrrgtg4dGzq4Ka4bwgSMbhMjNgs7YbAeJj4QAWA7UcFInuPtB550eYSu
wgcmNSZBfcCEKlWM3HleYM7Jnxf69nyoauHU4jaIUdPHVGNoai+acXFK0j+m7ODA
MMcjMR97SE/1DfBdnCI7QXrQKCCQmB1lrTC1Q7zYMlgmC8HcH5xllaAxantuDvHl
ItSLoYakZOqTVKfjuZGInsDuRPQ5bczuBonHgvT6biAOBaTZEcsMMtDc8lphws41
EuJyWyjAGGVCX+nU1ErODKcmH6sRyzP/2uiU0FTXGmQHHWgbKGw=
=wI9W
-----END PGP SIGNATURE-----
pgpx6QN3R197J.pgp
Description: PGP signature
--- End Message ---
