mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] Wrong md5sum for klibc 1.5.25 tarball in rule file
@ 2013-01-18 17:17 Dennis.Herbrich
  2013-01-21 11:16 ` Michael Olbrich
  0 siblings, 1 reply; 2+ messages in thread
From: Dennis.Herbrich @ 2013-01-18 17:17 UTC (permalink / raw)
  To: ptxdist

Greetings! 

Downloading klibc-1.5.25[0] as defined in the current ptxdist-git 
rulefile yields a file of 611938 bytes and an md5sum of 
0c11c9c9d0c8b9e55c6689f43cee5a23. 

However, the rulefile expects 9ff935403b6f9193aaf52dc53769f290, which is 
identical to the hash referred to by some other distributions like 
Ubuntu, from where I got a copy of the "correct" file[1] with a size of 
611955 bytes and the expected md5sum. 

Following a hunch, I gunzipped both files, and lo and behold, the 
resulting tar is actually identical, so there's likely no malice 
involved: 

[deh@vulpes ~]$ md5sum klibc*
313ed22fa9ef8586db473945248f5de2 klibc_1.5.25.orig.tar
313ed22fa9ef8586db473945248f5de2 klibc-1.5.25.tar 

Now, what I'd like to achieve with this email is to warn about this 
issue, and, well, a fixed md5sum in the next release of ptxdist. ;) 
Unfortunately I cannot tell WHY the package has been changed,
causing this mismatch. If anybody knows a reason, I'd appreciate
to learn about it!

Best regards,
  Dennis 

[0]:http://www.kernel.org/pub/linux/libs/klibc/1.5/klibc-1.5.25.tar.gz
[1]:https://launchpad.net/ubuntu/+archive/primary/+files/klibc_1.5.25.orig.tar.gz

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ptxdist] Wrong md5sum for klibc 1.5.25 tarball in rule file
  2013-01-18 17:17 [ptxdist] Wrong md5sum for klibc 1.5.25 tarball in rule file Dennis.Herbrich
@ 2013-01-21 11:16 ` Michael Olbrich
  0 siblings, 0 replies; 2+ messages in thread
From: Michael Olbrich @ 2013-01-21 11:16 UTC (permalink / raw)
  To: ptxdist

Hi,

On Fri, Jan 18, 2013 at 06:17:20PM +0100, Dennis.Herbrich@hytera.de wrote:
> Downloading klibc-1.5.25[0] as defined in the current ptxdist-git 
> rulefile yields a file of 611938 bytes and an md5sum of 
> 0c11c9c9d0c8b9e55c6689f43cee5a23. 
> 
> However, the rulefile expects 9ff935403b6f9193aaf52dc53769f290, which is 
> identical to the hash referred to by some other distributions like 
> Ubuntu, from where I got a copy of the "correct" file[1] with a size of 
> 611955 bytes and the expected md5sum. 
> 
> Following a hunch, I gunzipped both files, and lo and behold, the 
> resulting tar is actually identical, so there's likely no malice 
> involved: 
> 
> [deh@vulpes ~]$ md5sum klibc*
> 313ed22fa9ef8586db473945248f5de2 klibc_1.5.25.orig.tar
> 313ed22fa9ef8586db473945248f5de2 klibc-1.5.25.tar 
> 
> Now, what I'd like to achieve with this email is to warn about this 
> issue, and, well, a fixed md5sum in the next release of ptxdist. ;) 
> Unfortunately I cannot tell WHY the package has been changed,
> causing this mismatch. If anybody knows a reason, I'd appreciate
> to learn about it!

If you look at http://www.kernel.org/pub/linux/libs/klibc/1.5/ you'll see
that all versions of klibc got updated on 31-May-2012. Maybe related to the
kernel.org hack? Anyways, the content is identical to the one with the old
md5sum. I've updated the md5sum in ptxdist master.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-01-21 11:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-18 17:17 [ptxdist] Wrong md5sum for klibc 1.5.25 tarball in rule file Dennis.Herbrich
2013-01-21 11:16 ` Michael Olbrich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox