Re: amd64 daily installer images not updated since 2026-07-05

--bpejnqahgc5svjkk
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Roland,

Thanks for looking into this.

Roland Clobus <[email protected]> (2026-07-17):
> +CC: debian-boot
>=20
> Hi,
>=20
> On 13/07/2026 00:01, Besmir Hasanaj wrote:
> > The amd64 directory under the daily installer builds appears not to
> > have been updated since July 5, while the other architecture
> > directories are updating normally.

I don't think any code changes are needed in the first place,
linux-image-* packages are still there, including for amd64.

For example:

    Package: linux-image-amd64
    Source: linux-signed-amd64 (7.1.3+1)
    Provides: linux-image-generic, linux-latest-modules-7.1.3+deb14-amd64, =
virtualbox-guest-modules, wireguard-modules (=3D 1.0.0)
    Depends: linux-base-amd64 (=3D 7.1.3-1), linux-image-7.1.3+deb14-amd64 =
(=3D 7.1.3-1)

FWIW I knew linux and linux-signed-* were in the process of getting
updated last week so I decided not to jump the gun at the time:
  https://buildd.debian.org/status/package.php?p=3Dlinux&suite=3Dsid
  https://buildd.debian.org/status/package.php?p=3Dlinux-signed-amd64&suite=
=3Dsid

> I'm wondering at 2 things:
> * Why is only amd64 affected, whereas the other architectures are still b=
uilding?

Because things are getting too big, on this architecture, and because
we're making extra sure we're not missing something as critical as the
kernel, ensuring we don't build and publish clearly-broken images.

Let's start with:

    kibi@casulana:/home/debian-cd/build/log$ ls *sid*amd64* -ltr|grep 'Jul =
1'
    -rw-r--r-- 1 debian-cd debian-cd  38654 Jul 13 03:38 Fsidamd64
    -rw-r--r-- 1 debian-cd debian-cd 108922 Jul 13 03:58 Msidamd64
    -rw-r--r-- 1 debian-cd debian-cd 113747 Jul 13 03:59 Ksidamd64
    -rw-r--r-- 1 debian-cd debian-cd 385272 Jul 13 05:57 Dsidamd64
    -rw-r--r-- 1 debian-cd debian-cd 395446 Jul 13 06:11 9sidamd64
    -rw-r--r-- 1 debian-cd debian-cd 450269 Jul 13 06:30 3sidamd64
    -rw-r--r-- 1 debian-cd debian-cd  56640 Jul 17 09:02 2sidamd64
    -rw-r--r-- 1 debian-cd debian-cd  75701 Jul 17 09:03 Gsidamd64

Let's look at the first one from 2026-07-13 (Fsidamd64):

    kibi@casulana:/home/debian-cd/build/log$ tail -5 Fsidamd64
      Checking base is installable for amd64
      1 files missing for debootstrap and kernel, aborting!
        amd64 is missing 1 files needed for debootstrap, look in /srv/cdbui=
lder.debian.org/src/deb-cd/tmp/Fsidamd64/forky/make_disc_tree.log for the l=
ist
    make[1]: *** [Makefile:483: image-trees] Error 2
    make[1]: Leaving directory '/srv/cdbuilder.debian.org/git/setup/forky/d=
ebian-cd'

Deeper down the rabbit hole:

    kibi@casulana:/home/debian-cd/build/log$ tail /srv/cdbuilder.debian.org=
/src/deb-cd/tmp/Fsidamd64/forky/make_disc_tree.log
    CD 1: GUESS_TOTAL is 429722 after adding amd64:main:systemd-boot:82200:=
<DEFAULT>
    CD 1: GUESS_TOTAL is 429793 after adding amd64:main:systemd-boot-efi:13=
5492:<DEFAULT>
    CD 1: GUESS_TOTAL is 429993 after adding amd64:main:linux-base-7.1.3+de=
b14-amd64:406916:<DEFAULT>
    CD 1: GUESS_TOTAL is 429995 after adding amd64:main:linux-base-amd64:12=
04:<DEFAULT>
    CD 1: GUESS_TOTAL is 436737 after adding amd64:main:linux-binary-7.1.3+=
deb14-amd64:13802032:<DEFAULT>
    CD 1: GUESS_TOTAL is 489620 after adding amd64:main:linux-modules-7.1.3=
+deb14-amd64:108302028:<DEFAULT>
    CD 1: Real current size is 489984 blocks after adding amd64:main:linux-=
modules-7.1.3+deb14-amd64:108302028:<DEFAULT>
    CD 1 over-full (489984 > 488281). Rollback!
    CD 1: Real current size is 436736 blocks after rolling back amd64:main:=
linux-modules-7.1.3+deb14-amd64:108302028:<DEFAULT>
    No linux-image-* package(s) found

