Page History

...

Check using the command line interface

GenerateGENERATE. To generate checksums, navigate to the directory containing the .zip file and run the CertUtil command. Append SHA512 and MD5, as shown below, to generate those checksums.  (The default gives you the SHA1 checksum.) 

...

    CertUtil -hashfile 'apache-taverna-parent-2-incubating-source-release.zip' MD5

VerifyVERIFY. To verify, visually compare the checksums with those listed in the VOTE email., or copy and paste the checksums into use an online difference checker.

Check using the MD5 and SHA Checksum Utility

GenerateGENERATE. Follow the steps below.

1. Open the MD5 and SHA Checksum Utility (double-click the .exe), a window opens (see below). 
2. Browse to the release candidate .zip file, and the checksums will be displayed. (Use the checkboxes to choose which checksums you want to see.) 
3. You can copy individual checksums, or use the Copy All button. 
   

VerifyVERIFY. You can visually compare the checksums or use an online difference checker.  The utiility also allows you to paste a checksum (e.g., either from the VOTE email or from the downloaded .md5 or .sha1 files) into the Hash input box, and the utility will compare it with the value from the .zip file.

...

Each software artifact is signed using a PGP (Pretty Good Privacy) key. Verifying the downloaded key matches the original key is a critical step.

You can verify the signatures using a command line interface. See https://httpd.apache.org/dev/verification.html for some general verification info.

...

1. Download the Taverna key file from https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS. (On Windows this can be done by typing Ctrl-S in the browser window and saving the file as keys.txt.)
   
   
2. Import the key file into GPG:
   

   gpg --import keys.txt

    

3. Download the .asc file. (Save this file in the same folder as keys.txt.)
   
   
4. Verify the .asc file matches the zipped release candidate by using the gpg command with the --verify option followed by the .asc filename and the .zip filename.

...

The idea here is to check that the commit ID in the downloaded file matches that in the VOTE email. You will use a command line terminal interface for at least some of these steps.

Approach 1 (clone the git repository, checkout the commit id, and compare to release candidate)

This approach uses Git commands to compare the downloaded release candidate to a cloned git repository. You will clone one copy and unzip the other copy in such a way that will "trick" Git into thinking you are comparing two versions that you have edited. (I'm missing part of the picture here. What is the end configuration you want before you use git status to compare files?)

1. Make a new directory and change to that directory (e.g., mkdir 1 ; cd 1)
2. Git clone that-repository (which repository?? from where??)
3. Checkout the commit id from the repository you just created: git checkout <commit_id>
4.  rm -rf* (remove a directory? I don't understand this step.)
5. Unzip the release candidate (e.g., apache-taverna-parent-2-incubating-source-release.zip) (into the same directory?)
6. mv apache-taverna-"/*. (one level up) (Move the release candidate up one level? Because it zips into a new folder?) 
7. git status

Git will then check review the checksums of every file and let you know what has "changed." 

If there are NO CHANGES, then the commit ID in the VOTE email matches the release candidate.

Approach 2 (download git commit from GitHub and compare to release candidate)

This approach uses the commit id from the VOTE email to download that commit from GitHub, which is then compared to the release candidate using the diff command.

1. Search for the git commit corresponding to the email by browsing for it on GitHub. Use a URL that follows this pattern: https://github.com/apache/incubator-taverna-language/tree/<hash>, where <hash> is the commit has hash you want to download. 
2. Click "Download Zip" and save the file to your computer.
3. Make a new directory, change to the new directory, and unzip the GitHub file to the new folder. (e.g., mkdir 1 ; cd 1 ; unzip <filename>.zip)
4. Move up a directory (cd .. ) 
5. Make and make a second new directory (e.g., mkdir 2)
6. Change to the second new directory (e.g., cd 2) and unzip the release candidate (e.g., unzip release-candidate.zip)
7. Move up one directory. When you do a directory listing (ls) you should see both of your new directories listed.
8. Compare all files in the two new directories using the diff command:
   1. Linix: diff -uR 1 2
   2. Windows, GitBash: diff -r 1 2 (Windows CMD command line try FC)

The files that differ will be shown. If you do this after you build, make sure you don't have any target folders before diff-ing. (Run mvn clean to be sure.)

Again, if there are NO DIFFERENCES, then the commit ID in the VOTE email matches the release candidate.

3a Check the incubator disclaimer (INCUBATOR PROJECTS ONLY)

...