The issue was that for some reason, git-daemon-export-ok was not created.

We can either try to create that, or add SetEnv GIT_HTTP_EXPORT_ALL to the config.

I just tried to replicate this and it worked for me, should we close this ticket?

It seems like git-daemon-export-ok is not always being generated.
I've seen a case where a newly generated repo did not have that file at creation, but did get it magically later on.

It seems like git-daemon-export-ok is not always being generated.
I've seen a case where a newly generated repo did not have that file at creation, but did get it magically later on.

I wonder if your fix for multiple ssh key wouldn't fix also this then (by having
gitolite called in one place only).

Now that 0.1.27 is deployed, we should see if this issue is still valid :)

Unfortunately, it is:

$ git clone -vvv https://pagure.io/clufter.git
Cloning into 'clufter'...
fatal: repository 'https://pagure.io/clufter.git/' not found

while, on the other hand:

$ git clone -vvv https://pagure.io/pagure.git
Cloning into 'pagure'...
Server supports multi_ack_detailed
Server supports no-done
Server supports side-band-64k
Server supports ofs-delta
Server version is git/1.8.3.1
want 32086450ca79da9d7f072f4911e0a0c5f06bf1c4 (HEAD)
want 32086450ca79da9d7f072f4911e0a0c5f06bf1c4 (refs/heads/front_page)
[...]
done
POST git-upload-pack (gzip 1640 to 825 bytes)
remote: Counting objects: 16526, done.
remote: Compressing objects: 100% (6964/6964), done.
remote: Total 16526 (delta 12477), reused 12574 (delta 9491)
Receiving objects: 100% (16526/16526), 5.52 MiB | 1.09 MiB/s, done.
Resolving deltas: 100% (12477/12477), done.
Checking connectivity... done.

Yeah, I saw it also yesterday, let me fix the clufter project real quick and then see for a 'real' fix

clufter should be fixed

Ok so https://pagure.io/pagure/pull-request/423 should fix this

That PR has been merged and is part of 0.1.28 that pagure.io is currently running, so we should be fine for this.

Let's re-open if it happens again