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

Git Clone URL: (read-only)
Package Base: gitosis-git
Description: Software for hosting git repositories - git checkout
Upstream URL:
Licenses: GPL2
Conflicts: gitosis
Provides: gitosis
Submitter: alperkanat
Maintainer: eworm
Last Packager: eworm
Votes: 37
Popularity: 0.000000
First Submitted: 2009-01-24 23:29
Last Updated: 2015-06-30 08:02

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

rumtata commented on 2013-12-25 19:51

PKGBUILD improvements could be made by warning a user if "git" user exists (from other setup). This could be further checked if /srv/gitosis directory exists

rumtata commented on 2013-12-25 19:42

PKGBUILD should create /srv/gitosis directory if it does not exist before trying to chmod/chown it to gitosis user during install.

andrej commented on 2013-07-26 21:37

There are more issues:
1) There's no /usr/share/doc/gitosis, so it should be either added or *not* promised in the output.
2) Something related to /srv/gitosis fails (no such file or directory).

eworm commented on 2013-05-03 09:42

Please update you PKGBUILD for new pacman/makepkg:

slopjong commented on 2013-04-22 11:12

Or maybe create the user and group 'gitosis' as debian does. Then both, the 'git' and 'gitosis' users, can have their own home directory.

slopjong commented on 2013-04-22 11:00

Your PKGBUILD shouldn't try to create the 'git' user because the git package (dependency) already creates it. Your post_install() fails when trying to create an already existing user.

Instead create the gitosis directory and change gitosis' home:

In your PKGBUILD: mkdir -p "$pkgdir"/srv/gitosis
In your install script: usermod -d /srv/gitosis git

alperkanat commented on 2012-06-19 21:31

@aapzak: infact you're right. updating the package..

aapzak commented on 2012-06-19 20:01

@alperkanat: I don't have objections to using the git user but I really don't want my repositories to be deleted if I uninstall this package. Why not just delete the user but keep the files?

alperkanat commented on 2012-04-19 15:30

@Polizei: any suggestions? The only way I can think of is to create a user & group with a unique name which is unlikely to collide with user created ones. However, git user and group are supposed to be system objects (which are smallar than minimum uid & gid) and users are supposed to take care of the naming.

Anonymous comment on 2012-04-19 15:19

