From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 30873-done@debbugs.gnu.org
Subject: [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27.
Date: Fri, 23 Mar 2018 10:20:38 +0100 [thread overview]
Message-ID: <87h8p7kv15.fsf@gnu.org> (raw)
In-Reply-To: <87fu4sklds.fsf@fastmail.com> (Marius Bakke's message of "Thu, 22 Mar 2018 19:36:47 +0100")
Hello Marius,
Marius Bakke <mbakke@fastmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> “Which ones do we pick” summarizes the problem, I think. It’s
>> upstream’s job to pick a set of changes and declare a new release. It
>> seems to me that we’re kinda doing the glibc release manager’s job here,
>> except we lack insight compared to them: it’s harder for us to judge
>> which changes are critical, which changes are just the beginning of
>> broader modifications/fixes, etc.
>>
>> I’d be willing to just use upstream’s release. It has bugs, no doubts,
>> but the next release will have its own bugs too. :-) Furthermore,
>> SONAMEs and symbol versioning is quite critical, but it’s usually done
>> under the assumption that people use releases, not intermediate
>> snapshots.
>>
>> I understand that glibc’s 2.27 branch is stable, contains nothing but
>> bug fixes, and in that sense is rather safe. Still…
>>
>> WDYT?
>
> I pushed the patch with the cherry-picked fixes. I'd rather not
> knowingly break "date" on some locales, or introduce runtime issues on
> i686. But I do agree that these things should really be upstreams job.
Great, makes sense!
> All the distros I've checked take the entire branch, so we are the "odd
> kid out". But I guess that's nothing new. ;-)
Heheh. :-)
>> BTW, what about emailing the libc people to add you to the list of
>> distro maintainers at <https://sourceware.org/glibc/wiki/MAINTAINERS>?
>> I think it could be useful.
>
> That might be useful indeed. I'll look into it.
>
> I think we're getting ready to build core-updates now. Should we try
> starting the 'core' subset on Hydra? Maybe also set a 'freeze' date?
Note that berlin has been building the ‘core’ subset for a while
already. With berlin it’s harder to see what the status is, currently,
though ‘guix weather’ and “make assert-*” should help.
As for the freeze date, it could be within a couple of days if we see
that there’s no issue with the ‘core’ subset.
Thoughts? Do you want to be the time keeper or should it be someone
else? :-)
Ludo’.
next prev parent reply other threads:[~2018-03-23 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:20 [bug#30873] [PATCH core-updates 0/3] glibc 2.27 Marius Bakke
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27 Marius Bakke
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 2/3] gnu: make: Fix compatibility with glibc 2.27 Marius Bakke
2018-03-20 13:19 ` Ludovic Courtès
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 3/3] gnu: make: End phase on #t Marius Bakke
2018-03-20 13:19 ` Ludovic Courtès
2018-03-20 13:18 ` [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27 Ludovic Courtès
2018-03-20 16:54 ` Marius Bakke
2018-03-21 18:26 ` Ludovic Courtès
2018-03-22 18:36 ` bug#30873: " Marius Bakke
2018-03-23 9:20 ` Ludovic Courtès [this message]
2018-03-22 12:53 ` [bug#30873] glibc-2.27 patches Efraim Flashner
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=87h8p7kv15.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30873-done@debbugs.gnu.org \
--cc=mbakke@fastmail.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.