Dear Debian maintainer, On Wednesday, August 13, 2014, I sent you a notification about the beginning of a review action on debconf templates for lava-server.
Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please consider using it EVEN if you committed files to your development tree as long as they were reported. The attached tarball contains: - debian/changelog with the list of changes - debian/control with rewrites of packages' descriptions - debian/<templates> with all the rewritten templates file(s) - debian/po/*.po with all PO files (existing ones and new ones) As said, please use *at least* the PO files as provided here, preferrably over those sent by translators in their bug reports. All of them have been checked and reformatted. In some cases, formatting errors have been corrected. The patch.rfr file contains a patch for the templates and control file(s) alone. Please note that this patch applies to the templates and control file(s) of your package as of Wednesday, August 13, 2014. If your package was updated in the meantime, I may have updated my reference copy....but I also may have missed that. This is indeed why I suggested you do not modified such files while the review process was running, remember..:-) It is now safe to upload a new package version with these changes. Please notify me of your intents with regards to this. There is of course no hurry to update your package but feel free to contact me in case you would need sponsoring or any other action to fix this. --
patch.tar.gz
Description: application/gzip
--- lava-server.old/debian/lava-server.templates 2014-07-08
07:12:14.599754286 +0200
+++ lava-server/debian/lava-server.templates 2014-07-30 18:26:34.906492672
+0200
@@ -1,26 +1,37 @@
+# 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: lava-server/master
Type: boolean
Default: true
-_Description: Is this a single master instance of LAVA?
- LAVA can be set up in one of two ways, as a single instance
- with attached devices or as a master instance and remote
- dispatchers providing (more) devices.
+_Description: Is this a standalone master instance of LAVA?
+ LAVA can be set up in either of two ways: as a single standalone
+ master instance with attached devices, or in a distributed
+ configuration with a central master instance and remote dispatchers
+ providing (more) devices.
.
- Configuration of remote dispatchers is currently experimental
- and a single master instance is recommended.
+ Configuration of remote dispatchers requires manual intervention,
+ so the standalone configuration is recommended.
Template: lava-server/db-port
Type: string
Default: 5432
-_Description: Port number of the postgresql database:
- Please enter the port number for the postgresql database.
+_Description: Port number of the PostgreSQL database:
+ Please enter the port number for the PostgreSQL database.
Template: lava-server/worker-note
Type: note
_Description: This install looks like a remote worker
- You have asked for a master instance install but the current install
- looks like a remote worker install. Select back to change this or
- confirm to proceed and change to a master instance.
+ You asked for this system to be set up as master instance for a
+ distributed configuration, but this system looks like a remote worker.
+ You can either go back and change your answer or proceed with
+ reconfiguring this system as specified.
.
Note that you will have to ensure that the lava-coordinator
configuration is correct.
@@ -28,9 +39,10 @@
Template: lava-server/master-note
Type: note
_Description: This install looks like a master instance
- You have asked for a remote worker install but the current install
- looks like a master instance. Select back to change this or
- confirm to proceed and change to a remote worker.
+ You asked for this system to be set up as a remote worker for a
+ distributed configuration, but this system looks like a master
+ instance. You can either go back and change your answer or proceed
+ with reconfiguring this system as specified.
.
Note that you will have to ensure that the lava-coordinator
configuration is changed to point to the master instance for
@@ -41,17 +53,17 @@
Type: string
Default: default
_Description: Name for this LAVA instance:
- LAVA servers typically have an instance name. If this is a new
+ LAVA servers need to have an instance name. If this is a new
instance, you can safely use the default name. If this is an upgrade
of a previous LAVA instance, specify the instance name here to
upgrade the database or use a different name to start fresh with
a new database.
Template: lava-server/missingname
-Type: note
+Type: error
_Description: Missing LAVA instance name
An instance name must be specified for LAVA-server. Using
- the instance name 'default'.
+ the instance name "default".
Template: lava-worker/master-instance-name
Type: string
@@ -59,20 +71,20 @@
_Description: Name of the master instance for this worker:
LAVA servers need to have an instance name. Each remote
worker must be given the instance name of the master
- lava-server which it will poll for new jobs to run
+ LAVA server which it will poll for new jobs to run
on the devices attached to the worker.
Template: lava-worker/db-server
Type: string
-_Description: Name of the master scheduler for this worker:
+_Description: Master scheduler for this worker:
Each remote worker needs to connect to a master scheduler
running lava-server. This hostname or IP address will be
used to connect to the master database.
.
- To work with remote nodes, the Master needs to be configured
+ To work with remote nodes, the master needs to be configured
to allow the database to listen to the workers. An SSH key also
needs to be generated on the worker and added to the master list
- of authorized_keys. Ensure that the Master allows remote access
+ of authorized_keys. Ensure that the master allows remote access
from workers before submitting jobs or health checks.
.
You can continue setting up the worker, as long as
@@ -104,16 +116,5 @@
Type: string
_Description: Password for the database on the master:
Please enter the password for the database on the master scheduler
- running lava-server. The worker will use this username to contact
+ running lava-server. The worker will use this password to contact
the database.
-
-Template: lava-server/missingname
-Type: note
-_Description: Missing LAVA instance name
- An instance name must be specified for LAVA-server. Using
- the instance name 'default'.
-
-Template: lava-server/missingip
-Type: note
-_Description: Missing server IP address
- The IP address of the master scheduler must be specified.
--- lava-server.old/debian/control 2014-07-08 07:12:14.599754286 +0200
+++ lava-server/debian/control 2014-07-24 18:58:39.388321574 +0200
@@ -33,7 +33,7 @@
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
Tests can be simple boot testing, bootloader testing and system
- level testing, although extra hardware may be required for some
+ level testing. Extra hardware may be required for some
system tests. Results are tracked over time and data can be
exported for further analysis.
.
@@ -43,16 +43,17 @@
and dispatcher.
.
This package can be configured as the master scheduler or as a
- remote worker, although limitations in the remote worker design
- mean that an unused database will need to be installed.
+ remote worker, although design limitations mean that it always
+ installs a database (unused on a remote worker).
Package: lava
Architecture: all
Section: metapackages
Depends: lava-server, lava-server-doc, lava-dispatcher, lava-coordinator,
lava-dev, lava-tool, lavapdu-client, linaro-image-tools, ntp | ntpdate,
- tftpd-hpa, vmdebootstrap, ${misc:Depends}
+ tftpd-hpa, ${misc:Depends}
Recommends: lavapdu-daemon
+Suggests: vmdebootstrap, android-tools-adb, android-tools-fastboot
Description: Linaro Automated Validation Architecture metapackage
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
@@ -61,20 +62,22 @@
system tests. Results are tracked over time and data can be
exported for further analysis.
.
- Metapackage to bring in all LAVA components on a single
- machine. Some dependencies require the Linaro Tools PPA.
+ This metapackage brings in all LAVA components on a single
+ machine. Some suggested packages may not be available for all
+ architectures.
Package: lava-dev
Architecture: all
Section: devel
-Depends: ca-certificates, devscripts, dpkg-dev, debhelper (>= 8.0.0),
- fakeroot, git, libdistro-info-perl, django-testscenarios,
+Depends: build-essential, ca-certificates, devscripts, dpkg-dev,
+ debhelper (>= 8.0.0), fakeroot, git, libdistro-info-perl,
+ django-testscenarios,
python | python-all | python-dev | python-all-dev,
python-sphinx (>= 1.0.7+dfsg) | python3-sphinx, po-debconf,
python-mocker, python-setuptools, python-versiontools,
${misc:Depends}
Recommends: sbuild
-Description: Developer support for LAVA
+Description: Linaro Automated Validation Architecture developer support
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
.
@@ -89,7 +92,7 @@
Conflicts: linaro-dashboard-bundle-doc
Provides: linaro-dashboard-bundle-doc
Replaces: linaro-dashboard-bundle-doc
-Description: documentation for lava-server
+Description: Linaro Automated Validation Architecture documentation
LAVA is a continuous integration system for deploying operating
systems onto physical and virtual hardware for running tests.
Tests can be simple boot testing, bootloader testing and system
@@ -98,7 +101,8 @@
exported for further analysis.
.
This package contains an offline copy of the LAVA
- Manual available on each instance running LAVA server.
+ Manual which is also available on each instance running LAVA
+ server.
.
- an overview of LAVA
- help on installing and configuring LAVA
--- lava-server.old/debian/changelog 2014-07-08 07:12:14.599754286 +0200
+++ lava-server/debian/changelog 2014-08-12 09:10:41.469401665 +0200
@@ -1,3 +1,18 @@
+lava-server (2014.06.02.17-2) UNRELEASED; urgency=low
+
+ * Debconf templates and debian/control reviewed by the debian-l10n-
+ english team as part of the Smith review project. Closes: #754149
+ * [Debconf translation updates]
+ * Russian (Yuri Kozlov). Closes: #756644
+ * Portuguese (Américo Monteiro). Closes: #753907
+ * German (Chris Leick). Closes: #757519
+ * Danish (Joe Hansen). Closes: #757651
+ * French (Julien Patriarca). Closes: #757709
+ * Brazilian Portuguese (Adriano Rafael Gomes). Closes: #757728
+ * Spanish; (Matías A. Bellone). Closes: #757894
+
+ -- Christian Perrier <bubu...@debian.org> Tue, 08 Jul 2014 07:16:28 +0200
+
lava-server (2014.06.02.17-1) unstable; urgency=medium
* New upstream production release
signature.asc
Description: Digital signature
