[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426576#comment-16426576
]
Uwe Schindler commented on LUCENE-7935:
---
There is nothing wrong. I just said, that the md5 and sha1 files are generated
through this process und pushed to the repository. That is why they are there.
They were not added by Sonatype, the maven-ant-plugin generates them and puts
them into the repo that smoke tester checks.
If we upload to ASF repository, it's then their turn (?) or the plugin's
responsibility to add sha512. If the plugin have to do it, we have a problem.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426567#comment-16426567
]
Jan Høydahl commented on LUCENE-7935:
-
{quote}I think there is also a problem on top: the maven-ant-plugin seems to
generate the checksums when executing an "uploading" (in our case to local
folder, see "artifact:deploy" in the build log). As this plugin is no longer
maintained (or is it?), we can't publish the new hashes anyways.
{quote}
Can you clarify? I cannot see anything wrong, here's the output from the
{{artifact:deploy}} phase of last build:
*-dist-maven*
:
[artifact:install-provider] Installing provider:
org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-7:runtime
[artifact:deploy] Deploying to
file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/solr/package/maven/
[artifact:deploy] Uploading:
org/apache/solr/solr-velocity/8.0.0/solr-velocity-8.0.0.jar to repository local
at
file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/solr/package/maven/
[artifact:deploy] Transferring 31K from local
[artifact:deploy] Uploaded 31K
[artifact:deploy] [INFO] Uploading project information for solr-velocity 8.0.0
[artifact:deploy] [INFO] Retrieving previous metadata from local
[artifact:deploy] [INFO] repository metadata for: 'artifact
org.apache.solr:solr-velocity' could not be found on repository: local, so will
be created
[artifact:deploy] [INFO] Uploading repository metadata for: 'artifact
org.apache.solr:solr-velocity'
[artifact:deploy] Uploading:
org/apache/solr/solr-velocity/8.0.0/solr-velocity-8.0.0-sources.jar to
repository local at
file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/solr/package/maven/
[artifact:deploy] Transferring 31K from local
[artifact:deploy] Uploaded 31K
[artifact:deploy] Uploading:
org/apache/solr/solr-velocity/8.0.0/solr-velocity-8.0.0-javadoc.jar to
repository local at
file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/solr/package/maven/
[artifact:deploy] Transferring 63K from local
[artifact:deploy] Uploaded 63K
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426558#comment-16426558
]
Jan Høydahl commented on LUCENE-7935:
-
Smoke build success
https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/996/
{noformat}
[smoker] verify Maven artifacts' md5/sha1 digests...
...
Finished: SUCCESS
{noformat}
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426517#comment-16426517
]
Uwe Schindler commented on LUCENE-7935:
---
Thanks!
{quote}
bq. The ASF page on publishing Maven artifacts
(http://www.apache.org/dev/publishing-maven-artifacts.html) says we don't need
to provide MD5 or SHA1 files:
Nexus will create MD5 and SHA1 checksums on the fly
{quote}
I think there is also a problem on top: the maven-ant-plugin seems to generate
the checksums when executing an "uploading" (in our case to local folder, see
"artifact:deploy" in the build log). As this plugin is no longer maintained (or
is it?), we can't publish the new hashes anyways. I also think that Maven still
requires md5 files in its infrastructure (at least they require them at
sonatype when you close the repository).
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426364#comment-16426364
]
ASF subversion and git services commented on LUCENE-7935:
-
Commit dced5ae3742a747e96843055ece18a8f34f9b3d0 in lucene-solr's branch
refs/heads/branch_7x from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dced5ae ]
LUCENE-7935: Keep md5/sha1 checksums for maven artifacts
(cherry picked from commit 60ae7be)
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426361#comment-16426361
]
ASF subversion and git services commented on LUCENE-7935:
-
Commit 60ae7be40786d6f8a5c5c8393875bf986d2b8877 in lucene-solr's branch
refs/heads/master from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=60ae7be ]
LUCENE-7935: Keep md5/sha1 checksums for maven artifacts
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426248#comment-16426248
]
Jan Høydahl commented on LUCENE-7935:
-
Ok, that was what I suspected, as I could not find a way to generate any hashes
in the maven parts of the build.
Uploaded a patch LUCENE-7935_smokefail.patch which reverts the changes to
smokeTester's {{verifyMavenDigests(artifacts)}} method, i.e. it will look for
md5 and sha1 there. Looks good so far, running a full local smoketest and will
commit if it succeeds.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426238#comment-16426238
]
Steve Rowe commented on LUCENE-7935:
{quote}I suppose we want to discontinue md5 also for all maven artifacts, or is
it required?
{quote}
This page, which lists requirements for Maven Central hosting, doesn't mention
md5 or any other hash; only PGP signatures are mentioned:
[http://central.sonatype.org/pages/requirements.html]
The Maven distribution section on the ASF page on publishing releases
([http://www.apache.org/dev/release-publishing.html#distribution_maven]) says:
{quote}don't try to publish .sha256, .sha512 files yet; Nexus doesn't handle
them (as of March 2018)
{quote}
The ASF page on publishing Maven artifacts
([http://www.apache.org/dev/publishing-maven-artifacts.html]) says we don't
need to provide MD5 or SHA1 files:
{quote}Nexus will create MD5 and SHA1 checksums on the fly
{quote}
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426070#comment-16426070
]
Jan Høydahl commented on LUCENE-7935:
-
Looks like a mismatch here, the maven artifacts build still produces md5 and
sha1 files, while the smoke tester tries to verify sha512.
I suppose we want to discontinue md5 also for all maven artifacts, or is it
required?
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417018#comment-16417018
]
Jan Høydahl commented on LUCENE-7935:
-
Pushed new README file to the Solr list site. See
[http://www.apache.org/dist/lucene/solr/] for how it looks. If OK, I'll push
the updated one for Lucene too.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416972#comment-16416972
]
Jan Høydahl commented on LUCENE-7935:
-
Committed. These will get the final test during the 7.4 release process.
I will proceed with updating README files in the dist repo (LUCENE-5143 README
patch)
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416966#comment-16416966
]
ASF subversion and git services commented on LUCENE-7935:
-
Commit 5ba99d0ea0e7245c9a11c7c924c1a8d8ee59e1a2 in lucene-solr's branch
refs/heads/branch_7x from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5ba99d0 ]
LUCENE-7935: Publish .sha512 hash files with the release artifacts
(cherry picked from commit 9e780ba)
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416936#comment-16416936
]
ASF subversion and git services commented on LUCENE-7935:
-
Commit 9e780ba5640f8230a5b0cecad956707b1e6586ca in lucene-solr's branch
refs/heads/master from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9e780ba ]
LUCENE-7935: Publish .sha512 hash files with the release artifacts
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395137#comment-16395137
]
Jan Høydahl commented on LUCENE-7935:
-
New patch that gets rid of md5 files, and this time {{smokeTestRelease.py}}
actually works (tested), and also {{prep-solr-ref-guide-rc.sh}} is tested. I
moved the CHANGES entry to LUCENE 7.4, since the 7.3 branch is already cut.
Are we good to go?
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394323#comment-16394323
]
Jan Høydahl commented on LUCENE-7935:
-
Just saw that the new guideline actually discourages use of MD5:
{quote}SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).
{quote}
I'll modify the patch to get rid of {{.md5}} and upload a new patch with only
{{.sha512}}.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Fix For: 7.3, master (8.0)
>
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389735#comment-16389735
]
Jan Høydahl commented on LUCENE-7935:
-
I'll commit this to master and branch_7x soon so that 7.3 will be the first
release complying to the updated guidelines at
[http://www.apache.org/dev/release-distribution#sigs-and-sums.] Any objections?
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
>Priority: Major
> Fix For: 7.3, master (8.0)
>
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138908#comment-16138908
]
Cassandra Targett commented on LUCENE-7935:
---
bq. do these commands work for you (and produce the same output) on your dev
machine...
[~hossman], yes, they work and produce the same output on my machine. I guess
we're good then?
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138899#comment-16138899
]
Hoss Man commented on LUCENE-7935:
--
bq. I'm building an RC for 6.6.1 . Should we commit this to branch_6_6 and then
build one?
I can't see any reason whatsoever for this patch (or any discussion around it)
to hold up any releases -- let alone a bug fix release, which should *only*
contain things strictly neccessary for fixing bugs (not unrelated build/release
script improvements)
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138898#comment-16138898
]
Hoss Man commented on LUCENE-7935:
--
i didn't test it, but skimming the patch the changes seem fine ... assuming
we're ok w/removing support for doing ref-guide releases on machines that don't
have {{shasum}} ... i assume that's fine? IIRC the problem we've had in the
past was the opposite: that some OSs/distros didn't provide {{sha1sum}}.
[~ctargett]: you tend to do most of the ref guide releases, do these commands
work for you (and produce the same output) on your dev machine...
{noformat}
$ echo "anything" | shasum -a 512
b64baad7af53a75d3cebec373cadc509b09be8516844402f4f2d74355f9ef4488015d130f9d3874c09381daa9bca98452e6822a81b1a6cd4baeef356a781
-
$ echo "anything" | shasum
86b18486b5d0b47d7e6173dc2d90d6c9958518f3 -
{noformat}
If so then we're probably fine.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138879#comment-16138879
]
Cassandra Targett commented on LUCENE-7935:
---
I'm not the right person to look at that script - perhaps [~hossman] has time,
since he wrote it.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137632#comment-16137632
]
Jan Høydahl commented on LUCENE-7935:
-
I intended to test a a full round of buildAndPushRelease.py and then
smokeTestRelease.py but never completed due to some unit test failures. You are
free to add it and give it a spin, but be prepared to fix potential issues
along the way.
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137563#comment-16137563
]
Varun Thacker commented on LUCENE-7935:
---
I'm building an RC for 6.6.1 . Should we commit this to branch_6_6 and then
build one?
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7935) Release .sha512 hash files with our artifacts
[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135373#comment-16135373
]
Anshum Gupta commented on LUCENE-7935:
--
Just glanced through the patch. Looks good. Thanks Jan!
> Release .sha512 hash files with our artifacts
> -
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
