This bug was fixed in the package debconf - 1.5.86
---------------
debconf (1.5.86) unstable; urgency=medium
* Fix stdin/stdout handling regression in Debconf::DbDriver::Pipe (thanks,
Dan Bungert; closes: #1063817, LP: #2052982).
-- Colin Watson <cjwat...@debian.org> Tue, 13 Feb 2024 09:35:03 +0000
** Changed in: debconf (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/2052982
Title:
regression in debconf-copydb when writing to stdout
Status in debconf package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Invalid
Status in debconf package in Debian:
Fix Released
Bug description:
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 with names that look like:
GLOB(0x0123456789ab)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
