Andrew Kornilov <akornilov@gmail.com> (2025-10-01): > We still use the version 20240810. We upgraded it from the bookworm version > and it has been working fine till latest Trixie's changes (we build a > custom ISO based on the mostly Bookworm packages + Trixie's kernel + > debian-installer + some more not important updates). > > I've checked the code and see it contains the "Firmware_List_From_Contents" > function but a simpler version. > > We will upgrade it after some tests. Right now we applied the attached > patch and it works (but slow, of course). > > Thank you all, guys. Now i see that we should use the latest live-build > version (however, it might not work with bookworm packages, not sure right > now). Thanks anyway for the report, patch, and follow-ups. I totally understand how it makes sense not to move everything from oldstable to stable (I'm always slow to catch up personally), and why you encountered this issue. Now that we have a clear picture of what happens (more of a corner case than a general breakage we would have noticed months ago!), I still think it would make sense to teach the fallback code about the “new directory”, in unstable and then in trixie (which would only land after a point release). Phil, if you want to take the lead on the upload to unstable (with or without my comment suggestion, definitely not a blocker!), I can deal with the trixie preps? Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature