Re: git: e851e0aabdff - stable/13 - contrib/tzdata: import tzdata 2022g
- In reply to: Gordon Bergling : "Re: git: e851e0aabdff - stable/13 - contrib/tzdata: import tzdata 2022g"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 02 Dec 2022 00:53:35 UTC
On 2022-12-02 05:09:37 (+0800), Gordon Bergling wrote: > On Thu, Dec 01, 2022 at 01:37:54AM +0000, Philip Paeps wrote: >> The branch stable/13 has been updated by philip: >> >> URL: >> https://cgit.FreeBSD.org/src/commit/?id=e851e0aabdffb4f193e05645ffa45593f0603a1d >> >> commit e851e0aabdffb4f193e05645ffa45593f0603a1d >> Author: Philip Paeps <philip@FreeBSD.org> >> AuthorDate: 2022-11-30 01:36:28 +0000 >> Commit: Philip Paeps <philip@FreeBSD.org> >> CommitDate: 2022-12-01 01:36:29 +0000 >> >> contrib/tzdata: import tzdata 2022g >> >> Changes: https://github.com/eggert/tz/blob/2022g/NEWS >> >> tzdata 2022g and later split America/Ciudad_Juarez from >> America/Ojinaga. >> Ensure this file is removed in builds WITHOUT_ZONEINFO. >> >> (cherry picked from commit >> cf1ad5351036884e0a2e21d1bc9b712448467741) >> (cherry picked from commit >> 821549a9dfdf69f533feb84914b09450cd7311b6) > > many thanks for the update. One short question, I have a few FreeBSD > systems that are > externaly hosted where a switch the stable/13 is not possible. Would > it be possible to > put this tzdata-update into an ENA for current releases? > > My FreeBSD installation are hosted virtualy "across the globe" and I > am not sure how > important an tzdata is. (Cc: secteam@) We generally do freebsd-update builds and issue errata notices for tzdata updates. I wrote a draft EN and extracted the patch for freebsd-update. It will be in the next batch but we've not scheduled a date for that yet. We should probably do this one soon. It's a bit of a mess in that part of the world since the recent daylight saving silly season. Philip [hat: security-officer@ secretary] -- Philip Paeps Senior Reality Engineer Alternative Enterprises