On 2017-02-13 20:28, Cyril Brulebois wrote:
Hilko Bengen <ben...@debian.org> (2017-02-13):
Here. I have stripped out the kernel messages.
Nothing interesting there, same locally with my own tests with your
boot
parameters. I guess it wouldn't hurt if we had more details in syslog
from bootstrap-base…
Anyway, adding a few debug bits, I can reproduce your issue and I think
it's quite clear: we run debootstrap from bootstrap-base using
file:///cdrom so we're not hitting the https code path. Cc-ing Philipp
and Marga who worked on adding https support since they might have
ideas
on how to fix this.
Given that Steve added it to the CD's force list, what about adding the
two packages to $include in the https check that already exists in
bootstrap-base.postinst (to set the proxy correctly)? I don't see a good
way of adding the two packages after debootstrap ran but telling
debootstrap to pull them in upon initial installation, assuming the
media has it, seems feasible to me.
Kind regards
Philipp Kern
