Suppose we take the following example: https://lists.apache.org/thread.html/c99519e1c8e0a4af5be02f40e8e44b408cbc3d4568a334f3a400b94f%40%3Cdev.commons.apache.org%3E
This is Commons Daemon 1.2.0 based on RC2. Take for example: https://archive.apache.org/dist/commons/daemon/source/commons-daemon-1.2.0-native-src.tar.gz with sha256: 13c8d9b27d38ae1ced1fb37743239035cd1add74a8ef20bfce38386fc0b4a243 *commons-daemon-1.2.0-native-src.tar.gz How does one show that it is the same source that was voted on? Also the Maven jar: commons-daemon-1.2.0.jar sha1: a3a42da759a94a0522fe4b867ac2f5d0d58cc0a9 Sebb. On Mon, 7 Sep 2020 at 14:16, Gilles Sadowski <gillese...@gmail.com> wrote: > > Hello. > > > > [...] > > > see an explanation for why it is necessary > > > (or even helpful) to include artefact hashes in the vote mail. > > > > > I agree and understand all your points here. > > Well, I don't. > An explanation would be useful indeed. > > > > Validating the svn revision for the dist repo [ ... vs ...] > > > comparing the hashes of each file to a hash provided in > > > the vote email. [...] > > > > I was merely trying to offer the opposing perspective of the other folks. > > Aren't we talking about a *requirement*? > Referring to the "executive summary" above (as I understand it), > from Mark's edited text, which information is necessary and sufficient > for a vote? > > Also, isn't this discussion a rehash of my (recurrent) question > about whether the hash checks should be automated? > [I mean, isn't it sufficient that the RM would indicate in the vote > email that the hash values stored in the "dist" area are the same > as those generated by the build?] > > Regards, > Gilles > > > > > [...] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
