Opened 14 years ago
Closed 15 months ago
#604 closed defect (invalid)
soc dvcs repository doesn't work
Reported by: | wolf | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Sysadmin Contract 2023-II |
Component: | SysAdmin | Keywords: | dvcs, git, soc |
Cc: |
Description
Git cloning works well with git.osgeo.org using either https://git.osgeo.org/soc or https://wolf@git.osgeo.org/soc.
But when I try to push my changes to the repository I need to give my password twice AND I get this error: Unable to create branch path https://wolf@git.osgeo.org/soc/info/ error: cannot lock existing info/refs fatal: git-http-push failed
Problem is we'd need to get this fixed asap, since one of our students needs a repository (yeah sorry for the short notice).
--Wolf
Change History (4)
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Replying to hamish:
morning Wolf,
since in a hurry, I suggest to get the student to submit to Github. Git should be quite simple to migrate to a new home later, it's just a matter of verbally declaring the other tree to be the "primary" one to pull from, right?
That's true. :) Thanks for the hint. I'll set up another temp repo, but then that requires them to register at yet another system :P
--Wolf
comment:3 by , 13 years ago
Priority: | blocker → minor |
---|
Not currently relevant, so marking as minor. We should take another look at this in the near future to have infrastructure to support git in general.
- Multi repo support with trac 0.12 upgrade
- git-web for http/s checkouts
- gitolite for management of user permissions via ssh key?
comment:4 by , 15 months ago
Milestone: | → Sysadmin Contract 2023-II |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Not relevant in 2023. Closing as invalid.
soc
= for Summer of Code, currently each project participating organizes where to work- gitea is been used now
- no problems on
push
reported. - There is no soc` repository in gitea.
- no problems on
morning Wolf,
since in a hurry, I suggest to get the student to submit to Github. Git should be quite simple to migrate to a new home later, it's just a matter of verbally declaring the other tree to be the "primary" one to pull from, right?
Hamish