For reference, adding a space to the end of the line caused it to appear
in the joined line, which still caused the pkgsel step to try and
install tasksel tasksel/first multiselect (and thus fail)
** Description changed:
Binary package hint: busybox
- An automated preseed install has failed
Possibly related: When the system exhibits this bug, the VCs get a bit
unpredictable. Keystrokes often repeat (although this may just be a
side-effect of the VNC KVM I'm using), and occasionally the output from
the VC just to the right of the current one will overlay on top of the
one that
As baffling as this is to me, the following change to the config file
makes this problem vanish:
The last line of the preseed file is:
#d-i finish-install/reboot_in_progress note
...and I simply uncommented it.
What tickled this bug in the first place was my prepending a '#' on the
Hmm, actually I take back the earlier statement about the whitespace
just after dselect. It seems that *that* run errored out on a DNS
lookup of the archive hostname. Not sure yet if that was repeatable,
although the VC oddness and the syslog encoding effects (‘ instead of
) did occur.
--
Outright *removing* the finish-install/reboot_in_progress line causes
the problem to appear again, even with the space after dselect
(Manifests as Release 'first' for 'tasksel' was not found in pkgsel).
--
preseed file interpreted as having nonexistent backslashes
Well I've tried adding comment lines at various points in the file (both
before and after the two that get joined) and nothing I do seems to
affect it. It's almost as if the actual presence of the
reboot_in_progress setting is what fixes this. I even put this setting
at the top of the file and
