From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: mismatch of source tar ball hash Date: Sun, 28 Oct 2018 16:11:53 +0100 Message-ID: References: <20181028122333.063da88d@jasniac.instanton> <20181028123031.4d3156ec@jasniac.instanton> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGmjW-0005Nq-VB for guix-devel@gnu.org; Sun, 28 Oct 2018 11:12:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gGmjW-0001j5-7Z for guix-devel@gnu.org; Sun, 28 Oct 2018 11:12:06 -0400 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]:41305) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gGmjV-0001iu-V3 for guix-devel@gnu.org; Sun, 28 Oct 2018 11:12:06 -0400 Received: by mail-oi1-x231.google.com with SMTP id i10-v6so4914593oik.8 for ; Sun, 28 Oct 2018 08:12:05 -0700 (PDT) In-Reply-To: <20181028123031.4d3156ec@jasniac.instanton> 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" To: marco@hulten.org Cc: Guix-devel Hello Marco, Marco van Hulten ezt =C3=ADrta (id=C5=91pont: 2018. okt.= 28., V, 15:50): > > update=E2=80=94 > > Je 28 okt 12:23 skribis Marco: > > Hi=E2=80=94 > > > > When I try to install calcurse, the hash of the downloaded file is > > different from the one specified in the package: > > [...] > > I happened to find the same tar ball that I downloaded on 5 April 2018. > As this is quite some time ago, my *guess* is that the issue is related > to Guix instead of calcurse.org. > > =E2=80=94Marco > A few things you could check: 1. the tarball is the same as checked by diff or by diffoscope? Diffoscope might reveal some things, such as metadata differences, that can't be seen by diff alone. 2. can you have a look at the last modification of the hash value in question, for example by using git blame, or simply git log, as there tend to be good log entries, so this should be easy to find. Best regards, g_bor