From: Leo Famulari <leo@famulari.name>
To: 28977@debbugs.gnu.org
Subject: [bug#28977] tzdata updates and package rebuilding guidelines
Date: Tue, 24 Oct 2017 16:35:25 -0400 [thread overview]
Message-ID: <20171024203525.GA5362@jasmine.lan> (raw)
In-Reply-To: <8ae3fec37111ec4c68bfc7251c9193d975e16dcd.1508876232.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
When splitting tzdata into two packages, one for "real" use and one for
test suites, I'd hoped it would allow us to update tzdata immediately
after new versions were released.
But, there are still way more than 300 packages depending on tzdata, so
it should be updated on a staging branch:
$ guix refresh -l -e '(@@ (gnu packages base) tzdata)'
Building the following 335 packages would ensure 635 dependent packages are rebuilt ...
According to NEWS, if we don't update tzdata soon, some time zones will
first become incorrect in Northern Cyprus in 5 days.
"Northern Cyprus switches from +03 to +02/+03 on 2017-10-29"
Any advice? Should we do a staging build? Just be late (the old status
quo)? Something else?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-24 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:17 [bug#28977] [PATCH] gnu: tzdata: Update to 2017c Leo Famulari
2017-10-24 20:35 ` Leo Famulari [this message]
2017-10-26 5:12 ` [bug#28977] tzdata updates and package rebuilding guidelines Ludovic Courtès
2017-11-12 20:54 ` bug#28977: " Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171024203525.GA5362@jasmine.lan \
--to=leo@famulari.name \
--cc=28977@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).