unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Leo Famulari <leo@famulari.name>
Cc: 30537@debbugs.gnu.org
Subject: bug#30537: glibc 2.26 refuses to run on CentOS 6.8
Date: Tue, 20 Feb 2018 15:33:56 +0100	[thread overview]
Message-ID: <idj606r4tnv.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20180220125136.GA7573@jasmine.lan>


Leo Famulari <leo@famulari.name> writes:

>> For future updates to the glibc we would have to re-evaluate if the
>> current RHEL 6.x kernel still supports all features the glibc expects,
>> and decide once more if we can justify patching glibc to allow that one
>> particular kernel version.
>
> Yes... and this will probably continue for many years. But I do think we
> should do something to work around the issue now, and reevaluate our
> solution when the pressure is off.
>
> It would be nice if the graft only applied to x86_64-linux, but I've
> never considered if that is easy to do or not.

I don’t know if we can graft a package only for a single architecture.
At least at the time of ungrafting we could apply the patch only on
x86_64 (and only rebuild the world for that architecture).

FWIW: I’ve applied this patch to the installation at the MDC and it
works fine.  The biggest downside here is the slowness of grafts over
NFS (I still need to update the protocol to NFS 4.1) and the many lines
of output that are amplified by communicating with a remote daemon.

Other than that I’m happy that this crisis could be temporarily averted.

I’d like to have this in master, though, so that people can run “guix
pull” again and actually get working software.

--
Ricardo

  reply	other threads:[~2018-02-20 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 18:46 glibc 2.26 refuses to run on CentOS 6.8 Ricardo Wurmus
     [not found] ` <87d110stkn.fsf@mdc-berlin.de>
     [not found]   ` <87a7w4ssmx.fsf@mdc-berlin.de>
2018-02-19 19:41     ` bug#30537: " Ricardo Wurmus
     [not found]     ` <878tbosr7h.fsf@mdc-berlin.de>
2018-02-19 20:28       ` Jan Nieuwenhuizen
2018-02-21 23:12       ` Mark H Weaver
     [not found]       ` <87bmgiey3k.fsf@netris.org>
2018-02-22 20:30         ` Efraim Flashner
2018-02-23 22:01         ` bug#30537: Grafts vs. early bootstrapping packages Ludovic Courtès
2018-02-20  1:22 ` bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Leo Famulari
2018-02-20 11:52   ` Leo Famulari
2018-02-20 12:34     ` Ricardo Wurmus
2018-02-20 12:51       ` Leo Famulari
2018-02-20 14:33         ` Ricardo Wurmus [this message]
2018-02-20 17:55           ` Ricardo Wurmus
2018-02-20  9:39 ` Efraim Flashner
2018-02-23 22:26 ` 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

  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=idj606r4tnv.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=30537@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).