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 > > > > > > >
