Package: gitosis
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Sunday, February 08, 2009, I notified you of the beginning of a review
process
concerning debconf templates for gitosis.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading gitosis with these changes
right now.
The second phase of this process will begin on Sunday, March 01, 2009, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Sunday, March 22, 2009. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Monday, March 23, 2009, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- gitosis.old/debian/gitosis.templates 2009-02-03 06:07:28.691032045
+0100
+++ gitosis/debian/gitosis.templates 2009-02-26 06:16:26.523607545 +0100
@@ -1,44 +1,46 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
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
- gito...@example.com:foo.git'.
+Default: gitosis
+_Description: Dedicated system account for gitosis:
+ Repositories are managed by gitosis under a single system account, using SSH
+ keys to identify users. This account name is part of the clone
+ URL when checking out over SSH, leading to commands such as "git clone
+ gito...@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.
+ The account name can be customized but you should not use an existing
+ account.
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.
+Default: /srv/gitosis
+_Description: Directory for git repositories?
+ Please specify the directory where gitosis will manage the git repositories.
.
If you choose an already existing directory, this installation process
- will not touch it.
+ will leave it unmodified.
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 gito...@example.com:gitosis-admin.git'. See ssh-keygen(1) for more
- information about generating SSH keys.
+Default:
+_Description: SSH public key for the gitosis admin repository:
+ Configuration for gitosis is stored in a file named "gitosis.conf"
+ which is kept in the gitosis-admin repository.
.
- 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.
+ Access to this repository is controlled through an SSH public key.
.
- If there is already an initialized gitosis-admin repository in your
- gitosis directory, this installation process will not touch it.
+ You can specify an existing key by entering the name of the key file
+ or by pasting the key content itself here. Alternatively, you can leave
+ that field empty and configure the key manually later after
+ reading the /usr/share/doc/gitosis/README.Debian file.
.
- In order to add new project repositories, please read
- /usr/share/doc/gitosis/README.rst for more information about the format of
- gitosis.conf.
+ If there is already an initialized gitosis-admin repository in the
+ gitosis directory, this installation process will not touch it.
--- gitosis.old/debian/control 2009-02-03 06:07:28.691032045 +0100
+++ gitosis/debian/control 2009-02-11 18:46:16.096669678 +0100
@@ -12,7 +12,7 @@
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
+ This package aims to make hosting git repositories 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
+ users do not need shell accounts on the server; they will talk to one shared
account that will not let them run arbitrary commands.
