unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Philip McGrath <philip@philipmcgrath.com>,
	ashish.is@lostca.se, 72742@debbugs.gnu.org,
	72582@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Efraim Flashner" <efraim@flashner.co.il>
Subject: [bug#72742] [PATCH] gnu: racket: Update to 8.14.
Date: Wed, 21 Aug 2024 04:35:05 +0200	[thread overview]
Message-ID: <36fe4db6bf343e12e17d8fea67fa22b82e3f8a19.camel@gmail.com> (raw)
In-Reply-To: <d436bc1f-1060-43f9-85c2-a669458ec96a@app.fastmail.com>

Hi Philip,

Am Dienstag, dem 20.08.2024 um 21:39 -0400 schrieb Philip McGrath:
> In 72582 I also sent a commit reverting
> 0c96f7932de50c81f4b4714f287520699107c8bb, which merely masked an
> underlying problem on riscv64-linux, for reasons I explained in the
> cover letter there. If no one has time or hardware to look into the
> riscv situation, it's of course fine to just apply the commit with
> the update to 8.14 and address riscv in a separate issue (which
> arguably I should have done in the first place ...).
Looking at CI, there appears to be no meaningful difference except that
previously unknown packages have since become blocked – for what
appears to be completely unrelated reasons, e.g. missing disk space[1].

So while the CI situation for riscv is "we don't know", at the very
least we could push the update that's already built.

Cheers

[1]
https://bordeaux.guix.gnu.org/build/4c0c8fce-f139-4936-9dd8-4c08ba887ac1/log





      reply	other threads:[~2024-08-21  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  0:54 [bug#72742] [PATCH] gnu: racket: Update to 8.14 ashish.is--- via Guix-patches via
2024-08-21  1:39 ` Philip McGrath
2024-08-21  2:35   ` Liliana Marie Prikler [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=36fe4db6bf343e12e17d8fea67fa22b82e3f8a19.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=72582@debbugs.gnu.org \
    --cc=72742@debbugs.gnu.org \
    --cc=ashish.is@lostca.se \
    --cc=efraim@flashner.co.il \
    --cc=ludo@gnu.org \
    --cc=philip@philipmcgrath.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).