Hi Francis, Thanks a lot for your feedback. I can see it propagated too.
However, it is not listed in https://dlcdn.apache.org/calcite/ Maybe the list will be updated later. Thanks again for your kind help. Best, Liya Fan Francis Chuang <francischu...@apache.org> 于2022年3月19日周六 16:37写道： > Hi Liya, > > I can see that the release has propagated: > https://dlcdn.apache.org/calcite/apache-calcite-1.30.0/ > > We do need to sign your key though, using a virtual key signing party so > that your key is part of the web of trust. > > Francis > > On 19/03/2022 7:28 pm, Fan Liya wrote: > > Hi all, > > > > I am having another problem when trying to publish the release. > > After running the publishing command: > > > > ./gradlew publishDist -Prc=3 -Pasf > > > > It seemed to have finished successfully. > > However, the release was not propagated to the mirrors (it was supposed > to > > be propagated almost immediately): > > > > https://dlcdn.apache.org/calcite/ > > > > Do you have any idea about the reason? Is it because my key was not > signed, > > as noted by Julian? > > > > Thanks in advance > > > > Best, > > Liya Fan > > > > Fan Liya <liya.fa...@gmail.com> 于2022年3月11日周五 21:49写道： > > > >> Hi Stamatis, > >> > >> Thanks a lot for your clarification and confirmation. > >> > >> Best, > >> Liya Fan > >> > >> > >> Stamatis Zampetakis <zabe...@gmail.com> 于2022年3月11日周五 21:39写道： > >> > >>> Hi Liya, > >>> > >>> The asf.git.pushRepositoryProvider property controls the git repository > >>> that is used by the release plugin [1]. There are two options: > >>> * GITBOX -> https://gitbox.apache.org/repos/asf/calcite.git > >>> * GITHUB -> https://github.com/apache/calcite.git > >>> > >>> In the first attempt, you tried to push to GITBOX and it failed. > >>> In the second attempt, you tried to push to GITHUB and it was > successful. > >>> > >>> Probably, the reason lies behind the credentials (asfGitSourceUsername, > >>> asfGitSourcePassword) that you are using for the release (GitHub vs > ASF). > >>> > >>> When you push changes to a remote Calcite repository (that being > regular > >>> commits, or tags, or anything else) you have to pick one of the two > >>> available options and that is sufficient. > >>> > >>> Best, > >>> Stamatis > >>> > >>> [1] > >>> > >>> > https://github.com/vlsi/vlsi-release-plugins/commit/b8b3c60760f2065d791c0b095e1b675cdbcfacbd > >>> > >>> On Fri, Mar 11, 2022 at 2:09 PM Fan Liya <liya...@apache.org> wrote: > >>> > >>>> Hi all, > >>>> > >>>> When preparing a release build, I ran the command according to the > >>> document > >>>> [1]: > >>>> > >>>> *./gradlew prepareVote -Prc=2 -Pasf > >>>> -Pasf.git.pushRepositoryProvider=GITBOX* > >>>> > >>>> Then I got the following error message: > >>>> > >>>> > >>>> > >>>> *Build calcite FAILURE reason: Execution failed for task > >>> ':pushRcTag': > >>>> Caused by: org.eclipse.jgit.api.errors.TransportException: > >>>> https://gitbox.apache.org/repos/asf/calcite.git > >>>> <https://gitbox.apache.org/repos/asf/calcite.git>: not authorized* > >>>> > >>>> However, when I remove the last command line argument: > >>>> > >>>> *./gradlew prepareVote -Prc=2 -Pasf* > >>>> > >>>> It seemed to finish successfully. > >>>> > >>>> Is this expected? > >>>> Thank you in advance. > >>>> > >>>> Best, > >>>> Liya Fan > >>>> > >>>> [1] > >>> https://calcite.apache.org/docs/howto.html#making-a-release-candidate > >>>> > >>> > >> > > >
