unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: 27556@debbugs.gnu.org
Subject: bug#27556: libpng has wrong hash. [Fwd: Re: why has the hash for libpng-apng 1.6.28 changed?]
Date: Sun, 23 Jul 2017 10:15:47 +0000	[thread overview]
Message-ID: <20170723101547.3oi5uu2xhi625njp@abyayala> (raw)
In-Reply-To: <20170702201344.dvqpopouvpbzr4c2@abyayala>

[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]

----- Forwarded message -----

> 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?
> 
> Hi,
> 
> I calculated the hash for libpng-apng files on my local orignals.
> 
> md5sum
> 9f2b36bccf89c5f4097111f0f73c1798  libpng-1.6.28-apng.patch.README.txt
> fca7c6d87c8352e645facefc2e1dd153  libpng-1.6.28-apng.patch.gz
> 
> sha1sum
> cb620589ecf9c28a4ecc00e6225dd41ca660a959  libpng-1.6.28-apng.patch.README.txt
> 4fa952f5ad374fce8d478b7e54ee4298a0b8d159  libpng-1.6.28-apng.patch.gz
> 
> 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
> 
> That values equals on sourceforge.net.
> https://sourceforge.net/projects/libpng-apng/files/libpng16/1.6.28/
> 
> I don't really understand what happend, but it look just fine.
> 
> Cheers,
> ---
> daisuken@users.sourceforge.net
> 
> 
> From: ng0
> Subject: why has the hash for libpng-apng 1.6.28 changed?
> Date: Sat, 22 Jul 2017 09:06:28 +0000
> Message-ID: <20170722090628.rvnmyvafhkgrnl7t@abyayala>
> 
> ng0> Hi,
> ng0> 
> ng0> I noticed that the hash for libpng-apng at the source changed, for version 1.6.28.
> ng0> 
> ng0> Can you tell me what happened? As libpng-apng is a recent addition in our
> ng0> system (GNU Guix) I'm not yet aware of any bad or good practices or the
> ng0> lack of them libpng-apng applies.
> ng0> My current guess is that you changed the tarball in place, or that
> ng0> Sourceforge changed it in place. We'll diff the tarball contents and see
> ng0> what changed, but a maintainers reply will also be good.
> ng0> 
> ng0> Greetings,
> ng0> -- 
> ng0> ng0
> ng0> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> ng0> GnuPG: https://n0is.noblogs.org/my-keys
> ng0> https://www.infotropique.org https://krosos.org
> 

----- End forwarded message -----

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-07-23 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02 20:13 bug#27556: libpng has wrong hash ng0
2017-07-04 23:59 ` Leo Famulari
2017-07-05  7:57   ` ng0
2017-07-12 15:25 ` bug#27556: Fix for bug#27556 ng0
2017-07-22  9:15   ` ng0
2017-07-23 10:15 ` ng0 [this message]
2017-07-25 18:49   ` bug#27556: libpng has wrong hash. [Fwd: Re: why has the hash for libpng-apng 1.6.28 changed?] Leo Famulari
2017-07-26  6:56     ` ng0
2017-07-26  8:40       ` Efraim Flashner
2017-07-30  9:37         ` ng0
2017-07-31 14:34           ` Leo Famulari
2017-07-31 14:39             ` ng0
2017-08-01 15:47               ` ng0
2017-08-02 15:25                 ` Leo Famulari

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=20170723101547.3oi5uu2xhi625njp@abyayala \
    --to=ng0@infotropique.org \
    --cc=27556@debbugs.gnu.org \
    /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).