Repository navigation
feat(tzdata): rebuild 4.0-wiremind0 with tzdata 2026e - #2
Merged
Merged
Conversation
julien-duponchelle
added this pull request to stack #3
October 8, 2026 13:15
julien-duponchelle
force-pushed
the
tzdata-2026e
branch
2 times, most recently
from
October 8, 2026 13:47
b1bc77f to
fe002f9
Compare
arthlr
self-requested a review
October 8, 2026 14:42
julien-duponchelle
force-pushed
the
tzdata-2026e
branch
2 times, most recently
from
October 8, 2026 15:30
fe002f9 to
d56fb7f
Compare
arthlr
reviewed
Oct 8, 2026
From 2026-11-01, British Columbia (tzdata 2026b), Alberta (2026c) and Manitoba (2026e) keep summer time all year. The 4.0-wiremind0 image has tzdata 2025b, and PostgreSQL reads the system tzdata (the PGDG packages use --with-system-tzdata): its conversions are one hour off for these zones. wiremind/tzdata/Dockerfile rebuilds the published 4.0-wiremind0 image with tzdata 2026e only: PostgreSQL, Patroni, glibc and ICU stay the same, so no REINDEX. A rebuild from postgres-appliance/ would also move PostgreSQL 17.4 to 17.11, glibc and about 250 other packages. The build fails if another package changes or if a rule is missing. A '*-tzdata*' tag publishes it with publish-tzdata.yaml (the same test as the main workflow, amd64 only), and the main workflow ignores these tags.
julien-duponchelle
force-pushed
the
tzdata-2026e
branch
from
October 8, 2026 16:32
8f9050a to
9a2890f
Compare
arthlr
approved these changes
Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From 2026-11-01, British Columbia (tzdata 2026b), Alberta (2026c) and
Manitoba (2026e) keep summer time all year. The 4.0-wiremind0 image
ships tzdata 2025b, and PostgreSQL reads the system tz database (the
PGDG packages are built with --with-system-tzdata): from that date, its
conversions for America/Vancouver, America/Edmonton and
America/Winnipeg are one hour off.
wiremind/tzdata/Dockerfile starts from the published 4.0-wiremind0
image, pinned by digest (amd64 and arm64), and upgrades the tzdata
package only. PostgreSQL, Patroni, glibc and ICU do not change, so no
REINDEX is needed: the operator rolls the pods out as for any image
change. A rebuild from postgres-appliance/ would also move PostgreSQL
17.4 to 17.11, glibc and about 250 other packages.
tzdata 2026e is only in jammy-proposed for now: the build takes this
one package from it, then removes the source. Set
TZDATA_POCKET=jammy-updates once Ubuntu publishes it there. The build
fails if another package changes, if one of the three rules is missing,
or if /etc/localtime moves.
A tag such as 4.0-wiremind0-tzdata2026e runs publish-tzdata.yaml: it
builds the image, runs test_spilo.sh and pushes
ghcr.io/wiremind/spilo-17:. The main workflow ignores -tzdata
tags, so it does not rebuild from source under the same name.
Tested locally: test_spilo.sh passes (20 test cases), and a demo Spilo
starts with Patroni and returns 05:00, 06:00 and 07:00 for 2027-02-13
12:00 UTC in Vancouver, Edmonton and Winnipeg.