unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: Latest news on core-updates
Date: Thu, 20 Apr 2023 14:56:48 +0100	[thread overview]
Message-ID: <87wn264pfg.fsf@cbaines.net> (raw)
In-Reply-To: <87edog5dvl.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]


Christopher Baines <mail@cbaines.net> writes:

> Andreas Enge <andreas@enge.fr> writes:
>
>> I hope we will be able to merge core-updates after next weekend; also for
>> personal reasons, since I will not be able to spend much time on it any
>> more after that.
>
> After next weekend (around the end of April) sounds good to me.
>
> The bordeaux build farm has pretty much caught up after the staging
> merge which should mean there's some capacity to attempt to build
> core-updates changes prior to the merge around next weekend.
>
> I haven't restarted submitting builds for core-updates given I think
> there's still some big changes going to land, but in any case, it would
> be good to get this going once there are no planned big changes (aka the
> branch is frozen). Getting the builds to happen currently requires a
> code change in the qa-frontpage, but I can do this, I just need someone
> to let me know when I should.

Andreas suggested on IRC that I get things building, so I've configured
the qa-frontpage to start submitting builds for core-updates again.

You can track the progress here [1] of course, and if you want to get an
idea if any of the builds are currently happening, you can get some
information on what builds are assigned to what agents here [2]
(providing the experimental interface hasn't crashed).

1: https://qa.guix.gnu.org/branch/core-updates
2: https://bordeaux.guix.gnu.org/activity

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2023-04-20 15:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57   ` Andreas Enge
2023-04-17  8:06     ` Andreas Enge
2023-04-17  8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17  8:33   ` Andreas Enge
2023-04-17  9:03 ` Andreas Enge
2023-04-17  9:56   ` Andreas Enge
2023-04-17 12:19     ` Simon Tournier
2023-04-17 12:38       ` Andreas Enge
2023-04-17 12:57         ` Simon Tournier
2023-04-17 14:12       ` Lars-Dominik Braun
2023-04-17 17:47         ` Simon Tournier
2023-04-17 18:07           ` Andreas Enge
2023-04-17 19:01             ` Lars-Dominik Braun
2023-04-18 17:16               ` Andreas Enge
2023-04-21 18:29                 ` Lars-Dominik Braun
2023-04-17 12:57   ` Andreas Enge
2023-04-17 18:03   ` Maxim Cournoyer
2023-04-17 18:08     ` Andreas Enge
2023-04-18  5:04   ` John Kehayias
2023-04-18 17:38     ` Andreas Enge
2023-04-19 10:48   ` Latest news on core-updates Andreas Enge
2023-04-19 10:58     ` Christopher Baines
2023-04-19 12:41       ` Andreas Enge
2023-04-21  7:58         ` Andreas Enge
2023-04-21 13:01           ` Maxim Cournoyer
2023-04-20 13:56       ` Christopher Baines [this message]
2023-04-20 18:09         ` Andreas Enge
2023-04-21  8:20     ` Simon Tournier
2023-04-21  8:47       ` Andreas Enge
2023-04-21 11:31         ` Simon Tournier
2023-04-21 16:12     ` Katherine Cox-Buday
2023-04-21 16:12       ` Katherine Cox-Buday
2023-04-21 17:04       ` reza.housseini
2023-04-23  7:17         ` Andreas Enge

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=87wn264pfg.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@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).