trac/git sandbox

[strk]

It'd be nice to have a trac instance to play with for testing git integration.

Interesting points to deal with:

1: Check how to reference commits from tickets/wiki (ala r###) 2: Check what happens to old references (r###) -- should they be converted ? Is there an automatism for that ?

[wildintellect]

For fresh repositories, references would now be based on git Hashes.

For old repositories converted to git from svn something like the following would need to be run to maintain linkage by updating revision numbers to git Hashes. ​https://github.com/poseidix/TRAC-SVN-to-GIT-migration

I'm still looking for details on the syntax to reference a specific commit in a ticket without memorizing crazy hashes or copy/paste.

Suggested approach to this issue is to setup a new Trac instance with the latest Trac that supports multiple repos and create a test git repo or two for testing.

[wildintellect]

We'll put this into the TODO list for the upcoming install of Trac 0.12 - look for more planning details on the SAC list in the next few weeks.

[aboudreault]

If this still in your plan, We would like to use git for our repository of UbuntuGIS. It would be easier for us to collaborate with the git of debianGIS.

[hamish]

It would be easier for us to collaborate with the git of debianGIS.

n.b. we (meaning mostly Frankie) have only migrated about half the projects in DebianGIS to git, the other half remain in Svn.

fwiw, Hamish

[aboudreault]

Any update on this?

[strk]

Can this be done now that we're running 1.0.5 ?

[martin]

This one is using GIT for the source repo:

​https://trac.osgeo.org/martin/

I just didn't get to the point of installing a functional system for remote access control on the GIT repo - any "best practice" recommendation regarding this item ?

[strk]

I have no experience with setting up a multi-user git repo, but wouldn't allowing ssh login to developers on the "git" machine give all the needed power ? Or would it be too much ?

[strk]

This page talk about using a single "git" user (ala github) and ssh authorized keys to login: ​http://tumblr.intranation.com/post/766290565/how-set-up-your-own-private-git-server-linux

[strk]

And this ​http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way/ gives more tips to make it easier to create new repositories.

[strk]

Once the "git" user is setup (further restrictions to it can be given via ​https://git-scm.com/docs/git-shell) you may want to look at gitolite for easy management of repositories. gitolite seems to be packaged by debian, contrary to gitosis (the one referenced by scie.nti.st)

[strk]

Actually, I've just tried "gitolite3", and it does everything by itself, no need to manually create a "git" user (the packaged version installs a "gitolite3" user) - I guess it could later be changed (or aliased) to be "git"

[strk]

nvh reported this tool which might be useful to convert trac references from SVN revisions to GIT commits, for specific projects that want to switch: ​https://github.com/seantis/git-svn-trac

[strk]

Shall gitolite be choosen, there's a trac plugin for it: ​https://trac-hacks.org/wiki/GitolitePlugin

[strk]

In alternative to gitolite, it might be simpler to just setup https access to git: ​https://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.html

LDAP over HTTPS being already implemented for SVN, this could be the easiest path

[martin]

What about this one - anonymous, but fast read-only:

​git://git.osgeo.org/gittest/

Slower, but allowing authenticated commits (use your OSGeo LDAP password):

​https://<user>@git.osgeo.org/git/gittest/

[strk]

That's perfect. I guess next stop would be testing multiple-repositories, to make it easier for those coming from SVN to have a period of keeping both alive, maybe with ticket comments being able to refer to either of the two repo (so old ones can remain untouched and new one can point to the git repo, for example).

The other use case for multiple repository would be allowing for different project components to be in different repositories (think website, for instance).

[strk]

I've filed the multiple-repository ticket on the gittest repo: ​https://trac.osgeo.org/gittest/ticket/3

[strk]

Could I get admin access to the "gittest" repo, to continue the multi-repo research ? I'd like to setup a git repo under the "geos" trac instance in addition to the existing SVN repo.

[strk]

I tried creating a repo for "php-geos" but right now I'm failing to push changes in it. The error I get is 'receive-pack': service not enabled on the server side

[strk]

As a followup, php-geos works fine now (probably only took an apache restart). I don't know if this ticket still need to stay open, we can create git repos an attach them (even multiple ones) to trac instances.

[strk]

Closing as done. See #1650 for next sandbox ...