Package Details: gitosis-git 0.2.r49.gdedb3dc-2

Git Clone URL: https://aur.archlinux.org/gitosis-git.git (read-only, click to copy)
Package Base: gitosis-git
Description: Software for hosting git repositories - git checkout
Upstream URL: https://github.com/tv42/gitosis
Licenses: GPL2
Conflicts: gitosis
Provides: gitosis
Submitter: alperkanat
Maintainer: None
Last Packager: eworm
Votes: 35
Popularity: 0.000000
First Submitted: 2009-01-24 23:29 (UTC)
Last Updated: 2015-06-30 08:02 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5

<deleted-account> commented on 2010-10-27 00:56 (UTC)

@alperkanat Thanks! I think it was a problem with my system... I kept creating new groups and they all got GID 99. I ended up doing some looking and fixing it.

alperkanat commented on 2010-10-26 08:58 (UTC)

@wsduvall: updated the package with permissions fix. the GID problem was old bug that has been fixed a few months ago but I can't find the bug report right now. so maybe you could try updating your system and reinstall gitosis-git package. if the problem continues, you can fill a bug report because gitosis-git package does nothing but to use groupadd -r command.

<deleted-account> commented on 2010-10-26 01:22 (UTC)

Pretty sure you're supposed to do chmod 700 on /srv/gitosis (see the wiki), also this pkg is creating the git group with the same GID as nobody (99).

alperkanat commented on 2010-10-20 22:13 (UTC)

updated the package with python2, thanks!

alperkanat commented on 2010-10-20 06:51 (UTC)

thanks for your support, will do it asap

<deleted-account> commented on 2010-10-20 00:45 (UTC)

With the python2.x -> python3.x upgrade, this will no longer build because it needs setuptools, which is available only for python2.x, but uses python, which is now python3.x. The fix is easy: Replace the dependence on python with one on python2. A tar-file that fixes this can be found at http://www.cs.dal.ca/~nzeh/gitosis-git.tar.gz. If you could upload it, that would be great.

alperkanat commented on 2010-08-08 21:18 (UTC)

in fact, it's not. because of downloading the latest version from git, it never goes out of date when you install it unless the upstream development is stopped. but i'll update the package revision so that everyone can update to the latest one.

exterm commented on 2010-08-06 18:05 (UTC)

The link given lists the last commit as 2009-09-17 so This package is out of date, right?

« First ‹ Previous 1 2 3 4 5