Dear Debian maintainer,

On Sunday, February 22, 2009, I sent you a notification about the beginning of 
a review
action on debconf templates for adjtimex.

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 Sunday, February 22, 2009. 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.



-- 


Attachment: patch.tar.gz
Description: Binary data

--- adjtimex.old/debian/templates       2009-02-17 19:47:33.908972952 +0100
+++ adjtimex/debian/templates   2009-03-12 07:51:41.408251976 +0100
@@ -1,22 +1,35 @@
+# 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: adjtimex/run_daemon
 Type: boolean
 Default: true
 _Description: Should adjtimex be run at installation and at every startup?
- adjtimex can run at system startup to set the kernel time parameters to
- the values in /etc/default/adjtimex. Don't accept if you just want to
+ Running adjtimex at system startup will set the kernel time parameters to
+ the values in /etc/default/adjtimex.
+ .
+ You should not choose this option if you just want to
  use adjtimex to inspect the current parameters.
 
 Template: adjtimex/compare_rtc
 Type: boolean
 Default: true
-_Description: Should adjtimexconfig be run when adjtimex is installed or 
upgraded?
+#flag:comment:2
+# Translators: do not translate "tick" and "frequency"
+_Description: Run adjtimexconfig when adjtimex is installed or upgraded?
  The adjtimexconfig script will use adjtimex to find values for the kernel
- variables tick and frequency that will make the system clock approximately
+ variables "tick" and "frequency" that will make the system clock approximately
  agree with the hardware clock (also known as the CMOS clock).  It then
  saves these values in the configuration file /etc/default/adjtimex so the
  settings will be restored on every boot, when /etc/init.d/adjtimex runs.
  .
- The script takes 70 sec to run. Alternatively, you can run adjtimexconfig
- yourself at a later time, or determine the kernel variables one of several
- other ways (see the adjtimex man page) and install them in
- /etc/default/adjtimex.
+ The script takes 70 seconds to run, so running it for every upgrade
+ may be a waste of time. Alternatively, you can run adjtimexconfig
+ manually when needed, or determine the kernel variables by using other
+ methods and set them manually in /etc/default/adjtimex.
--- adjtimex.old/debian/control 2009-02-17 19:47:33.908972952 +0100
+++ adjtimex/debian/control     2009-03-12 07:51:43.516243074 +0100
@@ -9,12 +9,12 @@
 Architecture: any
 Depends: ${shlibs:Depends}, debconf | debconf-2.0
 Suggests: ntpdate
-Description: Utility to display or set the kernel time variables
- This program gives you raw access to the kernel time variables.  For
+Description: kernel time variables configuration utility
+ This package provides a utility to manipulate the kernel time variables.  For
  a machine connected to the Internet, or equipped with a precision
  oscillator or radio clock, the best way to keep the system clock
- correct is with ntpd.  However, for a standalone or intermittently
+ accurate is using NTP (Network Time Protocol).  However, for a standalone or 
intermittently
  connected machine, you may use adjtimex instead to at least correct
- for systematic drift.  adjtimex can optionally adjust the system
+ for systematic drift.  It can optionally adjust the system
  clock using the CMOS clock as a reference, and can log times for
  long-term estimation of drift rates.
--- adjtimex.old/debian/changelog       2009-02-17 19:47:33.908972952 +0100
+++ adjtimex/debian/changelog   2009-04-17 07:19:24.885744693 +0200
@@ -1,3 +1,23 @@
+adjtimex (1.26-3) UNRELEASED; urgency=low
+
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+    english team as part of the Smith review project. Closes: #519431
+  * [Debconf translation updates]
+  * French. Closes: #520986
+  * Japanese. Closes: #522188
+  * Czech. Closes: #522193
+  * Swedish. Closes: #522979
+  * Basque. Closes: #523079
+  * Italian. Closes: #523419
+  * Spanish. Closes: #523915
+  * Russian. Closes: #524069
+  * German. Closes: #524224
+  * Portuguese. Closes: #524283
+  * Danish. Closes: #524368
+  * Galician. Closes: #524397
+
+ -- Christian Perrier <[email protected]>  Fri, 13 Mar 2009 06:37:16 +0100
+
 adjtimex (1.26-2) unstable; urgency=low
 
   * debian/templates: Clarify wording: ask about running "when installed

Attachment: signature.asc
Description: Digital signature

Reply via email to