Hello Simon,

On 03/03/2026 13:26, Simon Josefsson wrote:
Should 'binutils' and 'initramfs-tools-bin' be added to debian/control
Depends?

I think that should be 'Suggests', since the hooks aren't essential.
...

I'm the author of 5000 and 5010 binary hooks, they work fine for the regular 
Debian live images.
Unfortunately, I need both binary hooks to be able to have a reproducible build 
when building first against deb.debian.org and second against 
snapshot.debian.org with a similar timestamp as the first build.

If you do not intend to use snapshot.debian.org yet, you can safely remove both 
hooks from your config.

These dependencies are purely for the rebuild.sh script, so I would not put 
them in debian/control. Also, these dependencies are within the binary chroot, 
so the host will not need them.

The rebuild.sh script is perhaps not located in the correct repo, because it is 
not a real part of live-build (it is not packaged). In the past (when I had 
less access to the Git repositories on Salsa it was the easiest place to have 
the script).

However arm64 builds fails like this:
touch: failed to get attributes of 'live/vmlinuz': No such file or directory

-> The installer download its kernel image properly
```
D: Downloading file `binary/install/vmlinuz` from 
`http://deb.debian.org/debian//dists/trixie/main/installer-arm64/current/images/cdrom/vmlinuz`
```

So I assume that the regular kernel image is named differently (I cannot see 
that from the logs)

Any ideas why this only happens on arm64?

Does '--debian-installer none' work? Where are all 'vmlinuz' files located in 
the final image?

Anyway, I've updated the script to check better whether it will be able run 
without missing tools.

With kind regards,
Roland Clobus

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to