...i think i see what is going on. Looking at older releases I see that the nexus repo sources.zip and dist directory sources.zip doesn't always precisely match. These are generated at different parts of the lifecycle and so they wont match as the dates would be different.
Our vote template says "The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-nnnn"; Yet our helper guide says "# Pull down nifi-${NIFI_VERSION} source release artifacts for review: wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip " Notice one is from the nexus repo and the other from dist. The only official artifacts we publish and vote on are those in dist. I'll update the vote template to clarify this and generate an RC3 to do a clean cycle. Thanks Joe On Sun, Oct 27, 2019 at 9:39 PM Joe Witt <[email protected]> wrote: > Mike - I confirm I see what you see. I'll cancel RC2 and issue RC3 in the > morning. The only thing unique was that I did release:prepare Friday > afternoon and release:perform Sunday AM. The first pass of release:perform > failed as I didn't enter user input at the right time so I ran it a second > time. Must have goofed up something there. The only difference I see in > the zip files for source is the date but better to be safe and ensure a > good clean release. > > Thanks > > On Mon, Oct 28, 2019 at 12:00 AM Joe Witt <[email protected]> wrote: > >> very strange. will verify and if so will dump rc2 and try again >> >> On Sun, Oct 27, 2019 at 6:17 PM Mike Thomsen <[email protected]> >> wrote: >> >>> Pulled the zip from the vote thread link and didn't get the same hashes: >>> >>> $ wget >>> >>> https://repository.apache.org/content/repositories/orgapachenifi-1149/org/apache/nifi/nifi/1.10.0/nifi-1.10.0-source-release.zip >>> $ shasum -a 256 nifi-1.10.0-source-release.zip >>> 468f4cf761bc2578407cc7bd080134b4bfb599cea45a42453942837f5bba5663 >>> nifi-1.10.0-source-release.zip >>> $ shasum -a 512 nifi-1.10.0-source-release.zip >>> >>> 5afdaf33770a309c77799d8e4d28063fc46ea0a4594d229405218e5ed894c1386853c1ab50ddce4041bc6db684dc017434a85db9e436cb05f6e004ad5faccd15 >>> nifi-1.10.0-source-release.zip >>> >>> Release guidance: >>> >>> Checksums of nifi-1.10.0-source-release.zip: >>> SHA256: 6e2b146c2feb779eee105ec6618e4789b9e4a8b977cca815027e6d1421180231 >>> SHA512: >>> >>> 745781ef11c1ee95ea38ffdf355d5d13dced8d6ecc0338b062995be30f7f55bad0c85f61d8ba81155bf849f53e36362bee86f3358ba3d974086234dfb7e11574 >>> >>> When I use the wget commands from the RC1 helper guide, I get the >>> expected >>> hashes: >>> >>> $ wget >>> >>> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.10.0/nifi-1.10.0-source-release.zip >>> $ shasum -a 256 nifi-1.10.0-source-release.zip >>> 6e2b146c2feb779eee105ec6618e4789b9e4a8b977cca815027e6d1421180231 >>> nifi-1.10.0-source-release.zip >>> $ shasum -a 512 nifi-1.10.0-source-release.zip >>> >>> 745781ef11c1ee95ea38ffdf355d5d13dced8d6ecc0338b062995be30f7f55bad0c85f61d8ba81155bf849f53e36362bee86f3358ba3d974086234dfb7e11574 >>> nifi-1.10.0-source-release.zip >>> >>> Did I screw something up or is there something out of sync between the >>> instructions and expected values published? >>> >>> Thanks, >>> >>> Mike >>> >>
