On Wed, 22 Apr 2009, christopher floess wrote:
Hi, I'm doing some research into the workings of yum, and one of the
things I'm stuck on is how the hash for a package is generated. As an
example, I took a look the information for nano-2.0.6-4.fc9.i386.rpm
In http://fedora.ifc.unam.mx/releases/10/Everything/i386/os/repodata/primary.xml
.gz this rpm has a sha hash of
7373fda2bbc183c01afe9ccc78411fec9fe52833. However, when I run sha1sum
on the file I get fec49e69aaf31cac8d7f0d7759f70f1d95355bfa and when I
get sha256sum on it, I get
96f4d11cf5cd66748e47f83639dae1e1f638792757944e32eeb810f3553ad, so I'm
wondering how that number was computed.
$ wget
http://fedora.ifc.unam.mx/releases/10/Everything/i386/os/Packages/nano-2.0.6-4.fc9.i386.rpm
--2009-04-23 00:23:01--
http://fedora.ifc.unam.mx/releases/10/Everything/i386/os/Packages/nano-2.0.6-4.fc9.i386.rpm
Resolving fedora.ifc.unam.mx... 132.248.16.8
Connecting to fedora.ifc.unam.mx|132.248.16.8|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 551005 (538K) [application/octet-stream]
Saving to: `nano-2.0.6-4.fc9.i386.rpm'
100%[=================================================================================>]
551,005 257K/s in 2.1s
2009-04-23 00:23:04 (257 KB/s) - `nano-2.0.6-4.fc9.i386.rpm' saved
[551005/551005]
$ rpm -K -v nano-2.0.6-4.fc9.i386.rpm
nano-2.0.6-4.fc9.i386.rpm:
Header V3 DSA signature: OK, key ID 4ebfc273
Header SHA1 digest: OK (0d1e0fb3a43b158288cd9d9b332f820bdb2953f9)
MD5 digest: OK (516a2031a87a3676f27b5afbdf659e4b)
V3 DSA signature: OK, key ID 4ebfc273
$ sha1sum nano-2.0.6-4.fc9.i386.rpm
7373fda2bbc183c01afe9ccc78411fec9fe52833 nano-2.0.6-4.fc9.i386.rpm
$
Did I get a corrupted rpm?
looks like you did.
-sv
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
