README goofs

Michael W. Lucas mwlucas at blackhelicopters.org
Sun Jan 16 20:21:04 CET 2005


Hi,

This is minor, but it's going to itch until I say something:

The README specifies a md5 checksum, but you publish a SHA1 checksum.

The README also specifies a gzipped tarball, but you have a bzipped
tarball.

Patch (such as it is) attached.

Thanks!

==ml

-- 
Michael W. Lucas	mwlucas at FreeBSD.org, mwlucas at BlackHelicopters.org
		http://www.BlackHelicopters.org/~mwlucas/
	       Latest book: Cisco Routers for the Desperate
	        http://www.CiscoRoutersForTheDesperate.com
-------------- next part --------------
--- README-dist	Sun Jan 16 14:15:54 2005
+++ README	Sun Jan 16 14:17:43 2005
@@ -54,7 +54,7 @@
        this.  Don't skip it - this is an important step!
 
     2) Unpack the tarball.  With GNU tar you can do it this way:
-       "tar xzvf gnupg-x.y.z.tar.gz"
+       "tar xyvf gnupg-x.y.z.tar.bz2"
 
     3) "cd gnupg-x.y.z"
 
@@ -104,13 +104,13 @@
 
 
     b) If you don't have any of the above programs, you have to verify
-       the MD5 checksum:
+       the SHA1 checksum:
 
-	$ md5sum gnupg-x.y.z.tar.gz
+	$ sha1 gnupg-1.4.0.tar.bz2
 
        This should yield an output _similar_ to this:
 
-	fd9351b26b3189c1d577f0970f9dcadc  gnupg-x.y.z.tar.gz
+	SHA1 (gnupg-1.4.0.tar.bz2) = 0054635a131b7af383e956fa9e1520ac44cad116
 
        Now check that this checksum is _exactly_ the same as the one
        published via the announcement list and probably via Usenet.


More information about the Gnupg-devel mailing list