This seems to be truncated, could you provide the entire output?

Hello pingou, unfortunately that's the output that we have... It is truncated.

I've also been looking at this, Its truncated because the git protocol is expecting a file size header and instead is receiving a string. I'm not sure about pagure, but in github or a raw git server when your ssh key doesn't have access to a repo it'll say "No such project" or similar error, and I think thats what its sending here.

More info and my full reproducer in a clean container system:

Load one of your deploy keys:

# ssh-add -l
4096 SHA256:wSoAmC..blahblah...ugD9//4w9fMk /root/.ssh/pagure (RSA)

clone normal repo fine:

# git clone --progress --verbose  ssh://git@pagure.io/greenwave.git greenwave
Cloning into 'greenwave'...
remote: Counting objects: 2404, done.
remote: Compressing objects: 100% (848/848), done.
remote: Total 2404 (delta 1612), reused 2326 (delta 1542)
Receiving objects: 100% (2404/2404), 535.34 KiB | 1.26 MiB/s, done.
Resolving deltas: 100% (1612/1612), done.

Cloning doc repo is broken:

# GIT_SSH_COMMAND="ssh -v" git clone --progress --verbose  ssh://git@pagure.io/docs/greenwave.git docs-on-pagure
Cloning into 'docs-on-pagure'...
 ... skipping most of this ...
Authenticated to pagure.io ([152.19.134.147]:22).
debug1: Sending environment.
debug1: Sending command: git-upload-pack '/docs/greenwave.git'
fatal: protocol error: bad line length character: No s

@pingou Hi, I just tested publishing a doc using a deploy key. It seems to me this issue still occurs :(

Can you help take a look?

This issue is 5 years old, we changed a ton of code that could be related since then. I'm closing this one for now, if the problem still exist based on the current master branch or upcoming 6.0 release, please re-open.