From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#15194: hop FTBFS Date: Thu, 29 Aug 2013 21:35:54 -0400 Message-ID: <87k3j43qpx.fsf@tines.lan> References: <87sixw5dxx.fsf@tines.lan> <87mwo3mtci.fsf@gnu.org> <87k3j75glw.fsf@tines.lan> <87haebgo1v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36328) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFDe8-0006GZ-VO for bug-guix@gnu.org; Thu, 29 Aug 2013 21:37:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VFDe3-0004OE-HF for bug-guix@gnu.org; Thu, 29 Aug 2013 21:37:08 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:49607) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFDe3-0004OA-Do for bug-guix@gnu.org; Thu, 29 Aug 2013 21:37:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VFDe2-0008VR-6V for bug-guix@gnu.org; Thu, 29 Aug 2013 21:37:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87haebgo1v.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 27 Aug 2013 17:18:20 +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-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 15194@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> ludo@gnu.org (Ludovic Court=C3=A8s) writes: >> >>> It turns out Hop & Bigloo have to be upgraded in lockstep. I believe >>> a new Hop version is around the corner, so I=E2=80=99m tempted to just = wait >>> for that. >>> >>> WDYT? >> >> I think we should find a solution that doesn't lead to the 'hop' build >> being broken every time 'bigloo' is upgraded before 'hop'. >> >> An obvious solution would be to keep two versions of 'bigloo': the >> latest release, and the release that corresponds to the latest release >> of 'hop'. Hopefully these would be the same most of the time. > > Yes, that sounds like a plan. And hopefully the =E2=80=9Cold=E2=80=9D Bi= gloo would just > differ by its =E2=80=98version=E2=80=99 and =E2=80=98source=E2=80=99 fiel= ds, which is easily handled. > > Would you like to propose a patch? I don't actually use 'bigloo' or 'hop' myself, and right now I have my hands full with a lot of pending work for Guile, so I'd prefer to let someone else take care of this. I only know about this problem because I've been building as many Guix packages as possible, for testing purposes. Regards, Mark