Hi Christoph,
On 31-08-2021 14:30, Christoph Sarnowski wrote:
> Hello Release-Mailinglist,
Our mailing list doesn't work well for plain mail as the amount of (bug)
traffic is very high. A bug report works better to avoid it failing
through the cracks.
> I stumbled upon this "bug" using di-netboot-assistant and thought that
> this mailing list might be the best
I very much doubt it, d-i is done over at d-boot.
> point of contact, feel free to teach me otherwise if I am mistaken :)
$(reportbug debian-installer)
> What I tried:
>
> - Download
> https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/netboot.tar.gz
>
>
> - Extract tar archive
>
> - Run "zcat debian-installer/amd64/initrd.gz | grep -c bookworm"
>
> Output: "0" (i.e. no references to "bookworm" inside the initrd)
>
> - Run "zcat debian-installer/amd64/initrd.gz | grep -c bullseye"
>
> Output: "13" (i.e. still a lot of references to "bullseye" inside the
> initrd)
I think that's to be expected, but people over at d-boot can probably
confirm my understanding. There has not been an update of the installer
after the bullseye release, so the installer doesn't know yet that the
release happened. It's the same for quite some "infrastructure" packages
I'd expect.
> One of the results of those references is that the netboot image
> searches for preseed.cfg files on the tftp server under a directory of
> "bullseye".
>
> If I provide a preseed file there, the installer reports a "Bad archive
> mirror" ("mirror does not support the specified release (bullseye)"). My
> guess is that the release file is checked for both Suite and Codename,
> and since "bullseye" is not "testing" anymore, it always fails.
>
>
> Expected Result:
>
> - the bookworm initrd does search for preseed.cfg under "bookworm" and
> accept debian mirrors as valid.
I wonder if that's a fair expectation so soon after the release, but I
defer to d-boot.
Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature