From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, ashish.is@lostca.se
Cc: 72173@debbugs.gnu.org
Subject: [bug#72173] [PATCH] gnu: chicken: Update to 5.4.0.
Date: Sat, 20 Jul 2024 15:43:57 +0000 [thread overview]
Message-ID: <496724dba6db0fe71042b700b5593a1160f017d2@dismail.de> (raw)
In-Reply-To: <87y15wp3ui.fsf@gnu.org>
July 20, 2024 at 8:53 AM, "Ludovic Courtès" <ludo@gnu.org> wrote:
Hi Ludo,
Sorry, I forgot to check the dependent chicken packages 🙃🦆
I will revert this commit immediately on Monday when I get back.
I don't think I'll have time to look into the chicken package failures this weekend or next week.
ashish, could you send a v2 with the dependent chicken packages passing in order for this to be merged properly by Monday?
all the best,
jgart
next prev parent reply other threads:[~2024-07-20 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:59 [bug#72173] [PATCH] gnu: chicken: Update to 5.4.0 ashish.is--- via Guix-patches via
[not found] ` <f30b142a445930084072b99890c6a987@lostca.se>
2024-07-19 21:47 ` bug#72173: " jgart via Guix-patches via
2024-07-20 13:53 ` [bug#72173] " Ludovic Courtès
2024-07-20 15:43 ` jgart via Guix-patches via [this message]
2024-07-22 16:04 ` jgart via Guix-patches via
2024-07-22 21:08 ` Ashish via Guix-patches via
2024-07-22 21:34 ` jgart via Guix-patches via
2024-07-25 17:41 ` [bug#72173] [PATCH v2 0/2] " ashish.is--- via Guix-patches via
2024-07-25 17:41 ` [bug#72173] [PATCH v2 1/2] " ashish.is--- via Guix-patches via
2024-07-25 17:41 ` [bug#72173] [PATCH v2 2/2] guix: chicken-build-system: Update for 5.4.0 ashish.is--- via Guix-patches via
2024-07-25 20:48 ` [bug#72173] [PATCH] gnu: chicken: Update to 5.4.0 jgart via Guix-patches via
2024-07-26 8:35 ` Ashish via Guix-patches via
2024-07-26 8:44 ` Ashish via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496724dba6db0fe71042b700b5593a1160f017d2@dismail.de \
--to=guix-patches@gnu.org \
--cc=72173@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=jgart@dismail.de \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.