Re: Bug#1030940: e2fsprogs: generates filesystems that grub-install doesn't recognize

Control: severity -1 important Control: retitle -1 e2fsprogs generates filesystems which cannot be mounted on systems with older e2fsprogs It turns out for debos the situation is a bit different. Since debos uses packages on the host to prepare the partitions, new features in e2fsprogs from unsta

Bug#901717: closed by Hideki Yamane (Bug#901717: fixed in debootstrap 1.0.104)

U46f17reM/Eg > hNR185Yvdjq0WewG4957rUyW9OVUxWaBzqSHltSb0qBhC2BuNittupdiHlTzagPe > 9a/sIw4bpyUIUE/4lGtLaAr+INPP3gk5ExksBe2yYEudUNTXwNnZvyODFww4NFK8 > Kxy/B31BP4tQutzrnmvoBIgSA/ObrbQyJWfyNcMT8KvWsiJll0Rgm3bsr3xhjoja > 7RwX8G/BXlYp8Q== > =GELe > -END PGP SIGNATURE- > >

Bug#901718: debootstrap: Version 1.0.102 breaks use of file mirrors

ist When trying to setup packages using setup_available, debootstrap exits and the log complains it cannot find the cached Packages file from DEF_MIRROR. I think debootstrap in --second-stage mode should read the mirror URI from sources.list or read the mirror URI from a new file called /debootstrap/mirror. Wh

Bug#901717:

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

Bug#901717: debootstrap: Version 1.0.102 breaks use of file mirrors

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" "