Hello Julian, On 22/01/2025 08:39, Julian Andres Klode wrote:
On Wed, Jan 22, 2025 at 01:09:21AM +0100, Cyril Brulebois wrote:Julian Andres Klode <j...@debian.org> (2025-01-21):Roland Clobus <rclo...@rclobus.nl> schrieb am Di., 21. Jan. 2025, 23:11:The new version of apt (2.9.24) will now cause a FTBFS for the daily d-i. This has been noticed already in the daily live ISO images based on sid.That sounds like nonsense. I've added Notices, they are only shown in interactive use in the apt(8) command which is not involved anywhere in the process, and they are not fatal either way.Maybe it's nonsense but I'm seeing a new failure for `æpt-get update`: E: Method gave invalid 400 URI Failure message: List of files can't be created as '/home/kibi/debian-installer/installer/build/apt.udeb/etc/apt/trusted.gpg.d/' is not a directory and that indeed breaks d-i builds. Looking at the few commits between 2.9.23 and 2.9.24 suggests 6f618323d2d1cea47df0952a9ed2cebcda6c7193 might trigger this, but I'm not going to spend time on this right now, especially ifThis is fine and it makes some sense, but it's unrelated to the matter being discussed here. And let me assure you, I combed through the logs of the failing builds and all I see is: P: building the debian-installer building build_cdrom_gtk failed, see log file dest/build_cdrom_gtk.log for details building build_cdrom_isolinux failed, see log file dest/build_cdrom_isolinux.log for details grep: ./dest//MANIFEST.udebs: No such file or directory cp: cannot stat 'chroot/debian-installer/build/dest/cdrom/vmlinuz': No such file or directory and then it starts failing to rsync some fails.
I'm sorry that I didn't take the time to fully point to the FTBFS part in the logs.
The FTBFS was first detected on Jenkins (as you have seen): https://jenkins.debian.net/view/live/job/reproducible_debian_live_build_lxqt_sid/1085/consoleFull The line that points to d-i FTBFS is (as you have seen):`building build_cdrom_gtk failed, see log file dest/build_cdrom_gtk.log for details`
Unfortunately, the log file that is pointed to (dest/build_cdrom_gtk.log) is not available in Jenkins. That makes my claim that the FTBFS is caused by the newer version of apt without evidence. The following rsync failures are be caused by the missing d-i image.
Yesterday I've built the installer locally, using sid in a chroot, andwas able to reproduce the FTBFS, which is caused by the line starting with 'E:', that Cyril reported. Having said directory already created does unfortunately not fix the error message.
A log is now available here: https://d-i.debian.org/daily-images/amd64/20250122-00:06/build_cdrom_isolinux.logPerhaps I should not have re-used this bug report, but you bumped the severity of this bug report, and after that the legacy one-line configuration stopped working, which made me think that there is a direct correlation.
For live-build I've implemented a quick fix, which adds 'signed-by' at https://salsa.debian.org/live-team/live-build/-/merge_requests/401, but that (temporarily) breaks the multi-distro functionality of live-build (due to the non-configurable filename 'debian-archive-keyring.gpg'). Unfortunately, this quick fix will also not be applicable to all use cases for debian-installer.
The current code for d-i parses the /etc/apt/sources.list file and uses that to generate a new single-line style sources.list for the retrieval of the udeb files.
It will take some effort to migrate to deb822 for d-i, and additionally live-build needs to migrate to deb822 as well.
With kind regards, Roland Clobus
OpenPGP_signature.asc
Description: OpenPGP digital signature
