On Thu, May 12, 2022 at 01:54:57PM +0900, Kyotaro Horiguchi wrote: > At Thu, 12 May 2022 11:44:33 +0900 (JST), Kyotaro Horiguchi > <horikyota....@gmail.com> wrote in > > At Thu, 12 May 2022 10:34:49 +0900 (JST), Tatsuo Ishii <is...@sraoss.co.jp> > > wrote in > > > Last year we faced a similar problem, namely, a new committer for > > > pgpool.git could not access the git repository (Permission denied > > > (publickey)). Magnus kindly advised following and it worked. Hope this > > > helps. > > > > > > > 1. Log into the git server on https://git.postgresql.org/adm/. It > > > > should be an automatic log in and show the repository. > > > > 2. *then* go back to the main website and delete the ssh key > > > > 3. Now add the ssh key again on the main website > > > > 4. Wait 10-15 minutes and then it should work > > > > Thank you for the info, but unfortunately it hasn't worked. > > I'm going to try a slightly different steps.. > > And finally I succeeded to clone from git.postgresql.org and to push a > commit.
Sorry, but this has me confused. When I read this, I thought you were pushing a 'pgsql' core server commit to gitmaster, but that would be impossible for git.postgresql.org, so where are you pushing to? This might be part of the confusion Dave was asking about. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson