-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git-receive-pack error #17
Comments
I'm not sure what's going on, other than the client (I think) is trying to use one variant of the protocol we don't yet support. From a quick read of the current protocol docs, I can't immediately see why it's trying to use I think I'll need to reproduce the issue locally to understand it. I'll try to do this in the next few days. |
Is it a possibility that GOGS does use |
@ceremcem I'm sorry that I still haven't looked into this. Can you give me access to a copy of the repository where this happens? |
I've e-mailed the login credentials just now. I experienced that problem with any repository in my server, so any trivial repo should give the same error. |
I was able to reproduce the git-receive-pack calls (even though I wasn't yet testing the cache) on both your Gogs instance and GitHub. So it's easier to just add support for it... Can you by any chance look into that? (I'm still curious as to why the problem didn't happen before with GitHub, but I don't think there's much point investigating into it now) |
Any updates? |
I checked the protocol specification (and its implementation in git) and the The current version of the project only supports |
I have a dedicated git repo backed by GOGS, which is served behind Nginx proxy and has an url like
https://example.com/git
, so the repobar
under userfoo
is named ashttps://example.com/git/foo/bar
.My
git-cache-http-server
setup works correctly for Github but not for my dedicated server. What isgit-receive-pack
error? How can I workaround this?The error I've got from the failing git repo is like so:
Systemctl status is as follows:
The text was updated successfully, but these errors were encountered: