all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: IMPORTANT: glibc security update
Date: Sat, 20 Feb 2016 00:20:36 -0500	[thread overview]
Message-ID: <20160220052036.GA2887@jasmine> (raw)
In-Reply-To: <87povsn7u4.fsf@netris.org>

On Fri, Feb 19, 2016 at 08:33:07AM -0500, Mark H Weaver wrote:
> Hello Guix!
> 
> I've pushed a fix for CVE-2015-7547 to the master branch, although Hydra
> has not fully rebuilt it.  I directed Hydra to build the most popular
> packages first, and with greater effort devoted to x86_64, so my hope is
> that most of what typical desktop users need is already built on x86_64.
> Still, it is likely that you'll need to compile some things locally.

At least two users on #guix (including me) have found that `guix pull`
is not fetching the latest snapshot. That is, the downloaded snapshot
is of some commit before the CVE-2015-7547 patch was applied.

Can you take a look?

> 
> i686 is not as fully built, so users will probably need to do some more
> compiling, but hopefully it is manageable.  I was able to fully update
> my Xfce desktop system on i686 anyway.
> 
> As I write this, the rebuilds of armhf and mips64el are considerably
> less advanced, so be prepared for a significant amount of local
> recompilation.
> 
> We'll prioritize getting grafts working properly soon, so that we can
> deploy security updates to core libraries much more quickly in the
> future.
> 
>      Thanks,
>        Mark
> 

  parent reply	other threads:[~2016-02-20  5:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 13:33 IMPORTANT: glibc security update Mark H Weaver
2016-02-19 18:14 ` Christopher Allan Webber
2016-02-20  5:20 ` Leo Famulari [this message]
2016-02-21  1:40   ` Mark H Weaver
2016-02-21 23:14     ` Mark H Weaver
2016-02-21 22:50 ` 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=20160220052036.GA2887@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.