[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/01: Merge branch 'origin/core-updates-next' into core-updates
From: |
Mark H Weaver |
Subject: |
Re: 01/01: Merge branch 'origin/core-updates-next' into core-updates |
Date: |
Wed, 06 Jun 2018 22:07:33 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hi Ricardo,
Mark H Weaver <address@hidden> writes:
> address@hidden (Ricardo Wurmus) writes:
>
>> rekado pushed a commit to branch core-updates
>> in repository guix.
>>
>> commit 87096247567ac0d4aac3fc5a7a1e150d307c5b80
>> Merge: 116ca65 5e6bd3e
>> Author: Ricardo Wurmus <address@hidden>
>> Date: Wed Jun 6 23:01:48 2018 +0200
>>
>> Merge branch 'origin/core-updates-next' into core-updates
>
> Umm, did you intend to push this to the 'core-updates' branch on
> Savannah? Core-updates has been frozen for months, and is almost
> completely built by Hydra. It looks like this would entail rebuilding
> the entire branch from scratch again.
Ah, I just noticed that you merged 'core-updates' into 'master', so now
this makes sense. I restored 'core-updates' to the way you had left it.
Personally, I think this merge was premature, with over 900 new failures
on core-updates compared to the previous master branch. Neither armhf
nor i686 would be able to build a typical system now, because armhf is
missing e2fsprogs and i686 is missing GRUB. armhf is also missing most
of its GUI programs due to <https://bugs.gnu.org/31708>, and i686 is
missing gst-plugins-base and thus GNOME and many other important GUI
programs and desktops.
Mark