+1 on release notes, release contents, rat, META-INF, maven build, but have to -1 on bits-to-mirrors, until I can verify the hashes:
ERROR: Checksum stored in commons-modeler-2.0.1-javadoc.jar.md5 does not match commons-modeler-2.0.1-javadoc.jar Correct hash: a5381f035c7076bffe8df548768449e2 commons-modeler-2.0.1-javadoc.jar File contents: 5f2e5e2aadc3445cbc6a7d754bf6cc49 ERROR: Checksum stored in commons-modeler-2.0.1-sources.jar.md5 does not match commons-modeler-2.0.1-sources.jar Correct hash: fa1531a9178e625d77f5209a59056bf2 commons-modeler-2.0.1-sources.jar File contents: 5f2e5e2aadc3445cbc6a7d754bf6cc49 The sigs (including for these files) and other hashes check fine for me. I don't know what is going on here, since I get a similar failure when I execute "maven dist" on the unpacked sources and then verify the hashes of the generated files - the same two files give different hashes when run through either "md5sum" or "openssl md5" on Linux Fedora Core 4. I use "verify_sigs.sh" from /committers/tools/releases to verify the sigs and hashes; but I also checked both "md5sum" and "openssl md5" from the command line. Both gave the "Correct hash" values above. Notice that the two hashes in the .md5 files are the *same* for the -sources and -javadoc jars, which have different contents. To make sure this was not a download problem on my end, I downloaded twice and then just looked at the .md5 files directly at http://people.apache.org/~niallp/modeler-2.0.1-rc1/. You can see the stored hashes are the same. So unless I am going crazy here, m1 is doing something funny. Very odd, I just did maven dist again, watched it create the hashes with the right names and put the same hash values into the two .md5. Bizarre... I did not verify the Ant build - too painful - but assm you have checked that ;-) Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
