ing to this email.
>
>
> --
> 901717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901717
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Hideki Yamane
> To: 901717-cl...@bugs.debi
Your message dated Tue, 26 Jun 2018 12:19:15 +
with message-id
and subject line Bug#901717: fixed in debootstrap 1.0.104
has caused the Debian Bug report #901717,
regarding debootstrap: Version 1.0.102 breaks use of file mirrors
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #901717 [debootstrap] debootstrap: Version 1.0.102 breaks use of file
mirrors
Bug #901718 [debootstrap] debootstrap: Version 1.0.102 breaks use of file
mirrors
Added tag(s) pending.
Added tag(s) pending.
--
901717: https://bugs.debian.org/
Hi,
On Sat, 23 Jun 2018 11:14:58 +0100
Christopher Obbard wrote:
> $ cat test/debootstrap/debootstrap.log
> ...
> /debootstrap/debootstrap: 1428: /debootstrap/debootstrap: cannot open
> //var/lib/apt/lists/http:__deb.debian.org_debian_dists_buster_main_binary-armhf_Packages:
> No such file
Oh,
I have confirmed debootstrap 1.0.101 is unaffected, so I am using this
version in the mean time.
Okay, so thinking about it I think inserting debootstrap.invalid in
the sources.list was a pretty good way of doing it for the case of
anything that isn't an http/https mirror.
Can we do that instead
Package: debootstrap
Version: 1.0.102
Severity: important
This is a new bug introduced in 1.0.101
We use debootstrap with a custom file:// mirror to strap cross-arch
images for SBCs, with a second call to debootstrap --second-stage.
in this format:
debootstrap --foreign --arch="armhf" "buster" "
6 matches
Mail list logo