The gitosis package introduced new or modified debconf templates. This is the perfect moment for a review to help the package maintainer following the general suggested writing style and track down typos and errors in the use of English language. If someone wants to pick up this review, please answer to this mail, in the mailing list, with an [ITR] (Intent To Review) label. The templates file is attached. To propose the file you reviewed for peer review, please send a [RFR] (Request For Review) mail with the reviewed file attached...then a few days later, when no more contributions come, a summary mail with a [LCFC] (Last Chance For Comments) label. Finally, after no more comments coming to the LCFC mail, you can send the reviewed templates file as a bug report against the package. Then, please notify the list with a last mail using a [BTS] label with the bug number. Helping the package maintainer to deal with induced translation updates at that moment will be nice. If you're not comfortable with that part of the process, please hand it off to a translator. --
Template: gitosis/username Type: string _Default: gitosis _Description: What system account should be created for gitosis? gitosis manages all git repositories under one system account, using SSH keys to identify users. The name of the system user is part of the clone URL when checking out over SSH, e.g. 'git clone gitosis@example.com:foo.git'. . By default this username is 'gitosis'. You can change this but make sure that for security reasons you do use a dedicated account solely for gitosis. Template: gitosis/directory Type: string _Default: /srv/gitosis _Description: What directory should be used to store repositories? The directory where gitosis will manage the git repositories is set by default to /srv/gitosis. You can change this if you like. . If you choose an already existing directory, this installation process will not touch it. Template: gitosis/key Type: string _Default: _Description: Enter the SSH public key for accessing the gitosis admin repository (either absolute filename or by pasting the actual key) gitosis is configured through gitosis.conf that is stored within the gitosis-admin repository. Access to this repository is controled through an SSH public key. In order to initialize this respository, you can enter such an SSH public key here and you will be able to clone it through 'git clone gitosis@example.com:gitosis-admin.git'. See ssh-keygen(1) for more information about generating SSH keys. . If you don't want to initialize the gitosis-admin repository now, you can leave this question empty and read in /usr/share/doc/gitosis/README.Debian how to initialize it manually. . If there is already an initialized gitosis-admin repository in your gitosis directory, this installation process will not touch it. . In order to add new project repositories, please read /usr/share/doc/gitosis/README.rst for more information about the format of gitosis.conf.
Source: gitosis
Section: admin
Priority: optional
Maintainer: Daniel Baumann <daniel@debian.org>
Build-Depends: debhelper (>= 7), quilt, po-debconf, python-dev, python-setuptools (>= 0.6c5), python-support
Standards-Version: 3.8.0
Vcs-Browser: http://git.debian.net/?p=debian/gitosis.git
Vcs-Git: git://git.debian.net/git/debian/gitosis.git
Package: gitosis
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, adduser, git-core (>= 1:1.5.0), openssh-server, python-setuptools (>= 0.6c5), sudo
Suggests: git-daemon-run, gitweb
Description: git repository hosting application
gitosis aims to make hosting git repos easier and safer. It manages multiple
repositories under one user account, using SSH keys to identify users. End
users do not need shell accounts on the server, they will talk to one shared
account that will not let them run arbitrary commands.
Attachment:
signature.asc
Description: Digital signature