unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 50859@debbugs.gnu.org
Subject: [bug#50859] [core-updates-frozen] gnu: tzdata: Update to 2021b.
Date: Tue, 26 Oct 2021 13:50:34 -0400	[thread overview]
Message-ID: <YXg/6nbw3a05vqLF@jasmine.lan> (raw)
In-Reply-To: <8735oofn04.fsf@gmail.com>

On Tue, Oct 26, 2021 at 12:06:35AM -0400, Maxim Cournoyer wrote:
> Thanks, I've been building the cufbc branch manually for now (the CI
> seems to have some problem with the branch, but the logs won't say
> what).
> 
> I'm hoping we won't have to go through another world rebuild at this
> point.  I'm trying to test the branch some more then I'd like to merge
> it into cuf.

If CI hasn't evaluated the branch yet, then updating tzdata (yet again,
to 2021e) shouldn't require extra rebuilding when the time comes to
actually build the branch with Cuirass. The same number of packages will
need to be built whether we use the current tzdata release or an older
release. Or do I misunderstand your objection?




  reply	other threads:[~2021-10-26 17:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 22:59 [bug#50859] [core-updates-frozen] gnu: tzdata: Update to 2021b Leo Famulari
2021-10-04 23:14 ` [bug#50859] [core-updates-frozen vv2] gnu: tzdata: Update to 2021c Leo Famulari
2021-10-12  4:36   ` [bug#50859] [core-updates-frozen] gnu: tzdata: Update to 2021b Maxim Cournoyer
2021-10-16 17:32     ` Leo Famulari
2021-10-16 17:39       ` Leo Famulari
2021-10-26  4:06         ` Maxim Cournoyer
2021-10-26 17:50           ` Leo Famulari [this message]
2021-10-26 19:52             ` Maxim Cournoyer
2021-10-26 20:34               ` Leo Famulari
2021-10-26 17:53           ` Leo Famulari
2021-11-12  5:50             ` bug#50859: " Maxim Cournoyer

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=YXg/6nbw3a05vqLF@jasmine.lan \
    --to=leo@famulari.name \
    --cc=50859@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).