You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Joe Witt <jo...@apache.org> on 2015/12/06 04:43:02 UTC

Helper for those interested in verifying 0.4.0 rc1

Team,

Here again is guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
  https://dist.apache.org/repos/dist/release/nifi/KEYS

# Import keys file:
  gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-0.4.0 source release artifacts for review:

  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.asc
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.md5
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.sha1

# Verify the signature
  gpg --verify nifi-0.4.0-source-release.zip.asc

# Verify the hashes (md5 and sha1) match the source and what was
provided in the vote email thread
  md5sum nifi-0.4.0-source-release.zip
  sha1sum nifi-0.4.0-source-release.zip

# Unzip nifi-0.4.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
  cd nifi-0.4.0
  mvn clean install -Pcontrib-check

# Verify the contents contain a good readme, notice, and license.

# Verify the git commit ID is correct

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the readme, license, notice are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on
your findings.

Thank you for your time and effort to validate the release!

Joe

Re: Helper for those interested in verifying 0.4.0 rc1

Posted by Joe Percivall <jo...@yahoo.com.INVALID>.
I actually had a problem unzipping this package on Windows. I tried unzipping in my Downloads folder and it gave me a "Path Too Long" error. Both the built-in Windows extractor and WinZip failed to un-package it. Turns out that once a path goes above a certain number of characters the extraction fails, you can see more in this youtube video [1].


I moved the zip to my root directory I was able to unpackage the zip file. 
[1] https://youtu.be/60aQwGvC5Bs

Joe
 
- - - - - - 
Joseph Percivall
linkedin.com/in/Percivall
e: joepercivall@yahoo.com




On Saturday, December 5, 2015 10:43 PM, Joe Witt <jo...@apache.org> wrote:



Team,

Here again is guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
  https://dist.apache.org/repos/dist/release/nifi/KEYS

# Import keys file:
  gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-0.4.0 source release artifacts for review:

  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.asc
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.md5
  wget https://dist.apache.org/repos/dist/dev/nifi/nifi-0.4.0/nifi-0.4.0-source-release.zip.sha1

# Verify the signature
  gpg --verify nifi-0.4.0-source-release.zip.asc

# Verify the hashes (md5 and sha1) match the source and what was
provided in the vote email thread
  md5sum nifi-0.4.0-source-release.zip
  sha1sum nifi-0.4.0-source-release.zip

# Unzip nifi-0.4.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
  cd nifi-0.4.0
  mvn clean install -Pcontrib-check

# Verify the contents contain a good readme, notice, and license.

# Verify the git commit ID is correct

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the readme, license, notice are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on
your findings.

Thank you for your time and effort to validate the release!

Joe