unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 28977@debbugs.gnu.org
Subject: [bug#28977] tzdata updates and package rebuilding guidelines
Date: Wed, 25 Oct 2017 22:12:08 -0700	[thread overview]
Message-ID: <87wp3iijbr.fsf@gnu.org> (raw)
In-Reply-To: <20171024203525.GA5362@jasmine.lan> (Leo Famulari's message of "Tue, 24 Oct 2017 16:35:25 -0400")

Hi Leo!

Leo Famulari <leo@famulari.name> skribis:

> 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"

Interesting.

> Any advice? Should we do a staging build? Just be late (the old status
> quo)? Something else?

I think we should identify those packages that unduly refer to ‘tzdata’
instead of ‘tzdata-for-tests’ and incrementally fix them.

In the meantime, I think this patch can go to ‘staging’ and/or
‘core-updates’ (which we should try building anytime now!).

How does that sound?

Thank you,
Ludo’.

  reply	other threads:[~2017-10-26  5:13 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 ` [bug#28977] tzdata updates and package rebuilding guidelines Leo Famulari
2017-10-26  5:12   ` Ludovic Courtès [this message]
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=87wp3iijbr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28977@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).