From: Marius Bakke <mbakke@fastmail.com>
To: "Leo Famulari" <leo@famulari.name>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Let’s freeze and build ‘core-updates’!
Date: Mon, 06 Mar 2017 19:49:42 +0100 [thread overview]
Message-ID: <87efya44vt.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170306184246.GD2185@jasmine>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Mon, Mar 06, 2017 at 10:19:34AM +0100, Ludovic Courtès wrote:
>> Hello Guix!
>>
>> Looks like there’s been a disk space issue a few days ago that’s now
>> solved, so I’ve restarted an evaluation of the “core” subset.
>>
>> Is there any blocker left or should we move forward after that?
>
> Let's also decide what to do about GRUB. I updated it originally because
> something (I forgot what) failed to build without a newer GRUB.
I think you meant "flex" here.
According to https://github.com/westes/flex/issues/162 , this commit
should fix the grub issue:
https://github.com/westes/flex/commit/f5d87f1a26f4a5c3402497008ae10e9a1345d327
Seeing as wireshark is apparently also affected according to the
upstream bug, I would suggest applying this fix on our flex package.
Alternatively package a "flex-for-grub" variant, but that's not very
re-usable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-03-06 18:49 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 9:05 Let’s freeze and build ‘core-updates’! Ludovic Courtès
2017-02-14 15:00 ` Marius Bakke
2017-02-14 16:22 ` Ludovic Courtès
2017-02-21 14:03 ` Marius Bakke
2017-02-21 16:27 ` Andreas Enge
2017-02-21 17:32 ` Leo Famulari
2017-02-21 17:41 ` Leo Famulari
2017-03-06 9:19 ` Ludovic Courtès
2017-03-06 12:31 ` Marius Bakke
2017-03-06 15:39 ` Ludovic Courtès
2017-03-06 22:26 ` Leo Famulari
2017-03-07 13:59 ` Ludovic Courtès
2017-03-08 5:43 ` Leo Famulari
2017-03-08 8:44 ` Ludovic Courtès
2017-03-08 9:03 ` Leo Famulari
2017-03-06 18:42 ` Leo Famulari
2017-03-06 18:49 ` Marius Bakke [this message]
2017-03-06 18:54 ` Marius Bakke
2017-03-06 19:13 ` Leo Famulari
2017-03-06 18:54 ` Leo Famulari
2017-02-27 20:30 ` core-updates frozen! Leo Famulari
2017-03-02 17:34 ` Leo Famulari
2017-03-03 0:02 ` Marius Bakke
2017-03-03 18:27 ` Leo Famulari
2017-03-03 18:33 ` Marius Bakke
2017-03-03 18:53 ` Leo Famulari
2017-03-09 22:33 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-10 21:46 ` Marius Bakke
2017-03-11 3:10 ` Leo Famulari
2017-03-11 17:21 ` core-updates: Python build failures Leo Famulari
2017-03-11 19:50 ` Marius Bakke
2017-03-12 0:05 ` Leo Famulari
2017-03-12 17:44 ` Marius Bakke
2017-03-13 8:30 ` Ludovic Courtès
2017-03-20 18:41 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-21 11:16 ` julien lepiller
2017-03-21 17:52 ` Leo Famulari
2017-03-21 21:19 ` Julien Lepiller
2017-03-21 22:02 ` Leo Famulari
2017-03-21 22:02 ` Ricardo Wurmus
2017-03-23 11:08 ` Thomas Danckaert
2017-03-23 12:38 ` Ricardo Wurmus
2017-03-29 13:41 ` Marius Bakke
2017-03-29 14:05 ` Marius Bakke
2017-03-29 20:49 ` Leo Famulari
2017-03-29 20:51 ` Leo Famulari
2017-03-30 6:23 ` Ricardo Wurmus
2017-03-30 8:36 ` Ricardo Wurmus
2017-03-30 9:18 ` Thomas Danckaert
2017-04-01 22:30 ` Ludovic Courtès
2017-04-01 23:09 ` Leo Famulari
2017-04-03 7:43 ` Ricardo Wurmus
2017-04-02 15:20 ` Marius Bakke
2017-04-02 15:42 ` Ricardo Wurmus
2017-04-02 21:23 ` Marius Bakke
2017-04-02 21:18 ` Marius Bakke
2017-04-02 22:39 ` ‘core-updates’ merged! Ludovic Courtès
2017-04-02 21:20 ` Greenisland & SDDM Ludovic Courtès
2017-04-02 21:31 ` Marius Bakke
2017-04-02 22:12 ` Ludovic Courtès
[not found] <mailman.60210.1490049834.22737.guix-devel@gnu.org>
2017-03-21 14:22 ` Let?s freeze and build ?core-updates?! rennes
2017-03-21 18:28 ` Leo Famulari
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=87efya44vt.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--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.