Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Hi Todd,

Todd Morgan <bamamorgans@gmail.com> (2025-08-18):

[…]

Did you mean to file a bug report against *simple-cdd* instead of
debian-cd? The latter is used to build images, the former is what's
doing the local mirroring. And that's the one with code (and changelog
entry) with that mandatory installer-i386 thing that's failing:

debian/changelog:

    simple-cdd (0.6.9) unstable; urgency=medium
    …
      * Add installer-i386 to the local mirror for amd64 builds
    …
     -- Arnaud Rebillout <arnaudr@kali.org>  Mon, 06 Feb 2023 12:10:35 +0700

build-simple-cdd:

                    # For amd64 builds: debian-cd (>= 3.1.36) needs the i386 installer images,
                    # cf. https://salsa.debian.org/images-team/debian-cd/-/commit/8a8e6238.
                    if a == "amd64" and "i386" not in self.env.get("ARCHES"):
                        self.env.append("checksum_files",
                                        os.path.join("dists", self.env.format("{DI_CODENAME}/main/installer-{a}/{di_release}/images/{checksum_file_type}", a="i386")))

You seem to have miscopied the version number (debian-cd 3.1.6 doesn't
say anything about i386, while 3.1.36 indeed mentions “Add 32-bit EFI
binaries to all amd64 images too, so we no longer need a multi-arch
image for Bay Trail etc.”).

That's been made configurable via DISABLE_UEFI_32 in debian-cd 3.2.0
(see #1031424) and I'm pretty sure current debian-cd is perfectly able
to build installation images, so I'm not seeing any “grave” bug in it.

(Perhaps a wishlist item about switching the default or something?)

Just in case that's useful, here's the difference between bookworm and
trixie found in setup.git (where configuration is recorded):

    kibi@tokyo:~/debian-cd/setup.git (master =)$ diff -u bookworm/amd64.cfg trixie/amd64.cfg
    --- bookworm/amd64.cfg	2023-05-15 22:20:32.337362454 +0200
    +++ trixie/amd64.cfg	2024-11-29 14:15:22.622724256 +0100
    @@ -1,2 +1,6 @@
     export ARCH=amd64
     export VARIANTS=xen
    +
    +# Trixie won't have i386 d-i bits any more, so no point trying to
    +# include the 32-bit UEFI files on an amd64 build
    +export DISABLE_UEFI_32=1

See https://salsa.debian.org/images-team/setup/-/commit/fb1d40d68b6372c35b1bc429f9cc03dba032a2fb


Looping in simple-cdd people and Arnaud specifically.


Cheers,

Thanks for the ping, I'm looking at it. Hope to fix it in simple-cdd
soon-ish.

Best,

I did not mean for it to be labelled with simple-cdd. The package line in
my email was for debian-cd. I don't know how it got put under simple-cdd.

There is a linked relationship between the simple-cdd and debian-cd issues
in trixie. In simple-cdd, it was modified to always package amd64 and i386
installers together, even when you specify only amd64. The simple-cdd
commit for that references a commit in debian-cd

simple-cdd commit:
https://salsa.debian.org/debian/simple-cdd/-/commit/30373893ad206cdb7ecdabfc13d82ba9b316aa10

debian-cd commit:
https://salsa.debian.org/images-team/debian-cd/-/commit/8a8e6238

As for the debian-cd version where this was added, I meant to type version
3.1.36. See link above.

Thank you for letting me know about the environment variable for handling
this. For the end user, it would be a lot more straightforward if you
didn't have to be aware of the need for the DISABLE_UEFI_32 variable. The
end user like myself probably thinks it should just work out-of-the-box
for trixie. Just my $0.02.

Ah sorry, my bad, I'm the one who re-assigned the bug to simple-cdd.

After a second reading, I understand that your bug is really for
debian-cd, and the fact that it still tries to download i386 installer
images for trixie, despite the fact that those images don't exist
anymore. It could be improved.

But reading carefully the answer of Cyril, it also seems that debian-cd
has some defaults config for trixie, and it sets export DISABLE_UEFI_32=1.

So the issue is more likely that, maybe, simple-cdd doesn't make use of
the config files that are available in debian-cd? So the bug still
belongs to simple-cdd.

Anyway, I think it's fixed on the master branch of simple-cdd. Please
give it a try, tell me if that works for you.

Thanks,

Arnaud