From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#24220: "failed to unpack source code" on guix pull Date: Sun, 14 Aug 2016 14:27:27 +0000 Message-ID: <87popbfmsw.fsf@we.make.ritual.n0.is> References: <20160814052735.GA13020@thebird.nl> <87r39rrajs.fsf@we.make.ritual.n0.is> <567c8b751b63d6851aeab6afa91ca878@sdf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36924) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYwOV-0001Fw-EC for bug-guix@gnu.org; Sun, 14 Aug 2016 10:28:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYwOQ-00046n-5h for bug-guix@gnu.org; Sun, 14 Aug 2016 10:28:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:59673) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYwOQ-00046j-1r for bug-guix@gnu.org; Sun, 14 Aug 2016 10:28:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bYwOP-0000BH-TZ for bug-guix@gnu.org; Sun, 14 Aug 2016 10:28:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <567c8b751b63d6851aeab6afa91ca878@sdf.org> 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: Harry Prevor , 24220@debbugs.gnu.org Harry Prevor writes: > 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 > > > Curious, I thought the normal behavior of debbugs was to send instructions with how bugs are closed etc. Sometimes there's a very long delay (I noticed 1-2 days delay with bugs being opened). Can you describe your problem more in detail and how to reproduce? I've just run a `guix pull` and the build succeeded for amd64. -- ♥Ⓐ ng0 For non-prism friendly talk find me on http://www.psyced.org