From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Woodcroft Subject: Re: Package ruby-ansi appears to be broken Date: Wed, 27 Apr 2016 22:45:23 +1000 Message-ID: <5720B463.8040700@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avOqU-0007nm-Cd for guix-devel@gnu.org; Wed, 27 Apr 2016 08:45:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1avOqQ-0007Qr-0o for guix-devel@gnu.org; Wed, 27 Apr 2016 08:45:34 -0400 Received: from mail-pa0-x242.google.com ([2607:f8b0:400e:c03::242]:34978) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avOqP-0007Qf-Q3 for guix-devel@gnu.org; Wed, 27 Apr 2016 08:45:29 -0400 Received: by mail-pa0-x242.google.com with SMTP id zy2so5441536pac.2 for ; Wed, 27 Apr 2016 05:45:29 -0700 (PDT) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Rob Syme , "guix-devel@gnu.org" Hi Rob, On 27/04/16 20:39, Rob Syme wrote: > Hi all > > Running `guix environment --ad-hoc ruby-ansi` fails for me (and > others). The package definition uses the ruby-build-system but fetches > the tar.gz directly from github instead of from rubygems. I'll try and > find time to have a closer look, but if Ricardo has any time, he might > be able to debug it faster than me. I think this the error is very similar to that described here, and occurs during 'gem install' https://github.com/rubygems/rubygems/issues/1448 which is fixed in rubygems 2.5.2. Today a new version of ruby was released, but sadly, comes with rubygems 2.5.1. So, I think this means we will need to either incorporate the patch(es) that fix this into the ruby package, or package rubygems alongside ruby somehow. Or, since there is only a problem during build time, perhaps clobber the gem from the ruby package with a rubygems package during build time. Unless you have any better ideas? Thanks for reporting this. ben