Re: [gitorious] problem cloning repo via https access
On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: Hi, some time in the past I must have been able to clone repos via https since my dev. machine is behind a natting firewall-proxy allowing http(s) access only. And up to now I didn't experience any problem pulling from these repos. But recently I had to clone a repo to a new machine and suddenly I was presented with the following message: git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.git seife Cloning into 'seife'... warning: remote HEAD refers to nonexistent ref, unable to checkout. The issue here is that our Git-over-HTTP service uses the dumb HTTP protocol; which pulls down commits one by one. The first thing that this service does is to try to locate the HEAD of the repository; which should point to a valid ref (branch). It looks like the HEAD reference on this repository points to a non-existing ref. The owner of the repository should be able to change which branch HEAD points to in the repository using the Gitorious UI. -- Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] http protocol option broke
On Tue, Aug 07, 2012 at 07:54:10AM -0700, Rich Kucera wrote: On Tuesday, July 31, 2012 5:51:53 AM UTC-4, Marius Mårnes Mathiesen wrote: On Mon, Jul 30, 2012 at 4:33 PM, Rich Kucera kucerarich...@gmail.comwrote: Background: We're trying to adopt git, enterprise inhouse, with gitorious stack from bitnami (saved a lot of work...). ssh works fine, git protocol does not due to firewall and that's ok (I proved it works on my laptop). Because of some internal partitioning, we can't ssh in both directions. This is OK, because I can still push the repositories in one direction for deployments. That's the last option. Well rsync push was the last option tried, but git is now perceived as partially working. Problem: HTTP protocol does not work in any case. It says you appear to have cloned an empty repository when I know there is stuff in the repository. If I had http, then presumably there'd be a pull option for deployment in addition to the single push option I have left. Rich, Did you set up modxsendfile on the server and point this to the correct location? Gitorious assumes this Apache module is installed and configured so it intercepts headers like X-Sendfile: pointing to the path where the git repository resides on disk. There's a page on the wiki outlining this and other components in Gitorious here: https://gitorious.org/gitorious/pages/GitoriousComponents#HTTP+cloning++ _Marius Thanks Marius, mod_xsendfile is not there in the bitnami stack apache modules directory. Guess the options are now: - compile in and configure xsendfile into bitnami stack and go through that nightmare, probably will learn a lot. - duct tape it with rsync push to remote nodes from local staging repo - configure minimal git ssh on remote nodes to handle git push instead of git pull at remote, still requires staging repo to push from. - check out TeamForge.. Rich, One thing you could do to get up and running really quickly (with the necessary Apache modules) is to use our brand new installer from http://getgitorious.com/ There's an installer you can run on a clean CentOS 6.3 machine (fully automated), and even a virtual appliance that comes preconfigured. Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
[gitorious] Upgraded Rails for Gitorious
I've now pushed commits to mainline:next that upgrades our Rails version: - Unvendor Rails (i.e. rm -fr vendor/rails, configure Rails in Gemfile) - Upgrade from 2.3.5 to 2.3.14 This means we're no longer on a completely ancient version of Rails. There has been some non-trivial changes in Rails between the two versions, so please report if you find any oddities. The two main things to look out for are: 1) Strangely translated text (I made quite a few changes to how our internationalization was implemented, to accommodate newer versions of I18N) 2) Over-eager HTML escaping. Will likely manifest as broken UI. Our tests does not cover the HTML generation very exhaustingly, but I've surfed through quite a bit, and it looks OK to me. Please beware that the next branch with this change is on the risky side. We'll be using it on our internal setup for a little while before merging to master and deploying on gitorious.org. If you have setups that can take a visual bug or two, please try it out and help us find bugs. How does this upgrade help us? 1) Lots and lots of bug fixes from the Rails team, including security patches 2) Tackled some deprecated APIs and flat out failing things that will help us move on to Rails 3 3) Solves a dependency deadlock involving Rack, that has made my integrating the new code browser, uhm, challenging 4) Solves the problem of your rubygems is to new, please downgrade For end users the upgrade is unlikely to bring any visual changes. -- MVH Christian -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] problem cloning repo via https access
Thank you for the quick answer. I will forward it to the repo owner. Am Donnerstag, 18. Oktober 2012 10:21:20 UTC+2 schrieb Marius Mårnes Mathiesen: On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: Hi, some time in the past I must have been able to clone repos via https since my dev. machine is behind a natting firewall-proxy allowing http(s) access only. And up to now I didn't experience any problem pulling from these repos. But recently I had to clone a repo to a new machine and suddenly I was presented with the following message: git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.gitseife Cloning into 'seife'... warning: remote HEAD refers to nonexistent ref, unable to checkout. The issue here is that our Git-over-HTTP service uses the dumb HTTP protocol; which pulls down commits one by one. The first thing that this service does is to try to locate the HEAD of the repository; which should point to a valid ref (branch). It looks like the HEAD reference on this repository points to a non-existing ref. The owner of the repository should be able to change which branch HEAD points to in the repository using the Gitorious UI. -- Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] problem cloning repo via https access
Hi, thank you for the quick answer that I forwarded to the repo owner. Unfortunately it didn't change the situation. He reported that HAED points to MASTER and there are no branches in his repo. Any other ideas what might be wrong or how to fix this? Am Donnerstag, 18. Oktober 2012 10:21:20 UTC+2 schrieb Marius Mårnes Mathiesen: On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: Hi, some time in the past I must have been able to clone repos via https since my dev. machine is behind a natting firewall-proxy allowing http(s) access only. And up to now I didn't experience any problem pulling from these repos. But recently I had to clone a repo to a new machine and suddenly I was presented with the following message: git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.gitseife Cloning into 'seife'... warning: remote HEAD refers to nonexistent ref, unable to checkout. The issue here is that our Git-over-HTTP service uses the dumb HTTP protocol; which pulls down commits one by one. The first thing that this service does is to try to locate the HEAD of the repository; which should point to a valid ref (branch). It looks like the HEAD reference on this repository points to a non-existing ref. The owner of the repository should be able to change which branch HEAD points to in the repository using the Gitorious UI. -- Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
