From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: glibc update
Date: Wed, 17 Feb 2016 11:14:19 -0500 [thread overview]
Message-ID: <20160217161419.GB1666@jasmine> (raw)
In-Reply-To: <20160216202010.GA21380@jasmine>
On Tue, Feb 16, 2016 at 03:20:10PM -0500, Leo Famulari wrote:
> I'm wondering if anyone has rebuilt their local systems based on the
> glibc update in security updates? I'm wondering what is the best way to
> achieve this?
>
> For Guix users, something like this?
>
> $ git checkout master \
> && git checkout -b my-branch \
> && git cherry-pick 8304ccdbc7b653ab0b81e3cec5420fcc6 \
> && ./pre-inst-env guix package -u
I tried this. The resulting process downloaded the bootstrap binaries
and appeared to rebuild *everything*. I haven't had time to figure out
what actually got rebuilt and if anything is still using the vulnerable
glibc.
>
> It would probably be desirable to reboot afterwards.
>
> GuixSD users would want to reconfigure, presumably.
>
> Then, you would rebase 'my-branch' on master as desired.
>
> It seems arduous, but faster than waiting for our build farm to rebuild
> all packages.
>
> Feedback requested!
>
next prev parent reply other threads:[~2016-02-17 16:14 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
2016-02-17 16:14 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160217161419.GB1666@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).