From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timothy Sample Subject: bug#36084: ghc-tasty/ghc-clock circular dependency breaking is broken Date: Tue, 16 Jul 2019 15:11:00 -0400 Message-ID: <87a7dddccb.fsf@ngyro.com> References: <4CEAB7EC-5859-4915-B381-C0AFFD93ABC5@vllmrt.net> <87ef2qdnl7.fsf@ngyro.com> <9C66C61B-16D7-4A01-A35D-85984FF819C4@vllmrt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44969) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnSrr-0001SO-Ao for bug-guix@gnu.org; Tue, 16 Jul 2019 15:12:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnSrq-0001T1-4O for bug-guix@gnu.org; Tue, 16 Jul 2019 15:12:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42337) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnSrq-0001Sv-0k for bug-guix@gnu.org; Tue, 16 Jul 2019 15:12:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hnSrp-0002B1-RE for bug-guix@gnu.org; Tue, 16 Jul 2019 15:12:01 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <9C66C61B-16D7-4A01-A35D-85984FF819C4@vllmrt.net> (Robert Vollmert's message of "Tue, 16 Jul 2019 18:17:26 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Robert Vollmert Cc: 36084-done@debbugs.gnu.org Hi, Robert Vollmert writes: >> On 16. Jul 2019, at 17:08, Timothy Sample wrote: >>=20 >> Hi Robert, >>=20 >> After looking at this and your patch at , >> I=E2=80=99m wondering if it works as long as we make sure the versions m= atch. >> Can we just inherit the current =E2=80=9Cghc-clock=E2=80=9D, disable its= tests, and call >> it =E2=80=9Cghc-clock-bootstrap=E2=80=9D? Is the Cabal consistency chec= king too clever >> for that? >>=20 >> If that doesn=E2=80=99t work, can you explain why the method you propose= d above >> doesn=E2=80=98t work? It seems a little simpler than your patch. In fa= ct, >> maybe we could live with the main =E2=80=9Cghc-tasty=E2=80=9D package be= ing built >> without =E2=80=9Cghc-clock=E2=80=9D (via the flag you mentioned). > > I tried the direct approach again, and this time it worked. Posted an > updated patch. > > I believe this should be fine, since GHCs builds should be deterministic. It looks like this is a common idiom for us, so I=E2=80=99m pretty confiden= t, too. Fixed in 71e5d425c9b9e108ebdd06d13de45b56dddd9ef5. Thanks! -- Tim