From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Prevor Subject: bug#24220: "failed to unpack source code" on guix pull Date: Sun, 14 Aug 2016 09:02:37 -0400 Message-ID: <567c8b751b63d6851aeab6afa91ca878@sdf.org> References: <20160814052735.GA13020@thebird.nl> <87r39rrajs.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYv4G-0006Ov-Lp for bug-guix@gnu.org; Sun, 14 Aug 2016 09:03:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYv4A-0007aU-S8 for bug-guix@gnu.org; Sun, 14 Aug 2016 09:03:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:59117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYv4A-0007aQ-OR for bug-guix@gnu.org; Sun, 14 Aug 2016 09:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bYv4A-0006Vk-Cx for bug-guix@gnu.org; Sun, 14 Aug 2016 09:03:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r39rrajs.fsf@we.make.ritual.n0.is> 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: 24220@debbugs.gnu.org Hi ng0, On 2016-08-14 04:59, ng0 wrote: > This was caused by a patch I sent which was applied on master. > Guix error messages could be more natural, as for me the error output I > got seemed just verbose and I decided it was okay to send this in. The > commit has since then be reverted and I will send in an updated patch. > > Simpler explanation: a license I added was already inherited by another > loaded module, this caused some "hick up" and make broke (while it did > not break locally on my side). > >>> P.S. I'm not subscribed to bug-guix, so please CC me in any >>> responses to this thread! > > Can you please close this bug (see the message you got from > debbugs.gnu.org with instructions) when it is done. > For me master builds again, so I assume this bug is done? I can do that once I get a message (I haven't yet), but for me I'm still having the guix pull issue. Are there any steps that need to be done by me to ensure I'm getting the latest master branch with the fix? If not, when would the fix be applied? Thanks, --- Harry Prevor