[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#982155: marked as done (PXE network booting looks broken to me: the initramfs doesn't attempt to wget my filesystem.squashfs)

Your message dated Wed, 10 Feb 2021 22:36:27 +0100
with message-id <1755d9d4-aed5-db90-19b6-ee3a38ddc6b1@debian.org>
and subject line Closing bug
has caused the Debian Bug report #982155,
regarding PXE network booting looks broken to me: the initramfs doesn't attempt to wget my filesystem.squashfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
982155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982155
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: live-boot
Version: 1:20210122
Severity: grave

Hi,

Since the last upload of live-build and live-boot (ie: 1:20210122) to unstable
the live image my script creates cannot be booted. After the network interfaces
are up, the image is supposed to wget the filesystem.squashfs, but it does
nothing, sitting idle and not even giving me a timeout or something.

Also, I wonder how come live-build / live-boot were uploaded 14 days from the
freeze, when no other upload were done during the development cycle of Bullseye.
There's clearly room for improvement here. If anything has changed in the
interface of live-build (which would be breaking me), then I'd like to find out
what. If you do know how to help, please do!

Also, did you try doing PXE booting of a live image with this version
1:20210122 ? Maybe you should... :)

Thanks for maintaining live-build,
Cheers,

Thomas Goirand (zigo)

--- End Message ---
--- Begin Message --- 
Version 1:20210208 fixed this bug: closing it.

Cheers,

Thomas Goirand (zigo)

--- End Message ---
Reply to: