Cyril Brulebois <kibi@debian.org> (2025-12-27): > Thanks Lalo for the report and Holger for the reference, I'll prepare an > upload for trixie-proposed-updates, and check the situation for bookworm. > If and when that gets accepted, images build for further point releases > should be fixed. As far as I can see, that was triggered by tzdata's splitting legacy names into a separate package: https://salsa.debian.org/glibc-team/tzdata/-/commit/81fcc2bdf2cc464f24aee7524c476d82bcbcbf9a which was published in 2023c-8 (even if some small parts of it were reverted in 2023c-9 and 2023c-10), during the trixie release cycle, so bookworm should be unaffected. And indeed, on my up-to-date bookworm system, I'm seeing these four: /usr/share/zoneinfo/America/Argentina/Buenos_Aires /usr/share/zoneinfo/America/Buenos_Aires /usr/share/zoneinfo/Europe/Kiev /usr/share/zoneinfo/Europe/Kyiv while a trixie devel chroot only has: /usr/share/zoneinfo/America/Argentina/Buenos_Aires /usr/share/zoneinfo/Europe/Kyiv (I failed to mention this in my initial reply but of course I'm taking both fixes…) Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature