[pkg-crosswire-devel] Access to pkg-crosswire-team/bibledit

[Teus Benschop]

Dear fellow-developers,

Recently I changed my account on salsa.debian.org from teus-guest to
teusbenschop at debian.org. And now I can no longer push to the Bibledit
repository at Salsa [1].

[1] https://salsa.debian.org/pkg-crosswire-team/bibledit/

Here is the failure to push to the repository:

*teus at sid*:*~/bibledit*$ git push

> GitLab: You are not allowed to upload code for this project.

fatal: Could not read from remote repository.


Please make sure you have the correct access rights

and the repository exists.

*teus at sid*:*~/bibledit*$

Then I confirmed that authentication over ssh works fine:

*teus at sid*:*~/bibledit*$ GIT_SSH_COMMAND="ssh -v" git push

OpenSSH_8.0p1 Debian-6, OpenSSL 1.1.1d  10 Sep 2019

[...]

debug1: Authenticating to salsa.debian.org:22 as 'git'

[...]

debug1: Host 'salsa.debian.org' is known and matches the ED25519 host key.

debug1: Will attempt key: [...]/.ssh/id_rsa RSA

[...]

debug1: Authentications that can continue: publickey

[...]

debug1: Server accepts key: [...].ssh/id_rsa RSA

[...[ Authentication succeeded (publickey).

Authenticated to salsa.debian.org ([209.87.16.44]:22).

debug1: channel 0: new [client-session]

debug1: Remote: PTY allocation disabled.

debug1: Sending environment.

[...]

debug1: Sending command: git-receive-pack 'pkg-crosswire-team/bibledit.git'>
GitLab: You are not allowed to upload code for this project.

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0

debug1: client_input_channel_req: channel 0 rtype eow at openssh.com reply 0

debug1: channel 0: free: client-session, nchannels 1

debug1: fd 0 clearing O_NONBLOCK

Transferred: sent 2880, received 2864 bytes, in 0.9 seconds

Bytes per second: sent 3211.9, received 3194.1

debug1: Exit status 1

fatal: Could not read from remote repository.


Please make sure you have the correct access rights

and the repository exists.

*teus at sid*:*~/bibledit*$

That means that there's something in Salsa that does not accept my identity.

I then tried to add my public SSH key to the specific repository, with
read-write access. But it said that the key fingerprint was already in use.
As it was already uploaded to my @teusbenschop account at Salsa. The Salsa
documentation, or actually the GitLab documentation [2], says that key
finger prints should be unique, and it's enough to add it to one's account.

[2] https://docs.gitlab.com/ee/ssh/

I assume that Salsa takes my identify from the public key that the Salsa
server accepts. But is this assumption correct?

Now I am a bit at a loss about what the cause of this failure to push to
the repository could be. And at the moment I won't know how to resolve this.

Teus.