all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Philip McGrath <philip@philipmcgrath.com>, 61372-done@debbugs.gnu.org
Subject: bug#61372: [PATCH v2] gnu: racket: Update to 8.8.
Date: Sun, 19 Feb 2023 08:28:46 +0100	[thread overview]
Message-ID: <7cad668d1576362665b28c7d53bc5782080e7697.camel@gmail.com> (raw)
In-Reply-To: <e20a6ee2f8ae553ad11e8444b9fb0f3a469e5a69.camel@gmail.com>

Am Samstag, dem 11.02.2023 um 09:19 +0100 schrieb Liliana Marie
Prikler:
> Am Samstag, dem 11.02.2023 um 02:26 -0500 schrieb Philip McGrath:
> > Hi,
> > 
> > On Sat, Feb 11, 2023, at 2:16 AM, Liliana Marie Prikler wrote:
> > > >  gnu/local.mk                                  |  3 +-
> > > git am fails for me with "error: sha1 information is lacking or
> > > useless (gnu/local.mk)."
> > > What gives?
> > 
> > It succeeds for me with the patch both as I supplied it to `git
> > send-
> > email` (attached) and with `curl
> > https://issues.guix.gnu.org/issue/61372/raw/2 | git am`. I'm not
> > really familiar with the possible ways for things to go wrong,
> > though. (I have only used `git am` for contributions to Guix.)
> Turns out that my local checkout was a few commits behind.  I'll
> locally build racket and schedule the update for the 19th.
Pushed




      reply	other threads:[~2023-02-19  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 19:23 [bug#61372] [PATCH] gnu: racket: Update to 8.8 Philip McGrath
2023-02-09  7:45 ` Liliana Marie Prikler
2023-02-11  0:49 ` [bug#61372] [PATCH v2] " Philip McGrath
2023-02-11  7:16   ` Liliana Marie Prikler
2023-02-11  7:26     ` Philip McGrath
2023-02-11  8:19       ` Liliana Marie Prikler
2023-02-19  7:28         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7cad668d1576362665b28c7d53bc5782080e7697.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=61372-done@debbugs.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 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.