From: Mathieu Othacehe <othacehe@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 60373@debbugs.gnu.org
Subject: [bug#60373] Kernel job for Cuirass
Date: Thu, 29 Dec 2022 11:33:37 +0100 [thread overview]
Message-ID: <874jtezegu.fsf@gnu.org> (raw)
In-Reply-To: <Y6zIJb4Pk2mbDQ/6@jasmine.lan> (Leo Famulari's message of "Wed, 28 Dec 2022 17:50:13 -0500")
Hey,
> What's the procedure for making these changes? I can push to guix.git
> and maintenance.git, but I'll need assistance putting the changes into
> practice.
You can go ahead and I'll take care of reconfiguring Berlin. If you
prefer to do it by yourself, the procedure is the following:
- Log in on Berlin
- Checkout the latest maintenance repository in your home
- Run guix pull
- Run sudo -E guix system reconfigure ~/maintenance/hydra/berlin.scm -L
~/maintenance/hydra/modules/
- Notify sysadmins about the reconfiguration
Thanks,
Mathieu
next prev parent reply other threads:[~2022-12-29 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 2:22 [bug#60373] Kernel job for Cuirass Leo Famulari
2022-12-28 2:25 ` [bug#60373] [PATCH] maint: Add a manifest for everything related to linux-libre Leo Famulari
2022-12-28 2:29 ` [bug#60373] [PATCH] hydra: cuirass: Add 'kernel-updates' jobset Leo Famulari
2022-12-28 14:35 ` [bug#60373] Kernel job for Cuirass Mathieu Othacehe
2022-12-28 22:50 ` Leo Famulari
2022-12-29 10:33 ` Mathieu Othacehe [this message]
2022-12-29 18:54 ` Leo Famulari
2023-01-05 3:48 ` Leo Famulari
2023-01-05 17:37 ` Mathieu Othacehe
2023-01-06 1:19 ` Leo Famulari
2023-01-06 3:00 ` Leo Famulari
2023-01-06 5:33 ` Leo Famulari
2023-01-06 6:27 ` Leo Famulari
2023-01-07 14:50 ` Mathieu Othacehe
2023-01-07 14:47 ` Mathieu Othacehe
2023-01-07 18:38 ` Leo Famulari
2022-12-28 22:54 ` [bug#60373] [PATCH v2] maint: Add a manifest for everything related to linux-libre 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=874jtezegu.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=60373@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).