This is the last call for comments for the review of debconf templates for gitolite. The reviewed templates will be sent on Sunday, August 01, 2010 to the package maintainer as a bug report and a mail will be sent to this list with "[BTS]" as a subject tag. (maintainer: explicit CC, as I suspect you aren't getting other mails in this process) -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Source: gitolite Section: vcs Priority: optional Maintainer: Gerfried Fuchs <firstname.lastname@example.org> Build-Depends: quilt Build-Depends-Indep: po-debconf Standards-Version: 3.8.4 Homepage: http://github.com/sitaramc/gitolite Vcs-Browser: http://git.deb.at/w/pkg/gitolite.git Vcs-Git: git://git.deb.at/pkg/gitolite.git Package: gitolite Architecture: all Depends: git (>= 1:220.127.116.11) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16), openssh-server | ssh-server, debconf (>= 0.5) | debconf-2.0, adduser Suggests: git-daemon-run, gitweb Description: SSH-based gatekeeper for git repositories Gitolite is an SSH-based gatekeeper providing access control for a server that hosts many git repositories. Without gitolite, each developer needing to push to one of the repositories hosted would need a user account on that server; gitolite lets you do that just using SSH public keys tied to a single, common, user that hosts all the repositories. . Gitolite can restrict who can read (clone/fetch) from or write (push) to a repository, and who can push to what branch or tag - an important issue in corporate environments. Other features include: * access control by branch-name or by modified file/directory; * per-developer "personal namespace" prefixes; * simple but powerful configuration file syntax (with validation); * config files (and authority for maintaining them) can be split; * easy integration with gitweb; * comprehensive logging; * easy migration from gitosis.
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # email@example.com for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: gitolite/gituser Type: string Default: gitolite _Description: System username for gitolite: Please enter the name for the system user which should be used by gitolite to access repositories. It will be created if necessary. Template: gitolite/gitdir Type: string Default: /var/lib/gitolite _Description: Repository path: Please enter the path in which the gitolite repositories should be stored. This will become the gitolite system user's home directory. Template: gitolite/adminkey Type: string _Description: Administrator's SSH key: Please specify the key of the user that will administer the access configuration of gitolite. . This can be either the SSH public key itself, or the path to a file containing it. If it is blank, gitolite will be left unconfigured and must be set up manually.
Description: Digital signature