GNU bug report logs -
#35359
docker-image produces corrupt tar
Previous Next
Reported by: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Date: Sun, 21 Apr 2019 13:45:02 UTC
Severity: normal
Found in version 0.16.0
Done: Ricardo Wurmus <rekado <at> elephly.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
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.
This bug report was last modified 6 years and 86 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.