From: Timothy Sample <samplet@ngyro.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org, 36807@debbugs.gnu.org,
Robert Vollmert <rob@vllmrt.net>
Subject: Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)
Date: Wed, 07 Aug 2019 23:47:48 -0400 [thread overview]
Message-ID: <874l2spbbv.fsf@ngyro.com> (raw)
In-Reply-To: <87k1bp1aut.fsf@devup.no> (Marius Bakke's message of "Wed, 07 Aug 2019 13:19:38 +0200")
Hi Robert and Marius,
Marius Bakke <mbakke@fastmail.com> writes:
> Robert Vollmert <rob@vllmrt.net> writes:
>
>> Oh, I meant to ask:
>>
>> On 6. Aug 2019, at 06:29, Timothy Sample <samplet@ngyro.com> wrote:
>>
>>> I think it makes sense to wait for the core-updates merge (which
>>> shouldn’t be too far out).
>>
>> Why? Shouldn’t substitutes be available since CI built the branch successfully?
>
> core-updates is still waiting for a full-rebuild change, and the CI is
> currently unusable, so merging might take a month or more still.
>
> Getting this in 'master' meanwhile would be great, especially for i686
> users :-)
I stand corrected! :) I cherry-picked these commits from core-updates.
Thanks for chiming in, Marius.
-- Tim
next prev parent reply other threads:[~2019-08-08 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F5E8BA95-BE79-4579-B881-AE0862B69D3A@vllmrt.net>
[not found] ` <87muh2ckdn.fsf@ngyro.com>
2019-08-01 16:23 ` Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages) Robert Vollmert
2019-08-06 4:29 ` Timothy Sample
2019-08-06 7:04 ` Robert Vollmert
2019-08-08 3:42 ` Timothy Sample
2019-08-06 7:49 ` Robert Vollmert
2019-08-07 11:19 ` Marius Bakke
2019-08-08 3:47 ` Timothy Sample [this message]
2019-08-08 13:12 ` Marius Bakke
2019-08-08 13:42 ` Robert Vollmert
2019-08-08 15:54 ` Timothy Sample
2019-08-08 16:08 ` Marius Bakke
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=874l2spbbv.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=36807@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=rob@vllmrt.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).