From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: ARM compilation via qemu binfmt - Assertion failure Date: Sun, 11 Feb 2018 10:53:32 +0100 Message-ID: <20180211095332.GA18764@thebird.nl> References: <87bmh4qrf5.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> <87bmh3kbd9.fsf@gnu.org> <87k1vqv23v.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> <20180208174238.2abc85dc@scratchpost.org> <87fu68o1dd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <87fu68o1dd.fsf@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Chris Marusich Cc: guix-devel@gnu.org, bug-guix@gnu.org, ng0@n0.is List-Id: bug-guix.gnu.org On Sun, Feb 11, 2018 at 12:45:18AM +0100, Chris Marusich wrote: > Danny Milosavljevic writes: > > > This is only fixed in glibc 2.27 (not in core-updates). > > Should we upgrade glibc in core-updates, then? Or is it better to do it > in the next core-updates cycle, to avoid still more unexpected breakage? I think we should not update packages deep in the tree unless there is a security patch. What we have now is well tested. Pj. --