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: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, 60831-done@debbugs.gnu.org
Subject: bug#60831: Are our graphs okay?
Date: Sun, 22 Jan 2023 10:18:09 +0100	[thread overview]
Message-ID: <037e00bec68fb96402f6b74408708bb306cea1a6.camel@gmail.com> (raw)
In-Reply-To: <87v8l517hb.fsf_-_@gmail.com>

Am Dienstag, dem 17.01.2023 um 10:55 -0500 schrieb Maxim Cournoyer:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > The ‘patch-compilation-driver’ phase pulls in libgccjit even though
> > it has been deliberately removed from emacs-minimal.
> > 
> > * gnu/packages/emacs.scm (emacs)[#:phases]: Delete ‘patch-
> > compilation-driver’.
> > ---
> > Thanks Josselin for pointing this out.
> 
> I'd add the following git tag "Reported-by: Josselin Poiret <email>"
> instead, but otherwise LGTM.
I pushed it without the tag because I initially reported the pulling
in; although Josselin did help in finding how it was pulled in.

Anyway, this particular bug should be fixed now.  As for larger "Are
our graphs okay?" style bugs, I think we can definitely answer those
with "No.", given that cargo hasn't been replaced with antioxidant yet.
Thus, I'm closing this.

Cheers




  reply	other threads:[~2023-01-22  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 12:39 bug#60831: Are our graphs okay? Liliana Marie Prikler
2023-01-15 14:22 ` Josselin Poiret via Bug reports for GNU Guix
2023-01-15 16:24 ` bug#60831: [PATCH] gnu: emacs-minimal: Do not patch compilation driver Liliana Marie Prikler
2023-01-17 15:55   ` bug#60831: Are our graphs okay? Maxim Cournoyer
2023-01-22  9:18     ` Liliana Marie Prikler [this message]
2023-01-19 14:18   ` Ludovic Courtès

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=037e00bec68fb96402f6b74408708bb306cea1a6.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=60831-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=maxim.cournoyer@gmail.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.