From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#35359: docker-image produces corrupt tar Date: Mon, 22 Apr 2019 19:12:05 +0200 Message-ID: <871s1u6k2i.fsf@elephly.net> References: <87a7gj2j13.fsf@gnu.org> <875zr66y7m.fsf@elephly.net> <8736ma6mwp.fsf@elephly.net> <752d885f-f513-49a0-b901-ab54c341e939@s.rendaw.me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIdDb-0002Hr-Ob for bug-guix@gnu.org; Mon, 22 Apr 2019 13:59:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hIdDa-00011V-SU for bug-guix@gnu.org; Mon, 22 Apr 2019 13:59:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:38000) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hIdDa-00011E-LG for bug-guix@gnu.org; Mon, 22 Apr 2019 13:59:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hIdDa-0001iM-Jd for bug-guix@gnu.org; Mon, 22 Apr 2019 13:59:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-reply-to: <752d885f-f513-49a0-b901-ab54c341e939@s.rendaw.me> 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: rendaw <7e9wc56emjakcm@s.rendaw.me> Cc: 35359-done@debbugs.gnu.org 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=E2=80=99m guessing that you are not actually using the pulled Guix bec= ause >> your shell may have cached the former location of the =E2=80=9Cguix=E2= =80=9D >> executable. Please try again with ~/.config/guix/current/bin/guix >> instead of just =E2=80=9Cguix=E2=80=9D. >> >> You can also run =E2=80=9Chash guix=E2=80=9D in Bash to invalidate the c= ache. > 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. --=20 Ricardo