all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: glibc update
Date: Mon, 22 Feb 2016 12:47:35 -0500	[thread overview]
Message-ID: <20160222174735.GB4836@jasmine> (raw)
In-Reply-To: <877fhwolxy.fsf@gnu.org>

On Mon, Feb 22, 2016 at 03:32:09PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > On Wed, Feb 17, 2016 at 09:10:12PM +1100, Jookia wrote:
> >> On Wed, Feb 17, 2016 at 10:10:14AM +0100, Andy Wingo wrote:
> >> > Given that seriousness of this bug and the amount of time that a full
> >> > rebuild will take, does anyone have a graft recipe they would like to
> >> > share?
> >> 
> >> Not really, unfortunately grafts are broken right now. I'm not sure how high a
> >> priority it is to fix it, but from what I know Mark Weaver knows how to fix it.
> >
> > Here is the relevant bug report:
> > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22139
> >
> > Personally, I'd say it's extremely high priority, but I don't know
> > Scheme or Guix internals well enough to fix it myself.
> 
> I agree it’s high-priority.  I’ll take another stab at it.

Christopher linked to some relevant discussions for posterity in the bug
report: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22139#8

  reply	other threads:[~2016-02-22 17:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 20:20 glibc update Leo Famulari
2016-02-17  9:10 ` Andy Wingo
2016-02-17 10:10   ` Jookia
2016-02-17 15:59     ` Leo Famulari
2016-02-22 14:32       ` Ludovic Courtès
2016-02-22 17:47         ` Leo Famulari [this message]
2016-02-17 16:14 ` Leo Famulari
2016-02-17 16:28   ` Jookia
2016-02-17 18:27     ` Leo Famulari
2016-02-18  6:45       ` Security warnings (was Re: glibc update) Pjotr Prins

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=20160222174735.GB4836@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --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.