Your message dated Tue, 13 Feb 2024 09:48:56 +0000
with message-id <e1rzppm-00gxmb...@fasolo.debian.org>
and subject line Bug#1063817: fixed in debconf 1.5.86
has caused the Debian Bug report #1063817,
regarding debconf-copydb pipe writes to GLOB file instead of stdout
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.)
--
1063817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debconf
Version: 1.5.85
Severity: normal
X-Debbugs-Cc: daniel.bung...@canonical.com
Dear Maintainer,
While debugging a FTBFS in Ubiquity, I observed that the usage of
debconf-copydb regressed when using version 1.5.85 of debconf. The
previous-in-Ubuntu version 1.5.82 of debconf was OK.
That invocation looks roughly like:
debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe
--config=InFd:none ...
Bisecting debconf from there found commit
5db857ade00953496bfdb7edb884296bebc41885:
"Avoid two-argument open"
Further tracing found the following change to Debconf/DbDriver/Pipe.pm
around line 120:
- open ($fh, '>-');
+ open ($fh, '>', \*STDOUT);
An additional symptom of this problem is GLOB files are created in CWD
with names that look like:
GLOB(0x0123456789ab)
Pointing the above to above to configdb on a fairly stock Debian Sid
installation produces an equivalent result - GLOB file creation
instead of the output.
Is the 3-argument form this?
open ($fh, '>&', \*STDOUT);
Originally filed as LP: #2052982.
-Dan
--- End Message ---
--- Begin Message ---
Source: debconf
Source-Version: 1.5.86
Done: Colin Watson <cjwat...@debian.org>
We believe that the bug you reported is fixed in the latest version of
debconf, 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.
Colin Watson <cjwat...@debian.org> (supplier of updated debconf 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: SHA256
Format: 1.8
Date: Tue, 13 Feb 2024 09:35:03 +0000
Source: debconf
Architecture: source
Version: 1.5.86
Distribution: unstable
Urgency: medium
Maintainer: Debconf Developers <debconf-de...@lists.alioth.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1063817
Changes:
debconf (1.5.86) unstable; urgency=medium
.
* Fix stdin/stdout handling regression in Debconf::DbDriver::Pipe (thanks,
Dan Bungert; closes: #1063817, LP: #2052982).
Checksums-Sha1:
7228fa436354957391ca506c7fe6d86f935bbcb9 2035 debconf_1.5.86.dsc
fad074732fbe7bbc6bca7cdecf5412bb75ae92cf 573944 debconf_1.5.86.tar.xz
Checksums-Sha256:
2528e4ed5f0873d5c425953d68bf6164959bd3f7430e53bce2bb99adf0e4a83a 2035
debconf_1.5.86.dsc
7128067f1144046a432784492c58839343768c15b32dc6fafbaa73200d3167d0 573944
debconf_1.5.86.tar.xz
Files:
45ad8f453c866c9a1edc38c8d50b797b 2035 admin optional debconf_1.5.86.dsc
837aecd8e44a5a998093e37a42f4cc0c 573944 admin optional debconf_1.5.86.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmXLN+UACgkQOTWH2X2G
UAv91g//egmsVy/XGaX+Mfc0YiaECqAUBf8n+cIWBwVPdchRYz2AA92USPeKr/RN
cpXa7iVYHdWesgQD1X3X4F+S3cGOy015nEhFBaZp/Gt/Hhtf6jHJdBJH8QYW+KKd
Fn4MM4CxGiQGYh+riwzt3pO+f3INeUWTrJT9p87IaUqYQuGHRkOBOIWm46phmmRP
td+wTLqEbd9qmlXbX0e2iXkD84wu7cdlJz0b8TR1hMWn1LHW3nFsRwGNp4BmZmKT
e6ZfwK1kBm0sfegMvgqFqArBZ80bB91yAVL1d6eOWNk4aW3iLSDpPqyLdb4f4QXO
rGnlMGPHXFHh2FmXA3gD4SKcGVFw0s42Ym2BexgumIoRbtcLJkmiOzVyZJ7IMdSz
5+LWylcxtK9DTT83ZOqALao+mUmPkORZ8c+VcpIaKfMiWtYuFEOuE4qVNBGtgStf
UFiPxyGXGxrlk91btJ03PtdmKnf6Ph93ZOqB5BAYQOoTFkHqy4konlG/OuddVzmA
KHgdenC7O4u4oq2oGakXU2CEI48ZvNLq/J1jb0tKpKytgEEH/0zPG2yFmK6RoIdu
i9XaPStm36S1xyKMCUr+KhPr7t+KW1VCc/V8f7nfQh+VTn/M75tf8t07gHuVU5MH
sshYcIXJi7dYHjzmjl34gmT+P81ck6YgD6MDdUTW26fvAOlqjOQ=
=wBGy
-----END PGP SIGNATURE-----
pgpRzMB1oCRUA.pgp
Description: PGP signature
--- End Message ---
