On 13/02/2021 18:05, Cyril Brulebois wrote:
> Wilco Baan Hofman (2021-02-13):
>> I managed to work around it. It seems as when you use 'in-target' in the
>> late script, that the problem starts to occur. chroot /target does
>> not trigger it.
>>
>> Still, it's a bit strange to have it
Wilco Baan Hofman (2021-02-13):
> I managed to work around it. It seems as when you use 'in-target' in the
> late script, that the problem starts to occur. chroot /target does
> not trigger it.
>
> Still, it's a bit strange to have it start to chain to individual
> commands together as if
On 13/02/2021 00:46, Cyril Brulebois wrote:
> 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
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
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
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
6 matches
Mail list logo
