Package: zope-common
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Tuesday, July 03, 2007, I notified you of the beginning of a review process
concerning debconf templates for zope-common.
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 are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading zope-common with these changes right now.
The second phase of this process will begin on Saturday, July 21, 2007, 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 Saturday, August 11, 2007. 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 <DAY25>, 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: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- zope-common.old/debian/templates 2007-06-25 20:41:56.553019815 +0200
+++ zope-common/debian/templates 2007-07-18 20:06:42.828496549 +0200
@@ -1,105 +1,109 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [EMAIL PROTECTED] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: shared/zope/restart
Type: select
_Choices: configuring, end, manually
Default: end
_Description: Automatic restart of Zope instances:
- Zope has an extensible, modular structure that allows you to easily
- add extra components (products) or features. Each product or feature
- can usually be found in packages whose name starts with a 'zope-'
- prefix. Unfortunately, each Zope instance needs to be restarted to
- use any new add-on. Here you can choose the default behaviour of
- Zope instances in any installed Zope version when Zope needs to be
- restarted. Each instance, however, is allowed to overwrite this
- setting:
- .
- * configuring: restart instances after each product configuration.
- * end: restart instances only once at the end of the whole
- installation/upgrading process.
- * manually: no restart, it is your responsibility to restart
- Zope instances.
+ Zope offers an extensible, modular structure that allows for the easy
+ addition of extra components (products) or features. These are
+ provided as packages with names that start with a 'zope-' prefix.
+ Each Zope instance needs to be restarted to use any new add-on.
+ .
+ Please choose the default behavior of Zope instances when Zope needs
+ to be restarted:
+ .
+ - configuring: restart instances after each product configuration;
+ - end: restart instances only once at the end of the whole
+ installation/upgrading process;
+ - manually: no automated restart.
Template: zope-common/remove-instance-without-data
Type: select
_Choices: abort, remove and continue
Default: abort
-_Description: Found an old/incomplete zope instance '${instance}':
- Found an old/incomplete ${instance} instance in
- /var/lib/zope${zver}/instance/${instance}. No data file Data.fs was found
- for the instance, meaning that the installation was not completed
- for some reason, or the installation was incompletely removed.
- Aborting the installation will allow you to inspect the state of the
- instance, continuing will remove /var/lib/zope${zver}/instance/${instance}
- and reinstall the ${instance}. Existing logfiles in
+_Description: Action on old/incomplete zope instance '${instance}':
+ An old/incomplete ${instance} instance was found in
+ /var/lib/zope${zver}/instance/${instance}, with no Data.fs file.
+ This installation is either incomplete or incompletely removed.
+ .
+ Choosing 'abort' will allow you to inspect the state of the
+ instance.
+ .
+ Choosing 'remove and continue' will remove
/var/lib/zope${zver}/instance/${instance}
+ and reinstall ${instance}. Existing log files in
/var/log/zope${zver}/${instance} and configuration files in
- /etc/zope${zver}/${instance} are preserved.
+ /etc/zope${zver}/${instance} will be preserved.
Template: zope-common/keep-data-on-purge
Type: boolean
Default: true
_Description: Keep data for ${instance} on package purge?
- Purging the data files of a zope instance on package purge
- results in loss of all data of the zope instance. The data
- files for this instance are stored in
- /var/lib/zope${zver}/instance/${instance}.
+ Purging the data files of a Zope instance on package purge will
+ result in the loss of all data for that instance. These data files
+ are stored in /var/lib/zope${zver}/instance/${instance}.
Template: zope-common/admin-user
Type: string
Default: admin
-_Description: Admin user for zope instance '${instance}':
- Please enter an admin user for the zope instance '${instance}'.
- A valid user name starts with a letter, followed by letters and digits.
- .
- NOTE: Once the instance has been created, the parameter entered
- here isn't relevant anymore. To change the admin user (and password)
- later on, call:
+_Description: Administrative user for '${instance}' Zope instance:
+ Please enter the login name of the administrative user for the
+ '${instance}' Zope instance. Valid names must start with a letter and
+ only include letters and digits.
+ .
+ This will only be used for instance creation. Please use the
+ following command to change the administrative user login name and
+ password at a later time:
.
/var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user>
<password>
Template: zope-common/admin-password
Type: password
-_Description: Password for the admin user:
- Please enter a password for the admin user. The password must not be empty.
- The password is deleted from the configuration database, once the
- instance is sucessfully created and cannot be recoverd.
- .
- NOTE: Once the instance has been created, the parameter entered
- here isn't relevant anymore. To change the admin user (and password)
- later on, call:
+_Description: Password for the administrative user:
+ Please enter a password for the administrative user. The password
+ must not be empty. The password is deleted from the configuration
+ database once the instance is successfully created and cannot be
+ recovered.
+ .
+ This will only be used for instance creation. Please use the
+ following command to change the administrative user login name and
+ password at a later time:
.
/var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user>
<password>
Template: zope-common/admin-password-confirmation
Type: password
-_Description: Same password:
- Please enter again the password for the admin user.
- .
- NOTE: Once the instance has been created, the parameter entered
- here isn't relevant anymore. To change the admin user (and password)
- later on, call:
- .
- /var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user>
<password>
+_Description: Password confirmation:
+ Please confirm the administrative user's password.
Template: zope-common/instance-http-port
Type: string
_Description: HTTP port for this instance:
- Please enter the HTTP port for the instance ${instance}.
+ Please enter the HTTP port number for the ${instance} instance.
.
Other services (e.g. FTP, WebDAV, debug) will be disabled by default.
- You can enable them editing /etc/zope${zver}/${instance}/zope.conf.
+ They can be enabled by editing /etc/zope${zver}/${instance}/zope.conf.
Template: zope-common/instance-zeo-port
Type: string
_Description: TCP port for the ZEO instance:
- Please enter the TCP port for the ZEO instance ${instance}.
+ Please enter the TCP port number for the ${instance} ZEO instance.
Template: zope-common/admin-automatic-password
Type: note
-_Description: Automatically generated user and password for your instance
- You haven't provided a user and a password for your instance, so these
- values have been automatically generated.
+_Description: Automatically generated user and password for this instance
+ No administrative user login name or password were provided for
+ this instance. They have been automatically generated.
.
- Use these values to log in the Zope${zver} instance ${instance}:
+ For ${instance} Zope${zver} logins, use the following values:
.
- * User : ${user}
- * Password : ${password}
+ - User : ${user}
+ - Password : ${password}
--- zope-common.old/debian/control 2007-06-25 20:41:56.553019815 +0200
+++ zope-common/debian/control 2007-07-15 09:36:46.909790292 +0200
@@ -11,5 +11,5 @@
Package: zope-common
Architecture: all
Depends: adduser, python2.4, ${misc:Depends}
-Description: common settings and scripts for zope installations
- The package contains common settings and scripts for zope installations.
+Description: common settings and scripts for Zope installations
+ This package contains common settings and scripts for Zope installations.
