Hey Liya, I can sign your key. Feel free to propose a timeslot when you are available and we can hold a virtual key signing party; I am in UTC+1.
The docker-compose build works fine for me so not sure what went wrong in your environment. I just added the 1.30.0 release in the reporter tool [1]. Best, Stamatis [1] https://reporter.apache.org/addrelease.html?calcite On Sun, Mar 20, 2022 at 11:26 AM Fan Liya <[email protected]> wrote: > The problem was worked around by building the site manually. > If we find the root cause, maybe we need to adjust the document > accordingly. > > BTW, we need a PMC to update the latest release at > https://reporter.apache.org/addrelease.html?calcite > Is there anyone willing to help? > Thank you in advance. > > Best, > Liya Fan > > > > Fan Liya <[email protected]> 于2022年3月20日周日 16:54写道： > > > Hi all, > > > > When building the web site, I got another problem. > > > > I followed the instructions in > > https://github.com/apache/calcite/blob/master/site/README.md, and each > > step finished successfully. > > However, after running the following command: > > > > docker-compose run build-site > > > > I got the following error: > > > > > /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/spec_set.rb:87:in > > `block in materialize': Could not find concurrent-ruby-1.1.9 in any of > the > > sources (Bundler::GemNotFound) > > > > I tried the following methods to solve it, but none of them worked: > > 1. Remove the Gemfile.lock file and rebuild > > 2. Install concurrent-ruby-1.1.9 manually > > 3. Add local source in Gemfile > > 4. Rebuild index: sudo bundle --full-index > > > > I changed another machine and restarted the whole process, but the > problem > > persists. > > > > Do you have any idea about the problem? Thank you in advance. > > > > Best, > > Liya Fan > > > > > > > > > > Fan Liya <[email protected]> 于2022年3月19日周六 16:59写道： > > > >> 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 <[email protected]> 于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 <[email protected]> 于2022年3月11日周五 21:49写道： > >>> > > >>> >> Hi Stamatis, > >>> >> > >>> >> Thanks a lot for your clarification and confirmation. > >>> >> > >>> >> Best, > >>> >> Liya Fan > >>> >> > >>> >> > >>> >> Stamatis Zampetakis <[email protected]> 于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 <[email protected]> > 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 > >>> >>>> > >>> >>> > >>> >> > >>> > > >>> > >> >
