Hi, On 2026-10-25 19:44 +03:00, Cyril Brulebois wrote: > Hi, > > Holger Wansing <[email protected]> (2026-10-18): >> Am 9. Oktober 2026 22:32:27 MESZ schrieb Alper Nebi Yasak >> <[email protected]>: >>> Hi, >>> >>> Daily build for the arm64 hd-media tiny image is broken, because it >>> can no longer fit into the 32 MiB limit for the gru/hana ChromeOS >>> boards. I have a small fix at [1] removing the depthcharge images >>> for the flavour. Also see the last time this happened for the cdrom >>> flavour [2]. >>> >>> I'm tempted to remove the "tiny" flavour for arm64 because I had >>> only added it to generate something that fits into that small limit. >>> I guess any proper attempt to re-add support for those boards should >>> not need that. Any objections, or preference either way? > > It's been on my to do list to reach out to you to see how we should > approach this, and my default action would have been to drop the images > if there were no other pertinent actions/fixes.
I think I'll go ahead and delete the hd-media/tiny thing as well (in a day or two), which still builds just the vmlinuz and initrd.xz [1]. They are in the MANIFEST and its build status shows up on the daily build overview, I was more concerned about if doing that would break anything or require manual changes to something else somewhere else. [1] https://d-i.debian.org/daily-images/arm64/20261103-01:19/hd-media/tiny/ >> My view is, that there is noone with a better expertise regarding the >> depthcharge images thingy than you :-) >> >> So I assume your approach is ok, if you think so. >> >> Or am I wrong here? Cyril? > > 100% correct on who's the depthcharge expert! Merging was the right > thing to do, and we're finally back to all green builds! Thanks Holger! I got sidetracked into working on depthcharge-tools upstream, then went out of town for a while, and forgot to actually merge it. (I _am_ trying to be more confident in merging my changes myself :D )

