regression in debconf-copydb when writing to stdout

Bug #2052982 reported by Dan Bungert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debconf (Debian)
Fix Released
Unknown
debconf (Ubuntu)
Fix Released
Undecided
Unassigned
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

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)

Dan Bungert (dbungert)
Changed in debconf (Ubuntu):
status: New → In Progress
Changed in ubiquity (Ubuntu):
status: New → In Progress
status: In Progress → Invalid
Changed in debconf (Ubuntu):
status: In Progress → Fix Committed
Changed in debconf (Debian):
status: Unknown → New
Changed in debconf (Debian):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Tue, 13 Feb 2024 09:35:03 +0000

Changed in debconf (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.