From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: Merge branch 'origin/core-updates-next' into core-updates
Date: Wed, 06 Jun 2018 22:07:33 -0400 [thread overview]
Message-ID: <87po13z6vu.fsf@netris.org> (raw)
In-Reply-To: <87h8mf1kx6.fsf@netris.org> (Mark H. Weaver's message of "Wed, 06 Jun 2018 20:48:21 -0400")
Hi Ricardo,
Mark H Weaver <mhw@netris.org> writes:
> rekado@elephly.net (Ricardo Wurmus) writes:
>
>> rekado pushed a commit to branch core-updates
>> in repository guix.
>>
>> commit 87096247567ac0d4aac3fc5a7a1e150d307c5b80
>> Merge: 116ca65 5e6bd3e
>> Author: Ricardo Wurmus <rekado@elephly.net>
>> 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
prev parent reply other threads:[~2018-06-07 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180606210241.30122.49748@vcs0.savannah.gnu.org>
[not found] ` <20180606210242.E94BC201F1@vcs0.savannah.gnu.org>
2018-06-07 0:48 ` 01/01: Merge branch 'origin/core-updates-next' into core-updates Mark H Weaver
2018-06-07 0:58 ` Mark H Weaver
2018-06-07 2:07 ` Mark H Weaver [this message]
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=87po13z6vu.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).