From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29406-done@debbugs.gnu.org
Subject: [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26.
Date: Tue, 28 Nov 2017 18:16:20 +0100 [thread overview]
Message-ID: <87609uz5ln.fsf@fastmail.com> (raw)
In-Reply-To: <87r2sixueu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hi,
>>>
>>> Marius Bakke <mbakke@fastmail.com> skribis:
>>>
>>>> From a5b022a355a0babdc4809f39f94b6662ea7789d1 Mon Sep 17 00:00:00 2001
>>>> From: Marius Bakke <mbakke@fastmail.com>
>>>> Date: Sat, 25 Nov 2017 19:17:28 +0100
>>>> Subject: [PATCH] gnu: glibc: Update to 2.26-91-gaaa2eb83b8.
>>>>
>>>> * gnu/packages/base.scm (glibc/linux): Update to 2.26-91-gaaa2eb83b8.
>>>> [source](uri): Download from alpha.gnu.org.
>>>> [source](patches): Remove glibc-CVE-2017-15670-15671.patch.
>>>> ---
>>>> gnu/packages/base.scm | 17 ++++++++++++-----
>>>> 1 file changed, 12 insertions(+), 5 deletions(-)
>>>>
>>>> diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
>>>> index a6663c5cf..20d5fa72b 100644
>>>> --- a/gnu/packages/base.scm
>>>> +++ b/gnu/packages/base.scm
>>>> @@ -515,14 +515,22 @@ store.")
>>>> (define-public glibc/linux
>>>> (package
>>>> (name "glibc")
>>>> - (version "2.26")
>>>> + ;; Glibc has stable branches that continuously pick fixes for each supported
>>>> + ;; release. Unfortunately they do not do point-releases, so we are stuck
>>>> + ;; with copying almost all patches, or use a snapshot of the release branch.
>>>> + ;;
>>>> + ;; This version number corresponds to the output of `git describe` and the
>>>> + ;; archive can be generated by checking out the commit ID and run:
>>>> + ;; git archive --prefix=$(git describe)/ HEAD | xz -9 > $(git describe).tar.xz
>>>> + ;; See <https://bugs.gnu.org/29406> for details.
>>>> + (version "2.26-91-gaaa2eb83b8")
>>>> (source (origin
>>>> (method url-fetch)
>>>> - (uri (string-append "mirror://gnu/glibc/glibc-"
>>>> - version ".tar.xz"))
>>>> + (uri (string-append "https://alpha.gnu.org/gnu/guix/mirror/"
>>>> + "glibc-" version ".tar.xz"))
>>>> (sha256
>>>> (base32
>>>> - "1ggnj1hzjym7sn93rbwydcqd562q73lsb7g7kd199g6j9j9hlkp5"))
>>>> + "0867nxcv3n48iq3b5f1hca7cyx8pzjva67rxyslf9l595xd934kx"))
>>>
>>> I’ve built the tarball locally with the command above but the hash I get is:
>>>
>>> 1zwz6d0x3ndd0hgqp17fx71miyjvn4dgkl1nzhaz3mbcqxzrprhk
>>
>> Gah. I used "xz --threads=0" initially and didn't expect it to change
>> the outcome.
>>
>> I can reproduce the above hash by running the same command:
>>
>> $ git archive --prefix=$(git describe)/ HEAD | xz -9 > $(git describe)-nothreads.tar.xz
>> $ guix hash glibc-2.26-91-gaaa2eb83b8-nothreads.tar.xz
>> 1zwz6d0x3ndd0hgqp17fx71miyjvn4dgkl1nzhaz3mbcqxzrprhk
>>
>> Let's stick with the "nothreads" variant for compatibility.
>
> OK, it’s now available at
> <https://alpha.gnu.org/gnu/guix/mirror/glibc-2.26-91-gaaa2eb83b8.tar.xz>.
>
> Thank you!
Typical: The 2.26 branch just got 10 new commits that look important:
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.26/master
Especially the malloc() fixes. Should we pick them while we still have
time, or update the snapshot?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-11-28 17:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 21:28 [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26 Marius Bakke
2017-11-23 14:57 ` Leo Famulari
2017-11-24 1:12 ` Marius Bakke
2017-11-24 3:08 ` Marius Bakke
2017-11-27 21:30 ` Leo Famulari
2017-11-28 1:42 ` Marius Bakke
2017-11-28 10:45 ` Ludovic Courtès
2017-11-28 12:54 ` Marius Bakke
2017-11-28 16:03 ` bug#29406: " Ludovic Courtès
2017-11-28 17:16 ` Marius Bakke [this message]
2017-11-28 21:02 ` [bug#29406] " Ludovic Courtès
2017-11-28 21:42 ` Leo Famulari
2017-11-29 16:40 ` Ludovic Courtès
2017-11-28 18:26 ` Leo Famulari
2017-11-23 15:42 ` 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=87609uz5ln.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29406-done@debbugs.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.