GNU bug report logs - #35359
docker-image produces corrupt tar

Previous Next

Full log

Message #23 received at 35359 <at> debbugs.gnu.org (full text, mbox):

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 35359 <at> debbugs.gnu.org
Subject: Re: bug#35359: docker-image produces corrupt tar
Date: Tue, 23 Apr 2019 01:53:50 +0900

On 4/23/19 1:10 AM, Ricardo Wurmus wrote:
> rendaw <7e9wc56emjakcm <at> s.rendaw.me> writes:
>
>> Thanks! I just did `guix pull` and forced an image rebuild (by changing
>> host-name)
> Changing the host name is not needed.  After getting the new Guix most
> of the packages that should end up in the image would be updated
> anyway.
>
>> but I get the same tar error.
> I’m guessing that you are not actually using the pulled Guix because
> your shell may have cached the former location of the “guix”
> executable.  Please try again with ~/.config/guix/current/bin/guix
> instead of just “guix”.
>
> You can also run “hash guix” in Bash to invalidate the cache.
Thanks, that was the issue.  I replaced the path and now the build uses
fresh packages and the tar is not corrupt.  This can be closed.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.