Yeah, nice. Seems that you've updated the package removal hooks and now it's probably even more shit than before -- pkg_remove() destroys the `git' user.

alperkanat commented on 2012-04-18 09:39

thanks to Igor Vinokurov, updated the package with package removal fixes.

alperkanat commented on 2012-04-03 16:17

Updated the package.

Anonymous comment on 2012-04-03 04:29

I get permission denied. He moved his repo. Update the URL and git_root to be this:

alperkanat commented on 2012-04-02 18:58

I believe you mean the movement to github of upstream? I just created an updated AUR package but cannot upload atm since I'm on my iPad. I'll be updating this package asap when I get my hands on my computer. Thanks @nickray!

Anonymous comment on 2012-04-02 16:46

It seems the maintainer has moved his repo to gitosis but not adjusted the PKGBUILD?

alperkanat commented on 2012-02-13 12:36

added git as a dependency. thanks

Anonymous comment on 2012-02-11 17:38

Yeah. You might want to add git as a dependency (or at least a suggested one, as nothing works without it)

alperkanat commented on 2012-01-23 09:06

sorry i missed tuxce's message, updated the package again. thanks @tuxce

alperkanat commented on 2012-01-23 09:03

updated the package. sorry for the delay and thanks to @ksira

ksira commented on 2011-12-06 11:37

I had an error using makepkg from pacman 4.0.1 with this PKGBUID
I had to remove the parenthesis from around the install file name:
Hope that helps.

Anonymous comment on 2011-08-29 21:34

Nevermind, I just realized that gitosis-git was added to archlinuxfr and it changed the permissions to /srv/gitosis to 700, it requires 711 to work.

Anonymous comment on 2011-08-29 06:23

Hi, just updated the package and now I'm receiving a 404 - No projects found error, I've checked all the permissions etc and dug through config files but can't find anything wrong. Know why this recent update would have borked things?

tuxce commented on 2011-08-27 12:09

Hi, gitosis-init need pkg_resources module which is provided by python2-distribute.
python2 and python2-distribute should be in "depends" not "makedepends".

alperkanat commented on 2011-08-19 07:15

the author reactivated his git repositories, so the package should start being built without any need for an update. you should create the folder and set it as gitosis' users home. please check if there are any existing gitosis or git users in your /etc/passwd and /etc/group files. that might be the reason if you installed gitosis manually or in any other way.

josemota commented on 2011-08-18 16:55

@alperkanat no problem. I had trouble installing it for a couple of hours and went digging.
Hey btw, how can I turn around the /srv/gitosis issue? Creating the folder isn't enough, right? What should I do?
Thanks for helping, Alper.

alperkanat commented on 2011-08-18 16:14

@josemota: thanks for the notice! i sent an e-mail to its author to notify him about the issue. meanwhile, i'll update the package asap. that github url seems to be the author's repositories so it's a possible reason why he might have killed his own repo.

josemota commented on 2011-08-18 16:04

@alperkanat, the package needs an update. The URL is ill, i've found to be trustful.

alperkanat commented on 2011-04-12 13:31

it's created by user addition of git(osis) so it has nothing to do with this package.. useradd command is used to add the user.

Anonymous comment on 2011-04-12 13:29

/srv/gitosis does not create successfully

ChojinDSL commented on 2011-03-16 12:26

Update... Ok I managed to resolve the issue.

python2-setuptools needs to be installed.

I had python2-distribute installed, which seemed to conflict with python2-setuptools.

I simply uninstalled python2-distribute and installed python2-setuptools.

ChojinDSL commented on 2011-03-16 10:55

When I try to run gitosis-init as specified in the Arch Wiki, I get the following:

sh-4.2$ gitosis-init < /srv/
Traceback (most recent call last):
File "/usr/bin/gitosis-init", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/", line 2691, in <module>
add_activation_listener(lambda dist: dist.activate())
File "/usr/lib/python2.7/site-packages/", line 668, in subscribe
File "/usr/lib/python2.7/site-packages/", line 2691, in <lambda>
add_activation_listener(lambda dist: dist.activate())
File "/usr/lib/python2.7/site-packages/", line 2192, in activate
File "/usr/lib/python2.7/site-packages/", line 2299, in insert_on
File "/usr/lib/python2.7/site-packages/", line 2338, in check_version_conflict
for modname in self._get_metadata('top_level.txt'):
File "/usr/lib/python2.7/site-packages/", line 2186, in _get_metadata
for line in self.get_metadata_lines(name):
File "/usr/lib/python2.7/site-packages/", line 1174, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/usr/lib/python2.7/site-packages/", line 1166, in get_metadata
return self._get(self._fn(self.egg_info,name))
File "/usr/lib/python2.7/site-packages/", line 1281, in _get
stream = open(path, 'rb')
IOError: [Errno 13] Permission denied: '/usr/lib/python2.7/site-packages/soaplib-1.0.0_beta8-py2.7.egg-info/top_level.txt'

If run the gitosis-init command as root its fine. But not if I try to run it as the git user, either via sudo or directly as the git user.

canton7 commented on 2011-02-08 09:14

See the repository owner's blog here: and github README here:
If, for example, you have a number of repositories in dir/ which are all writable by the same group, it allows you to write
[group mygroup]
members = jdoe
writable = dir/*

instead of specifying each repository individually.

alperkanat commented on 2011-02-07 23:57

Hello canton7,

What are wildcards are used for?

canton7 commented on 2011-02-07 23:54

I've created a package of a fork which supports wildcards for the 'writable' attribute here:

Anonymous comment on 2011-01-17 06:14

Ah, it appears reinstalling python2-distribute fixes this issue.

Anonymous comment on 2011-01-16 16:30

I'm still having a problem...

alperkanat commented on 2011-01-13 17:25

corrected the pkgbuild, thanks for warning!

notizblock commented on 2011-01-11 13:28

i used python2-distribute instead of python2-setuptools

alperkanat commented on 2010-12-21 20:46

thanks for warning.. updated the package.

Anonymous comment on 2010-12-21 18:48

You need to change setuptools to python2-setuptools in the dependencies.

Anonymous comment on 2010-10-27 00:56

@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

@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.

Anonymous comment on 2010-10-26 01:22

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

updated the package with python2, thanks!

alperkanat commented on 2010-10-20 06:51

thanks for your support, will do it asap

Anonymous comment on 2010-10-20 00:45

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 If you could upload it, that would be great.

alperkanat commented on 2010-08-08 21:18

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

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