There is an issue where the changes on the cloned repository can't be pushed.
Here a paste showing both client and server logs. https://paste.ubuntu.com/p/FDgxWj39zP/
I've reached #gitolite at freenode and some tips and bits are these,
<sitaram> Ark74: that error is pretty common when you bypass gitolite and try to directly access a repo using the actual, "on disk" pathname ... <sitaram> Ark74: looking at https://pagure.io/pagure/blob/master/f/pagure/hooks/__init__.py#_500, where it is using GL_USER, it seems pagure itself is run from gitolite, because it is gitolite that normally sets that variable
Still researching.
Updating conversation (2018-11-30),
<sitaram> Ark74: what it appears to be doing is reporting a directory as not found, which we already know exists (from gitolite's messages) <sitaram> so the thing to look for might be: what is pagure's definition of "found a "GitDir" <sitaram> Ark74: looking at https://pagure.io/pagure/blob/master/f/pagure/lib/git.py#_1313 ... <sitaram> maybe something in how you're supposed to configure pagure <sitaram> I called in a pythonista friend to my desk <sitaram> Ark74: here's what that code is doing <sitaram> lines 1332-1336 pick up some paths from your pagure config <sitaram> the next block says this "gitdir" we have, MUST start with one of those 4 paths you just picked up from pagure config <sitaram> if /opt/pag_01/<whatever> does not have ANY of those 4 paths as a prefix, it's not a pagure directory of any sort, and we bail out <sitaram> all 4 paths are optional too <sitaram> so... either you did not define ANY of them in your pagure config (whatever and wherever that is) <sitaram> or you did but none of them are a prefix match for /opt/pag_01/repositories/NotArk_01.git
Fixed by https://pagure.io/pagure-installer-trisquel/c/08bab2ae18dc5bac82717ae5d4291d567d2f1f4a
Metadata Update from @ark74: - Issue status updated to: Closed (was: Open)
Metadata Update from @ark74: - Issue assigned to ark74