Hi, Hm... I finally solve the problem and for *ALL* committers *in China* please pay attention:
If you do not have a VPN (a regular VPN like L2TP), and you never uploaded your GPG KEY to a key server, then you can not use pgp.mit.edu as the destination of the key server... I think all of you Chinese guys know why... And, you even can not use pool.sks-keyservers.net:11371 because the terminal will say: gpg: keyserver search failed: No route to host So, how to upload your key to a key server?.. Fortunately you can find a dozen of server addresses from [1], I tried two of them, [2] and [3]. Then I tried another [4]. Actually you still can not use command `gpg --keyserver --send-key` to upload your key successfully. But, if you open these urls using your browser, you can find a button called `Submit Key`! Just paste your ascii public key here.. Your ascii public key looks like: -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBF2LLTABEACRM0lzt9BMSsIg9cCfcEBRH6Fc2etS7vrOt8NPq2VTuHYHUMzA ... -----END PGP PUBLIC KEY BLOCK----- Then, you can search your key id from [4] or [5]. By the way, you can not get any result if you enter key id like 2206EF8F64C35889. But, if you input the key id as your email address (that you wrote when you generate the key), you will find a result, and it means you have uploaded your GPG key successfully! (What confusing me is that I still can not get my public key from [2] or [3]) Then you can close the staging repository successfully. Cheers! [1] https://sks-keyservers.net/overview-of-pools.php [2] ipv4.pool.sks-keyservers.net [3] p80.pool.sks-keyservers.net [4] http://keys.gnupg.net [5] http://pool.sks-keyservers.net:11371/# Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang <[email protected]> 于2019年9月27日周五 下午10:19写道： > Hi Julian, > > Thanks for your reply. I think I uploaded the key about 20 hours ago, so > does it really need so long time to sync...? > > Then I tried to search your key id and Chris's key id on the website ( > http://pool.sks-keyservers.net:11371/), the website also says not > found... > > Best, > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer <[email protected]> 于2019年9月27日周五 下午10:03写道： > >> Hi, >> >> it can take some time fort he keyservers to sync, so this could be one >> issue. >> Just try it again later. >> >> Julian >> >> Am 27.09.19, 16:00 schrieb "Xiangdong Huang" <[email protected]>: >> >> Hi all, >> >> Thanks for taking care of this release... >> >> One more question that I am facing... >> >> Now I am trying to closing the staging repository from the Nexus [1], >> but fails because "No public key: Key with id: (2206ef8f64c35889) was >> not >> able to be located on <a href="http://pool.sks-keyservers.net:11371";> >> http://pool.sks-keyservers.net:11371</a>." >> >> Actually I have created a GPG KEY by following the documents [2] and >> [3], >> attached the public key to KEYS file, uploaded the new KEYS to SVN >> [4], >> and have uploaded the key to keyserver by using `gpg2 --keyserver >> pgp.mit.edu --send-keys MY KEY ID` . >> Now, if I run `gpg2 --keyserver pgp.mit.edu --search-keys >> Xiangdong`. I can >> find the public key like: >> >> gpg: data source: http://pgp.mit.edu:11371 >> (1) Xiangdong Huang (Apache IoTDB release signing key) < >> [email protected]> >> 4096 bit RSA key 2206EF8F64C35889, created: 2019-09-25 >> >> Would someone kind to help me to tell me why the public key is not >> able to >> be located on pool.sks-keyservers.net? >> >> Best, >> >> [1] https://repository.apache.org/#stagingRepositories >> [2] https://spark.apache.org/release-process.html >> [3] https://www.apache.org/dev/openpgp.html#generate-key >> [4] https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS >> >> ----------------------------------- >> Xiangdong Huang >> School of Software, Tsinghua University >> >> 黄向东 >> 清华大学 软件学院 >> >> >> Julian Feinauer <[email protected]> 于2019年9月27日周五 >> 下午8:13写道： >> >> > Hey, >> > >> > but I think we are totally covered here by Apache Policy as a >> Release is >> > only a release (and released) if its source in the svn. >> > So although this thing has the "name" release in the tag it has >> strictly >> > speaking nothing to do with an APACHE release at all. >> > >> > In fact, this is the practice we also use in PLC4X (and in many >> other >> > projects). >> > >> > Julian >> > >> > Am 27.09.19, 11:58 schrieb "Justin Mclean" < >> [email protected]>: >> > >> > Hi, >> > >> > > That's what maven automatically does ... it tags the potential >> > release in the repo. >> > > That Github shows these release tags as "released" versions >> is a >> > issue that has been discussed in the past. >> > >> > Which I believe why you should do do maven release after you >> have >> > voted on the release. Maven is not where Apache releases software, >> it’s >> > only a secondary distribution mechinism. >> > >> > Thanks, >> > Justin >> > >> > >> >> >>
