Hi,
after letting this rest for a while I am now ready for another round of
trying.
On Wed, Jul 15, 2026 at 06:23:48PM +0200, Cyril Brulebois wrote:
Marc Haber <[email protected]> (2026-07-15):
when I boot a qemu machine from
https://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso, everything
is fine. I can proceed until partman comes up (I abort then, partman is what
interests me).
When I check out
https://salsa.debian.org/installer-team/debian-installer.git, do make
reallyclean, make build_netboot and boot from that mini.iso, at the stage
where partman is supposed to come up, I get a red screen saying that
partitioning disks failed.
Since you're not mentioning switching branch or anything, I'm assuming
you're working from the master branch, and building within unstable
I have followed the instructions, did the mr thing and have rebuilt
partman-base from the master branch. I also checked out the 241 tag
which matches the version that seems to currently be in the archive,
with the same result. I can say that my resulting partman-base has the
same depends line as partman-base_241_amd64.udeb from the archive, but
my locally built partman-base_241_amd64.udeb depends on >= 3.8 of
libparted-fs-resize0-udeb and libparted2-udeb. The error remains when I
harcode the same depends in my partman-base udev to be >= 3.7 as in the
archive.
(e.g. a devel-oriented schroot environment).
The docs don't say anything about schroot, I did the build in my daily
driver system after installing partman-base's Build-Dependendcies.
What environment am I supposed to use when I want to rebuild a single
udeb while still using the rest of d-i from the archive?
Starting from a clean Git checkout (meaning reallyclean is a no-op),
the build_netboot target gives me a build/dest/netboot/mini.iso that
lets me start and finish partman successfully.
Looks like your build environment differs to mine. How would you rebuild
it in case you lost it?
The log then says:
Jul 15 09:03:01 main-menu[259]: INFO: Menu item 'partman-base' selected
Jul 15 09:03:01 main-menu[259]: WARNING **: Deep recursion configuring package
partman-base (dep loop?)
Jul 15 09:03:01 main-menu[259]: WARNING **: Menu item 'partman-base' failed.
Why does my image behave differently? Any ideas what might be going
wrong here?
Maybe something to do with the build environment we have no information
about.
I apologize for not knowing enough about d-i to be able to give the
information that you don't ask for.
I am eager for a solution and would be willing to build a cloud VM that
I could give anyone access to. Maybe that would help identifying what I
was doing wrong in building my build environment. As an alternative, I
am prepared to answer questions about my build environment you might be
willing to ask.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421