wenhao created HBASE-25366:
--
Summary: [Documentation] Fix spelling error
Key: HBASE-25366
URL: https://issues.apache.org/jira/browse/HBASE-25366
Project: HBase
Issue Type: Bug
Components:
Now that the Docker release script is working again (thanks Stack) I can make a
test branch and run that to build a fake RC and examine the resulting temporary
repository. If there are .asc.asc files again I’m not sure we learn more (could
be normal, or a POM change introduced into branch-2)
Baiqiang Zhao created HBASE-25365:
-
Summary: The log in move_servers_rsgroup is incorrect
Key: HBASE-25365
URL: https://issues.apache.org/jira/browse/HBASE-25365
Project: HBase
Issue Type:
If gpg had verified the signatures I probably wouldn't have noticed
them and we have no other staged repos at the moment, so it's hard to
say if this is a new problem. None of the published versions contain
such files, but for all we know nexus filters them when promoting the
repository.
I think
Even a clean build of 'mvn clean install deploy -DskipTests
-Papache-release' produces a staging repository containing .asc.asc files. I
am not doing anything different than the build script, our earlier
make_rc.sh, and documented procedure. Are we sure this has not always been
the case and now we
I will drop that temporary repository and make a new one. I believe I know what
happened. I re-ran the Maven deploy goal after it had failed the one time
without a clean step first. Previous signature files in target/ were themselves
included in the list of things to sign (apparently). ‘mvn
+1 for the artifacts on dist.a.o for 2.4.0 RC1
I'd rather we not use the staged nexus repo orgapachehbase-1416
because it appears to have some errors. specifically there's a
duplicative '.asc.asc' file for each signed artifact that gpg can't
verify.
On Fri, Dec 4, 2020 at 11:29 AM Andrew Purtell
