unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ian Eure <ian@retrospec.tv>
Cc: Felix Lechner <felix.lechner@lease-up.com>,  guix-devel@gnu.org
Subject: Re: Proposal: nss updates
Date: Sun, 18 Aug 2024 23:10:18 +0900	[thread overview]
Message-ID: <874j7hudkl.fsf@gmail.com> (raw)
In-Reply-To: <87r0ap1h74.fsf@meson> (Ian Eure's message of "Thu, 15 Aug 2024 16:38:05 -0700")

Hi Ian,

Ian Eure <ian@retrospec.tv> writes:

[...]

> The recent 3.101.1 NSS release is an ESR, per the relesae notes[1].
> What’s the process for getting that update into Guix? Since it’ll
> cause many rebuilds, it needs to go into a branch first.  core-updates
> seems like a reasonable place for it -- do I just send a patch and use
> prose to indicate that it should land in core-updates instead of
> master?  Or if I perform the work on the core-updates branch, do the
> patches indicate that when emailed?

I'd suggest to create the patches first, then build them on a feature
branch using CI (cuirass). You'll need some help from some committer who
can pushes the patches to a branch and configure the CI to build it.

I have myself little availability at the moment but that's going to
improve in the coming weeks.

-- 
Thanks,
Maxim


      reply	other threads:[~2024-08-18 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 14:13 Proposal: nss updates Ian Eure
2024-06-27 16:21 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 20:56   ` Ian Eure
2024-07-01  2:50 ` Maxim Cournoyer
2024-07-01 15:00   ` Ian Eure
2024-07-01 20:31     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-02  0:06       ` Ian Eure
2024-07-02  1:57         ` Maxim Cournoyer
2024-08-15 23:38           ` Ian Eure
2024-08-18 14:10             ` Maxim Cournoyer [this message]

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=874j7hudkl.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=ian@retrospec.tv \
    /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).