From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Woodcroft Subject: Re: Hash mismatch for Python 2.7.10 (x86_64-linux) Date: Sun, 3 Apr 2016 07:11:13 +1000 Message-ID: <57003571.5050302@uq.edu.au> References: <20160319152540.GA29638@thebird.nl> <87d1qqf9i8.fsf@gnu.org> <20160321154731.GB26140@jasmine> <87lh5b690v.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1amSpM-0003hI-FY for guix-devel@gnu.org; Sat, 02 Apr 2016 17:11:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1amSpJ-0002XH-9e for guix-devel@gnu.org; Sat, 02 Apr 2016 17:11:28 -0400 In-Reply-To: <87lh5b690v.fsf_-_@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: =?UTF-8?Q?Ludovic_Court=c3=a8s?= , Leo Famulari Cc: guix-devel@gnu.org On 22/03/16 03:22, Ludovic Court=C3=A8s wrote: > Leo Famulari skribis: > >> Can you take a look at python-2.7.10? >> >> Specifically, /gnu/store/4bs4mx6xyx0jx9827vmmbxyhjln7cmcv-python-2.7.1= 0 >> >> This is from "ifur" on #guix: >> http://paste.lisp.org/display/311051 > This is an =E2=80=9Cinteresting=E2=80=9D case. There=E2=80=99s indeed = a hash mismatch between > that narinfo and the nar (hydra.gnu.org and mirror.guixsd.org provide > the exact same narinfo and nar though): I think perhaps tcl might be a similar case? It has non-zero size so=20 wasn't picked up in Ludo's latest sweep. >From http://mirror.guixsd.org/nar/6kvy3ryb04nl49wwdy0dmhhfnfbwrmna-tcl-8.= 6.4 Downloading 6kvy3r...-tcl-8.6.4 (24.8MiB installed)... http://mirror.guixsd.org/nar/6kvy3ryb04nl49wwdy0dmhhfnfbwrmna-tcl-8.6.4= 710KiB/s 00:03 | 1.7MiB transferredd bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file =3D (stdin), output file =3D (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. But it is not interesting in the way python2 is: $ wget -q -O -=20 https://hydra.gnu.org/6kvy3ryb04nl49wwdy0dmhhfnfbwrmna.narinfo |grep Hash NarHash: sha256:03dm95xz885jhy57b2r5hqh7v4dfwbpdxj1jbfxc1z99pvwnx07j $ wget -q -O -=20 https://hydra.gnu.org/nar/6kvy3ryb04nl49wwdy0dmhhfnfbwrmna-tcl-8.6.4 |=20 bunzip2 | guix hash /dev/stdin 03dm95xz885jhy57b2r5hqh7v4dfwbpdxj1jbfxc1z99pvwnx07j ben