Your message dated Mon, 6 Oct 2025 13:45:45 +0100 with message-id <[email protected]> and subject line Re: release-notes: Explain tzdata changes from bookworm to trixie has caused the Debian Bug report #1114970, regarding release-notes: Explain tzdata changes from bookworm to trixie to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1114970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114970 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: release-notes Severity: wishlist During the trixie cycle, the tzdata package reduced the set of timezone files that it ships, moving many of them to tzdata-legacy on the basis that the upstream tz project considers them to be for backward compatibility: tzdata (2023c-8) unstable; urgency=medium [...] * Ship only timezones in tzdata that follow the current rules of geographical region (continent or ocean) and city name. Move all legacy timezone symlinks (that are upgraded during package update) to tzdata-legacy. This includes dropping the special handling for US/* timezones. (Closes: #1040997) -- Benjamin Drung <[email protected]> Mon, 07 Aug 2023 15:02:14 +0200 People ran into this at the time (#1051973, #1056908), and the response was to add a NEWS.Debian entry: tzdata (2023d-1) unstable; urgency=medium From 2023c-8 on the tzdata package ships only timezones that follow the current rules of geographical region (continent or ocean) and city name. All legacy timezone symlinks (old or merged timezones mentioned in the upstream backward file) were moved to tzdata-legacy. This includes the US/* timezones. Please install tzdata-legacy in case you need the legacy timezones or to restore the previous behavior. This might be needed in case the system provides timezone-aware data over the network (e. g. SQL databases). -- Benjamin Drung <[email protected]> Tue, 02 Jan 2024 14:17:33 +0100 That's fine as far as it goes, but https://rachelbythebay.com/w/2025/09/11/debtz/ points out that it would be a good idea to mention this in the release notes. I agree: it's the sort of thing that can cause weird symptoms in various packages after the upgrade, and if you didn't carefully read through all the NEWS.Debian entries at the time then you might not think to look in tzdata for (say) a PostgreSQL problem. Thanks, -- Colin Watson (he/him) [[email protected]]
--- End Message ---
--- Begin Message ---This is now done, thanks to Chris Hofstaedtler: https://www.debian.org/releases/stable/release-notes/issues.en.html#timezones-split-off-into-tzdata-legacy-package Thanks, -- Colin Watson (he/him) [[email protected]]
--- End Message ---
