From owner-freebsd-hackers@freebsd.org Tue Jan 5 15:49:55 2021 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 525434E7EC9 for ; Tue, 5 Jan 2021 15:49:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9H4g1RDhz4dLQ for ; Tue, 5 Jan 2021 15:49:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82c.google.com with SMTP id z3so21071507qtw.9 for ; Tue, 05 Jan 2021 07:49:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VNfza6JJ+vTDuZPJ8P/B0lin3M3VUmr/Jtlu2pE/gKo=; b=a6jymouinz67pS5EOoSLWOWL3W431hGRKwc36QfQYKXjVvMJOoErY+gxo+0PbEmDNf Yq5UKJi5Mi4qS7YosZdv7nVPZl/6ps+Iz0gF91DYgqeDeX/bxF/SZJiZEyox6rXqfGoX 7JyYpZNfLfePpGYxyyIGVs5j8L2m0RO4RsNdL1cB1LJnZOXAW8/g487+tMK/0DlxymtZ VZA1/IX0GzmD3h7eaXapnkt8IoL8Ms/eSROlyLfWDNgNNdBNEK/dd57GgegqqTnn6AAu mfFkt+14K3x1Ystacxjw/t6FmahZfaKaa2VYwUyNYYiPqX4FyFCl/YvATykGfIKOBMvB AyJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VNfza6JJ+vTDuZPJ8P/B0lin3M3VUmr/Jtlu2pE/gKo=; b=k+AVBEbKGKbG/hVQ5Hihtom+ofKnC6BQh/nt7UT3jXFwJj3k1p6jiksaaqUlQZY2gD AAgn/tTyRCUCGi4URP20HGJKsono3pM2cDxoo7RApsxF+37Q/H1m4fYyosXG5OJUCrUN wzdqXjK5we8z168qJX6pEZHGtNO7Q9mTA5t21wJwQ157MJbiUEK+exWPo5jY52C/rlI2 u/DT3iYWpdJ1+N/uImqj+DDgokHUnpc2P36FNapI9pn8j1x5hwGABc0wPzViDPyZJdb3 oXbmrZYmF3rQ682OAc15M5H2QRV73CZoDbMPI4KAQBwLXUHXWN/esfnWsjqP8HwgwTDJ xJ8g== X-Gm-Message-State: AOAM532TAM5US8mNQKNwEmRYleyPwmrcA7GOIxIQ8E68ZiHvm5egUr5T 13Fs/6LmIPKsjw/WSZTN9z0FYxcgLopzMIcVu9EOeQ== X-Google-Smtp-Source: ABdhPJzUsKAbhOa5tmAqD+LJTqsbm2y3cH88eJHD83W1YbJmwCwCnxk0xW/t8dh/Vj03kqPddB5JSbS15/4Us4EWX9c= X-Received: by 2002:ac8:51d8:: with SMTP id d24mr102830qtn.73.1609861793774; Tue, 05 Jan 2021 07:49:53 -0800 (PST) MIME-Version: 1.0 References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> In-Reply-To: <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> From: Warner Losh Date: Tue, 5 Jan 2021 08:49:42 -0700 Message-ID: Subject: Re: How does the time zone info get updated? To: Stefan Esser Cc: FreeBSD Hackers , Hal Murray X-Rspamd-Queue-Id: 4D9H4g1RDhz4dLQ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2021 15:49:55 -0000 On Tue, Jan 5, 2021, 4:24 AM Stefan Esser wrote: > 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 > > > > It gets updated several times a year. There were 6 during 2020. 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 > > it. > > > > The tz database includes the leap-seconds.list file. That gets updated > every > > 6 months. I'd like to get whatever FreeBSD does for time zones to > include > > that file so ntpd can use it without having to be concerned with keeping > it up > > to date. That only works if the zone info is kept up to date. > > 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). > > That way -STABLE users could update the definitions with base, but if > you strictly follow a release, you could install the port and decouple > timezone file updates from base updates ... > > 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 might > want to do it himself. > The calendar files aren't what he's talking about. These are the timezone files he's asking about. Those get updated very shortly after upstream releases. But, three things. First, we update leapseconds.list as soon as it is announce. Second, there is no way to get just these files updated: they 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 cron job that fetches leap-seconds.list if you have ntpd enabled and you are on the internet. So no TZ update outside an os upgrade, but the leap seconds file updates at the speed of NIST... Warner >