Date: Tue, 5 Jan 2021 20:51:49 +0100 From: Stefan Esser <se@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Hal Murray <hmurray@megapathdsl.net> Subject: Re: How does the time zone info get updated? Message-ID: <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> In-Reply-To: <CANCZdfrsxY2-h4NmcnaC16Y_tdpQuxEjPCYgeMvdfqoz5AmzRw@mail.gmail.com> References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> <CANCZdfrsxY2-h4NmcnaC16Y_tdpQuxEjPCYgeMvdfqoz5AmzRw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --AL4cD8n6iueTMTSMNWy8MB1DMuokSp0xN Content-Type: multipart/mixed; boundary="8q6jLyrg1n30rU5AxHYsr1X8pPaupEqWG"; protected-headers="v1" From: Stefan Esser <se@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Hal Murray <hmurray@megapathdsl.net> Message-ID: <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> Subject: Re: How does the time zone info get updated? References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> <CANCZdfrsxY2-h4NmcnaC16Y_tdpQuxEjPCYgeMvdfqoz5AmzRw@mail.gmail.com> In-Reply-To: <CANCZdfrsxY2-h4NmcnaC16Y_tdpQuxEjPCYgeMvdfqoz5AmzRw@mail.gmail.com> --8q6jLyrg1n30rU5AxHYsr1X8pPaupEqWG Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: quoted-printable Am 05.01.21 um 16:49 schrieb Warner Losh: >=20 >=20 > On Tue, Jan 5, 2021, 4:24 AM Stefan Esser <se@freebsd.org=20 > <mailto:se@freebsd.org>> wrote: >=20 > Am 05.01.21 um 08:51 schrieb Hal Murray:> It gets distributed with = the > base packages, but I haven't figured out how to > > keep it up to date. > > > > The info is distributed via IANA. > > https://www.iana.org/time-zones <https://www.iana.org/time-zones= > > > > > It gets updated several times a year.=C2=A0 There were 6 during = 2020.=20 > When is > > unpredictable, often shortly after some government passes a law > to change > > something with short notice. > > > > I'd expect there to be some mechanism to track the updates but I= > haven't found > >=C2=A0 =C2=A0it. > > > > The tz database includes the leap-seconds.list file.=C2=A0 That = gets > updated every > > 6 months.=C2=A0 I'd like to get whatever FreeBSD does for time z= ones > to include > > that file so ntpd can use it without having to be concerned with= > keeping it up > > to date.=C2=A0 That only works if the zone info is kept up to da= te. >=20 > We have recently moved the calendar files out of -CURRENT and into = a > port, and I could imagine providing the timezone files in the same > way (without removal from base, but from there only used as a fall-= back > if the port supplied files are not available). >=20 > That way -STABLE users could update the definitions with base, but = if > you strictly follow a release, you could install the port and decou= ple > timezone file updates from base updates ... >=20 > I'd be willing to support this change and maintain the data files, = but > I can imagine that the current maintainer of those files in base mi= ght > want to do it himself. >=20 >=20 > The calendar files aren't what he's talking about. Yes, I'm very well aware of that fact. > These are the timezone files he's asking about. Those get updated very = > shortly after upstream releases. Yes, and they are not considered critical security fixes and thus are not available as patches for those that install binary releases. By providing the timezone files by a port/package in the same way as the calendar data files (and preferring them if present), they could be kept up-to-date with other packages on system that run only release versions of FreeBSD. (And as written before, I do not suggest to remove the timezone files from base at all.) > But, three things. First, we update leapseconds.list as soon as it is=20 > announce. Second, there is no way to get just these files updated: they= =20 > come for free with a rebuild or and update using the beta pkgbase, but = > there is no automatic way to just get these. Third, there is an daily=20 > cron job that fetches leap-seconds.list if you have ntpd enabled and yo= u=20 > are on the internet. Yes, if only the leap-seconds are required, this helps get the time synchronized - but is quite different from timezone file updates. > So no TZ update outside an os upgrade, but the leap seconds file update= s=20 > at the speed of NIST... The OP did not ask for leap-second updates but for timezone files, if I understand his mail correctly. Regards, STefan --8q6jLyrg1n30rU5AxHYsr1X8pPaupEqWG-- --AL4cD8n6iueTMTSMNWy8MB1DMuokSp0xN Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAl/0w1YFAwAAAAAACgkQR+u171r99USu 6wf+IlnrRsCwedIOoejRsLoiOdY0X3ThhfhDd1f5o1e+TJ6SpVfj8ClMVYKCWAZ2Ls8QhlIE65eN uZYj+vU/n1yBcdvt3F9SXHHKe6CQCHUrzx1wrjbeetK3TfqydkmkQhLQZe/dRplt+BEz9Cd6cqDn WJH4CH6NdCR1hCPbs25m/yb3LGs/7thoDEogAukEhEuq4X2aObfLJWgzpJxZnAMyMs5/6fc4yFdx AyRoeDWnc74Gg5OqB9h8EtyvRXPcOFKusrp/16n2Llqi6eb4J/DquUgHxyHPDWJnOdur46zygRQk rTmRI5sy2mbUTKOxos1fzBhkxZH7ux0EJH6GILMouw== =wwTv -----END PGP SIGNATURE----- --AL4cD8n6iueTMTSMNWy8MB1DMuokSp0xN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47c37f75-e082-7a34-7eb6-3ee2a4ade395>