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.

On Mon, Aug 18, 2025 at 9:50 PM Cyril Brulebois <[email protected]> wrote:

>
> Hi Todd,
>
> Todd Morgan <[email protected]> (2025-08-18):
> > Package: debian-cd
> > X-Debbugs-Cc: [email protected]
> > Version: 3.2.2
> > Severity: grave
> > Justification: renders package unusable
>
> […]
> >
> > debian-cd on Debian trixie is still attempting to pull in installer-i386
> > packages because in 3.1.6, both installers were made required.
> >
> > Error output:
> > 2025-08-18 18:42:53,964 INFO Running tool
> > /usr/share/simple-cdd/tools/mirror/reprepro
> > 2025-08-18 18:44:11,453 INFO mirror/reprepro ran successfully, full log
> can
> > be found in /debian/tmp/log/mirror-reprepro
> > 2025-08-18 18:44:11,466 INFO Checking package file
> > /debian/tmp/mirror/dists/trixie/main/binary-amd64/Packages using
> > /usr/bin/dose-debcheck
> > 2025-08-18 18:44:11,561 INFO Running tool
> > /usr/share/simple-cdd/tools/build/debian-cd
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd exited with code 2
> > 2025-08-18 18:44:13,781 ERROR Last 5 lines of standard error:
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd: xorriso 1.5.6 : RockRidge
> > filesystem manipulator, libburnia project.
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd: E: No packages found
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd: cp: cannot stat
> >
> '/debian/tmp/mirror/dists/trixie/main/installer-i386/current/images/cdrom/debian-cd_info.tar.gz':
> > No such file or directory
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd:     Failed to start disc
> 1,
> > error 256
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd: make: *** [Makefile:487:
> > image-trees] Error 1
> > 2025-08-18 18:44:13,781 ERROR build/debian-cd exited with code 2, full
> log
> > can be found in /debian/tmp/log/build-debian-cd
>
> 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 <[email protected]>  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,
> --
> Cyril Brulebois ([email protected])            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant
>

Reply via email to