Processed: Re: Bug#971019: accidental chaining of debconf commands

2021-02-12 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #971019 [cdebconf] accidental chaining of debconf commands Severity set to 'important' from 'critical' -- 971019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971019 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#971019: accidental chaining of debconf commands

2021-02-12 Thread Cyril Brulebois
Control: severity -1 important (cc-ing Paul for information, due to interest in RC bugs) Hello Wilco, Wilco Baan Hofman (2020-09-26): > Package: cdebconf > Version: 0.249 > Severity: critical > > I have a problem with the debian installer, at the finish-install > stage in the udeb clock-setup.

Bug#971019: accidental chaining of debconf commands

2021-02-12 Thread Paul Gevers
Hi, Excuse me if I totally got this wrong, but to an outsider this looks like a typo... On Sat, 26 Sep 2020 12:17:13 +0200 Wilco Baan Hofman wrote: > debconf: --> FGET clock-setup/utc seen ^ hyphen > debconf: <-- 0 true > debconf: --> SET clock-setup/utc true INPUT low cl

Bug#971019: accidental chaining of debconf commands

2020-09-26 Thread Wilco Baan Hofman
Package: cdebconf Version: 0.249 Severity: critical I have a problem with the debian installer, at the finish-install stage in the udeb clock-setup. The following code path produces a strange protocol interaction: if db_fget clock-setup/utc seen && [ "$RET" = true ]; then # keep preseeded v