From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#27556: libpng has wrong hash. [Fwd: Re: why has the hash for libpng-apng 1.6.28 changed?] Date: Tue, 25 Jul 2017 14:49:36 -0400 Message-ID: <20170725184936.GA32001@jasmine.lan> References: <20170702201344.dvqpopouvpbzr4c2@abyayala> <20170723101547.3oi5uu2xhi625njp@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1da4uE-0006XV-A2 for bug-guix@gnu.org; Tue, 25 Jul 2017 14:50:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1da4uB-0002Fg-7b for bug-guix@gnu.org; Tue, 25 Jul 2017 14:50:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53603) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1da4uA-0002FR-Sk for bug-guix@gnu.org; Tue, 25 Jul 2017 14:50:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1da4uA-0005om-F3 for bug-guix@gnu.org; Tue, 25 Jul 2017 14:50:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20170723101547.3oi5uu2xhi625njp@abyayala> 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: 27556@debbugs.gnu.org --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 23, 2017 at 10:15:47AM +0000, ng0 wrote: > ----- Forwarded message ----- >=20 > > Date: Sun, 23 Jul 2017 18:21:19 +0900 (JST) > > To: ng0 > > Cc: daisuken@users.sourceforge.net > > Subject: Re: why has the hash for libpng-apng 1.6.28 changed? > >=20 > > Hi, > >=20 > > I calculated the hash for libpng-apng files on my local orignals. > >=20 > > md5sum > > 9f2b36bccf89c5f4097111f0f73c1798 libpng-1.6.28-apng.patch.README.txt > > fca7c6d87c8352e645facefc2e1dd153 libpng-1.6.28-apng.patch.gz > >=20 > > sha1sum > > cb620589ecf9c28a4ecc00e6225dd41ca660a959 libpng-1.6.28-apng.patch.READ= ME.txt > > 4fa952f5ad374fce8d478b7e54ee4298a0b8d159 libpng-1.6.28-apng.patch.gz > >=20 > > Local file time stamps are > > 2017-01-06 21:02:10.938833896 +0900 libpng-1.6.28-apng.patch.README.txt > > 2017-01-06 21:02:10.938833896 +0900 libpng-1.6.28-apng.patch.gz > >=20 > > That values equals on sourceforge.net. > > https://sourceforge.net/projects/libpng-apng/files/libpng16/1.6.28/ > >=20 > > I don't really understand what happend, but it look just fine. > >=20 > > Cheers, > > --- > > daisuken@users.sourceforge.net Okay, this doesn't help us, so we need to inspect the different tarballs ourselves. Do you have an old copy of the patch you can share? --/04w6evG8XlLl3ft Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAll3ksAACgkQJkb6MLrK fwjnthAArilFxdbi8a87Yz+8/6fTejoWf5zBjFxmR3V4003GrqlBoLvYrrcdI8/4 Tgyiov4WT99Ns1DuVrXfRESoReb9bnpWVD6X/dU4+d/L+ECNHfRFAye1ygBgOzsm 5TPWyQJFAl+kqthEG+vy1RKDiysfN+B4JLRvSGwvjBlSg9pll7VhlKawzAIGznFx v78yoqvHtuaEjf1WI7BypHPMfwCGSEoBju2wGlE/iIl9F4sanDTgIqrxFhYa8zbr dcMnEVg4PhtTaxOZoQz5B/5WFdmUffW9tVH1c0kG79m9AeCsFFhLpy33Dihb/Io5 9LXiYW2NCQOi2zjmpWDptlXLF3//Cmdcp9Hu/2HdrifttXLGn0w6ouX9Bu+ThqdS t/KVwXkawYDubmE9d+HU48euHjCKSS22V4xtd/lcFShnZcuRjb7wQBIQuLinKF2g 6AmLOdjQwHEwD09vXhcMJnvstF7P1QV5Rw4W+NZoRh+PvqaHQDHWZnufnR1f1Ofe qkn1as2VsGUye6CkzLZjc+EM0HOT1tMkWu3WKJJFmbaAq5Vi2oksGdTOSupPtqxX K3uEe65yYzobe3nFuJppB2GclVthG+UIsxSpq0oNxYvqD9t3P7kM4MZn2HsuG/1Y I6jLvnpCbWybqm8BrJ2/eHdFMANTHd0Qt/MS3SXZs65SKNiaWXU= =E+P+ -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--