unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: okay to merge rekados-rust-queue branch?
Date: Fri, 02 Sep 2022 16:16:20 +0200	[thread overview]
Message-ID: <87mtbhvp3f.fsf@gnu.org> (raw)
In-Reply-To: <87czchv4o4.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 30 Aug 2022 22:41:52 +0200")

Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I have a small branch with minor Rust package upgrades.  I successfully
> built icecat on that branch and the failing rust-* packages seen in the
> latest builds at https://ci.guix.gnu.org/jobset/rekados-rust-queue seem
> to be broken on the master branch as well.
>
> Would it be okay to merge this branch?
>
> I’m asking because the cargo-build-system makes it difficult to see how
> upgrades affect other packages, so building things on ci.guix.gnu.org
> and locally is the only way I can verify that the changes aren’t
> catastrophic.
>
> I’d like to merge this soon while the successful builds are fresh.

I guess that as long as there are no big regressions on ci.guix compared
to the starting point in ‘master’, that should be fine.

Normally we should be able to compare the status of both branches with:

  https://data.guix.gnu.org/compare?base_commit=b594c7354ce1daedecb3310b55817b69e90adbe9&target_commit=9ea5ebb9b1f393abba81e90d33ccc0da97f47032&locale=en_US.UTF-8

However, it seems that data.guix hasn’t processed the new branch.

Ludo’.


  reply	other threads:[~2022-09-02 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 20:41 okay to merge rekados-rust-queue branch? Ricardo Wurmus
2022-09-02 14:16 ` Ludovic Courtès [this message]
2022-09-09 15:41   ` Ricardo Wurmus

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=87mtbhvp3f.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).