Moving the discussion to separate thread instead of vote thread. The md5 and sha512 are generated through following commands :
gpg --print-md MD5 apache-lens-2.1.0-beta-incubating-bin.tar.gz > apache-lens-2.1.0-beta-incubating-bin.tar.gz.md5 gpg --print-md SHA512 apache-lens-2.1.0-beta-incubating-bin.tar.gz > apache-lens-2.1.0-beta-incubating-bin.tar.gz.sha512 But seems md5sum -c is expecting a different format. If the numbers generated through both methods match is that enough for verifying? I hope so, because 2.0.x release vote passed with same checksum generation methods. Can anyone confirm if that is fine? Thanks Amareshwari On Tue, Apr 28, 2015 at 12:52 PM, Arshad Matin <[email protected]> wrote: > Not able to verify checksum , md5 and sha512 > > lens:~/verify$ md5sum -c apache-lens-2.1.0-beta-incubating-bin.tar.gz.md5 > md5sum: apache-lens-2.1.0-beta-incubating-bin.tar.gz.md5: no properly > formatted MD5 checksum lines found > > > lens:~/verify$ gpg --print-md MD5 > apache-lens-2.1.0-beta-incubating-bin.tar.gz > apache-lens-2.1.0-beta-incubating-bin.tar.gz: > 63 FF 66 20 9C 13 C9 F5 CF F4 7D C6 37 41 5D 28 > lens:~/verify$ > lens:~/verify$ cat apache-lens-2.1.0-beta-incubating-bin.tar.gz.md5 > apache-lens-2.1.0-beta-incubating-bin.tar.gz: > 63 FF 66 20 > 9C 13 C9 F5 > CF F4 7D > C6 37 41 5D > 28 > > Actually md5sum is expecting the checksum in following format > > lens:~/verify$ md5sum apache-lens-2.1.0-beta-incubating-bin.tar.gz > c1.md5 > lens:~/verify$ cat c1.md5 > 63ff66209c13c9f5cff47dc637415d28 > apache-lens-2.1.0-beta-incubating-bin.tar.gz > > On Mon, Apr 27, 2015 at 5:54 PM, Amareshwari Sriramdasu < > [email protected]> wrote: > > > Hi everyone, > > > > I propose the following RC to be released as official Apache Lens > > 2.1.0-beta-incubating release. > > > > The commit id is fdd19b9c2b17e329465cbde62dbce6f8be435cec > > : > > > https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=fdd19b9c2b17e329465cbde62dbce6f8be435cec > > > > > > This corresponds to the tag: apache-lens-2.1.0-beta-incubating > > : > > > https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.1.0-beta-incubating > > > > > > The release archives (tar.gz/.zip), signature, and checksums are > > here: > > > https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.1.0-beta-incubating-rc0 > > > > You can find the KEYS file here: > > * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS > > > > The release candidate consists of the following source distribution > > archive: > > apache-lens-2.1.0-beta-incubating-source-release.zip > > > > In addition, the following supplementary binary distributions are > > provided for user convenience at the same location: > > apache-lens-2.1.0-beta-incubating-bin.tar.gz > > > > The licensing of bundled bits in the archives have not changed from > > previous release, which are > > documentedhttps:// > > cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens > > > > The Nexus Staging URL: > > https://repository.apache.org/content/repositories/orgapachelens-1003 > > > > Release notes available at > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923&version=12328991 > > > > > > Vote will be open for at least 72 hours > > > > [ ] +1 approve > > [ ] 0 no opinion > > [ ] -1 disapprove (and reason why) > > > > +1 from my side for the release. > > > > For folks not familiar with vetting a release, please refer > > tohttp://incubator.apache.org/guides/releasemanagement.html#check-list > > > > Thanks > > > > Amareshwari > > > > -- > _____________________________________________________________ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. >