Your MR effectively turns the =E2=80=9CI tried to fit linux-image in, addin=
g its
dependencies one after another, until there wasn't enough space, so we
only have some of them=E2=80=9D situation into an acceptable one.

> * Is the switch from 'linux-image-*' to 'linux-binary-*' the correct way =
to proceed?

I don't recall seeing requests/suggestions to move away from installing
linux-image-<arch> (this is a simplification, there are variations). It
doesn't look like d-i should focus on installing the binary instead of
pulling the image, as we wouldn't have any modules=E2=80=A6

    (unstable-amd64-devel)kibi@tokyo:~$ apt-file list linux-binary-7.1.3+de=
b14-amd64
    linux-binary-7.1.3+deb14-amd64: /boot/vmlinuz-7.1.3+deb14-amd64
    linux-binary-7.1.3+deb14-amd64: /usr/share/bug/linux-binary-7.1.3+deb14=
-amd64
    linux-binary-7.1.3+deb14-amd64: /usr/share/doc/linux-binary-7.1.3+deb14=
-amd64
    linux-binary-7.1.3+deb14-amd64: /usr/share/lintian/overrides/linux-bina=
ry-7.1.3+deb14-amd64

The only dependency of that package is linux-base-7.1.3+deb14-amd64,
which doesn't pull anything else, and installs a limited number of
support files:

    (unstable-amd64-devel)kibi@tokyo:~$ apt-file show linux-base-7.1.3+deb1=
4-amd64
    linux-base-7.1.3+deb14-amd64: /boot/System.map-7.1.3+deb14-amd64
    linux-base-7.1.3+deb14-amd64: /boot/config-7.1.3+deb14-amd64
    linux-base-7.1.3+deb14-amd64: /usr/lib/modules/7.1.3+deb14-amd64/module=
s.builtin
    linux-base-7.1.3+deb14-amd64: /usr/lib/modules/7.1.3+deb14-amd64/module=
s.builtin.modinfo
    linux-base-7.1.3+deb14-amd64: /usr/lib/modules/7.1.3+deb14-amd64/module=
s.order
    linux-base-7.1.3+deb14-amd64: /usr/share/bug/linux-base-7.1.3+deb14-amd=
64/control
    linux-base-7.1.3+deb14-amd64: /usr/share/bug/linux-base-7.1.3+deb14-amd=
64/presubj
    linux-base-7.1.3+deb14-amd64: /usr/share/bug/linux-base-7.1.3+deb14-amd=
64/script
    linux-base-7.1.3+deb14-amd64: /usr/share/doc/linux-base-7.1.3+deb14-amd=
64/NEWS.Debian.gz
    linux-base-7.1.3+deb14-amd64: /usr/share/doc/linux-base-7.1.3+deb14-amd=
64/changelog.Debian.gz
    linux-base-7.1.3+deb14-amd64: /usr/share/doc/linux-base-7.1.3+deb14-amd=
64/copyright

Mandatory buckets of salt: I haven't followed any talks, reports, etc.
=66rom the kernel team (ENOTIME, not ENOCARE) so the above is just based
on random observations.


Cheers,
--=20
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

--bpejnqahgc5svjkk
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmpaAIQACgkQ/5FK8MKz
VSCxQw/+J4v+kcbqL2OWKNEEJVZKQfLEGEF+YllkFqjsd96oHbewajJVDHi7U4oW
s23VA23UiKoqvNt4lc0kravKPI9Xp72VMlgUN29PFCmwzSzPjKi2/MrKKqvgcM8l
SSwbgQYICJY9e7T2gLiQgeLjlopHlIO69SclFXNOGEtwhvrD3N0TYgD0tA1qAh4P
SAbEmSrRBeB9Kvt4gO8ae/n3XLeAKtK5AGjzcTciYLlnKkKmEfbgDoMehMIuT5Qq
ePVrYfWTzOIJEsyN4FQtDnusSM9mMhBSMuQWlplRHCFM1il26h1txEn360RrpuGB
EztH8L67DfHba2ZkXpYVKwwkSW4gxPm9X/F0hSJYbu2khhc4PiR4ytiPoG07o3NX
BXW3hTG/cegFCqH3LoTl//qFgX39egyZtBupQfHGFOatnHwd5etGD72E4bvBWhkD
sHAN7gr9forH5Xsg/2uhpDGyYo5em1X8DqqOh5TDpdhDv6BAaQttsAUDjgSKk7Ud
4RgcxzriDNfITNZQ5tsCi0ZqKXku+Zt1ImXDm6DD/GKkUBhYBikGBQk5vu/W5kQv
LMufwsFN9Jn2vrMBTkBaUHksKfr7LJIJoRdgJ0EozUIw3VUEzuhRvq5uQbD6vCtk
0AmExG2wGGwplWOU3tuEvM7SS2w3iUsyCEcYnFygHWVhcIdUlGQ=
=HOj4
-----END PGP SIGNATURE-----

--bpejnqahgc5svjkk--