|From:||GNU bug Tracking System|
|Subject:||[debbugs-tracker] bug#29537: closed (Core updates broken)|
|Date:||Mon, 04 Dec 2017 12:55:02 +0000|
Your message dated Mon, 04 Dec 2017 13:54:18 +0100 with message-id <address@hidden> and subject line Re: bug#29537: Core updates broken has caused the debbugs.gnu.org bug report #29537, regarding Core updates broken to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 29537: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29537 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---
Subject: Core updates broken Date: Sat, 2 Dec 2017 21:12:48 +0100It seems, that we have a breakage in current core-updates. m4, gettext, and at least a few other packages fail to build.We had a discussion about that on irc, here are the important points:
[09:34:53] * g_bor has joined #guix [09:34:58] <g_bor> [09:37:37] <g_bor> [09:38:03] <g_bor> [09:38:10] <g_bor>
[16:46:05] <civodul> [16:46:16] <civodul> [16:47:16] <mb[m]1> [16:47:24] * kristofer has joined #guix [16:53:03] <civodul> [16:54:11] <mb[m]1> [16:54:35] <civodul> [16:54:41] <civodul> [16:54:46] <mb[m]1> [16:55:27] * jonsger has joined #guix [16:55:31] <mb[m]1> [16:55:36] <civodul> [16:55:41] <mb[m]1> [16:56:24] <civodul> [16:56:28] <civodul>
[16:57:52] <mb[m]1> [16:57:56] * jonsger has joined #guix [17:00:55] <mb[m]1> [17:00:57] <mb[m]1> [17:01:24] <civodul> [17:06:59] * ryanwatkins has joined #guix [17:11:08] <g_bor> [17:11:18] <g_bor> [17:11:30] <g_bor> [17:11:51] <g_bor> [17:13:38] <civodul> [17:13:45] <mb[m]1> [17:14:36] <g_bor> [17:14:55] <g_bor> [17:15:05] <g_bor> [17:16:04] * civodul has quit (Read error: Connection reset by peer) [17:17:26] <g_bor> [17:18:19] * civodul has joined #guix [17:18:42] <mb[m]1> [17:19:17] <g_bor> [17:19:38] <g_bor> [17:20:08] <g_bor> [17:20:15] <g_bor> [17:22:51] <g_bor> [17:23:01] <g_bor> [17:26:26] * xkapastel has joined #guix [17:30:38] <mb[m]1> [17:31:12] <g_bor> [17:31:21] <g_bor> [17:32:01] <mb[m]1> [17:32:24] <g_bor>
[17:36:36] <g_bor> [17:36:58] <g_bor> [17:37:13] <g_bor>> Ok, now it's building.<> I think this will take a time...<> (guile does take some time :) )<> I'm trying to help to switch the default icedtea to icedtea-8, and we'd like to that on core-updates...<> I've just written on the mailing list, that it would be nice if we could have substitutes for the core-updates gnu-build-system.<> That could speed things like this up.<< > mb[m]1: just popped in for a second, core-updates is failing on aarch64 also< > civodul too ^> Oh, well.<> Do we have a bug report on that already?<> Now I'm trying what mb[m]1 suggested, by reverting the ncurses commit.<> It might be easier to track related information in a bug...<<> reverting 667082d59104d4b964dce878f5e8c0f8ad1be958 did not helpDoes anyone know of a last working commit id?I'm trying to seen if it's working after last merge of master, but if someone knows a later point to start investigating the issue would help.It would also help, if someone with a more powerful computer could help, as building on mine is very slow.
--- End Message ---
--- Begin Message ---
Subject: Re: bug#29537: Core updates broken Date: Mon, 04 Dec 2017 13:54:18 +0100 User-agent: Notmuch/0.25.2 (https://notmuchmail.org) Emacs/25.3.1 (x86_64-pc-linux-gnu)Ludovic Courtès <address@hidden> writes: > Hi, > > Marius Bakke <address@hidden> skribis: > >> From 41677631be815d58c36052de7b54d297ad496ec1 Mon Sep 17 00:00:00 2001 >> From: Marius Bakke <address@hidden> >> Date: Sun, 3 Dec 2017 02:32:16 +0100 >> Subject: [PATCH] gnu: glibc: Don't use full version string in locale path. >> >> This is a follow-up to commit ee3ebf1a357bd4eb36a2fa1790a7b549cffb305a. >> Fixes <https://bugs.gnu.org/29537>. >> >> * gnu/packages/base.scm (glibc/linux)[version]: Change to >> 2.26.91-gaaa2eb83b8. >> [source](uri): Adjust accordingly. >> [arguments]: Use VERSION-MAJOR+MINOR for locales path. >> (glibc-locales, glibc-utf8-locales): Likewise. >> * guix/profiles.scm (ca-certificate-bundle, profile-derivation): Likewise. > > Good catch! That looks good to me (along with the guix/packages.scm > occurrence you found.) OK, pushed! Now, it would be good to do a final update of glibc so we get the fix for CVE-2017-15804 and a few other things. Could you upload a new tarball for glibc-2.26-105-g0890d5379c.tar.xz? I'm getting "0m8cnp2nik0596adwibhl0f3w649m57i3qciqwpwiix7y0sb7vhi" for it.
Description: PGP signature
--- End Message ---
|[Prev in Thread]||Current Thread||[Next in Thread]|