unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: rendaw <7e9wc56emjakcm@s.rendaw.me>
Cc: 35359-done@debbugs.gnu.org
Subject: bug#35359: docker-image produces corrupt tar
Date: Mon, 22 Apr 2019 19:12:05 +0200	[thread overview]
Message-ID: <871s1u6k2i.fsf@elephly.net> (raw)
In-Reply-To: <752d885f-f513-49a0-b901-ab54c341e939@s.rendaw.me>


rendaw <7e9wc56emjakcm@s.rendaw.me> writes:

> On 4/23/19 1:10 AM, Ricardo Wurmus wrote:
>> rendaw <7e9wc56emjakcm@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.

Excellent.  Thanks for the confirmation!

Closing.

-- 
Ricardo

      reply	other threads:[~2019-04-22 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 13:44 bug#35359: docker-image produces corrupt tar rendaw
2019-04-21 20:35 ` Ludovic Courtès
2019-04-22 11:55   ` rendaw
2019-04-22 12:06     ` Ricardo Wurmus
2019-04-22 14:35       ` rendaw
2019-04-22 16:10         ` Ricardo Wurmus
2019-04-22 16:53           ` rendaw
2019-04-22 17:12             ` Ricardo Wurmus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871s1u6k2i.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=35359-done@debbugs.gnu.org \
    --cc=7e9wc56emjakcm@s.rendaw.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).