Bug#463673: mdadm: General update after the debconf review process

Christian Perrier bubulle at debian.org
Mon Feb 25 06:18:15 UTC 2008 

Dear Debian maintainer,

On Tuesday, December 18, 2007, I sent you a notification about the beginning of a review
action on debconf templates for mdadm.

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 Tuesday, December 18, 2007. 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.



-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.tar.gz
Type: application/octet-stream
Size: 47406 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20080225/60ed06a5/attachment-0001.obj 
-------------- next part --------------
--- mdadm.old/debian/mdadm.templates	2007-12-16 21:28:20.042026695 +0100
+++ mdadm/debian/mdadm.templates	2008-02-02 07:27:22.543486561 +0100
@@ -1,26 +1,36 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english at lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: mdadm/initrdstart
 Type: string
 Default: all
-_Description: MD arrays needed for the root filesystem:
+#flag:translate!:2
+_Description: MD arrays needed for the root file system:
  ${msg}
  .
- Please enter a space-separated list of devices, 'all', or 'none'. You may
- omit the leading '/dev/' and just enter e.g. "md0 md1", or "md/1 md/d0".
+ Please enter 'all', 'none', or a space-separated list of devices such as
+ 'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted).
 
 Template: mdadm/initrdstart_msg_intro
 Type: text
 _Description: for internal use - only the long description is needed.
- If your system has its root filesystem on an MD array (RAID), it needs to be
- started early during the boot sequence. If your root filesystem is on
+ If the system's root file system is located on an MD array (RAID), it needs to be
+ started early during the boot sequence. If it is located on
  a logical volume (LVM), which is on MD, all constituent arrays need to be
  started.
  .
- If you know exactly which arrays are needed to bring up the root filesystem,
+ If you know exactly which arrays are needed to bring up the root file system,
  and you want to postpone starting all other arrays to a later point in the
  boot sequence, enter the arrays to start here. Alternatively, enter 'all' to
  simply start all available arrays.
  .
- If you do not need or want to start any arrays for the root filesystem, leave
+ If you do not need or want to start any arrays for the root file system, leave
  the answer blank (or enter 'none'). This may be the case if you are using
  kernel autostart or do not need any arrays to boot.
 
@@ -47,9 +57,9 @@
 Template: mdadm/initrdstart_notinconf
 Type: boolean
 Default: false
-_Description: Proceed with starting arrays not listed in mdadm.conf?
- The array you have specified (${array}) is not listed in the configuration
- file ${config}. Therefore it cannot be started during boot, unless you
+_Description: Start arrays not listed in mdadm.conf?
+ The specified array (${array}) is not listed in the configuration
+ file (${config}). Therefore, it cannot be started during boot, unless you
  correct the configuration file and recreate the initial ramdisk.
  .
  Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend
@@ -65,36 +75,39 @@
 Type: boolean
 Default: true
 _Description: Do you want to start MD arrays automatically?
- Once the base system has come up, mdadm can start all MD arrays (RAIDs)
- specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless
- you have compiled multiple device (MD) support into the kernel and marked all
- partitions part of MD arrays with type 0xfd (as those and only those will be
- started automatically by the kernel), this is probably what you want.
+ Once the base system has booted, mdadm can start all MD arrays
+ (RAIDs) specified in /etc/mdadm/mdadm.conf which have not yet been
+ started. This is recommended unless multiple device (MD) support is
+ compiled into the kernel and all partitions are marked as belonging
+ to MD arrays, with type 0xfd (as those and only those will be started
+ automatically by the kernel).
 
 Template: mdadm/autocheck
 Type: boolean
 Default: true
 _Description: Should mdadm run monthly redundancy checks of the MD arrays?
- If your kernel supports it (>> 2.6.14), mdadm can periodically check the
- redundancy of your MD arrays (RAIDs). This may be a resource-intensive process,
- depending on your setup, but it could help prevent rare cases of data loss.
+ If the kernel supports it (versions greater than 2.6.14), mdadm can periodically check the
+ redundancy of MD arrays (RAIDs). This may be a resource-intensive process,
+ depending on the local setup, but it could help prevent rare cases of data loss.
  Note that this is a read-only check unless errors are found; if errors are
  found, mdadm will try to correct them, which may result in write access to
  the media.
  .
- The default, if turned on, is to run the checks on the first Sunday of every
- month at 01:06 o'clock.
+ The default, if turned on, is to check on the first Sunday of every
+ month at 01:06.
 
 Template: mdadm/start_daemon
 Type: boolean
 Default: true
 _Description: Do you want to start the MD monitoring daemon?
  The MD (RAID) monitor daemon sends email notifications in response to
- important MD events (such as a disk failure). You probably want to enable it.
+ important MD events (such as a disk failure).
+ .
+ Enabling this option is recommended.
 
 Template: mdadm/mail_to
 Type: string
 Default: root
 _Description: Recipient for email notifications:
  Please enter the email address of the user who should get the email
- notification for important MD events.
+ notifications for important MD events.
--- mdadm.old/debian/control	2007-12-16 21:28:20.042026695 +0100
+++ mdadm/debian/control	2008-01-26 17:52:12.132823195 +0100
@@ -15,11 +15,11 @@
 Replaces: mdctl
 Conflicts: mdctl (<< 0.7.2), raidtools2 (<< 1.00.3-12.1), initramfs-tools (<< 0.65)
 Description: tool to administer Linux MD arrays (software RAID)
- mdadm is a program that can be used to create, manage, and monitor MD
- arrays (e.g. software RAID, multipath devices).
+ The mdadm utility can be used to create, manage, and monitor MD
+ (multi-disk) arrays for software RAID or multipath I/O.
  .
  This package automatically configures mdadm to assemble arrays during the
- system startup process. If not needed, this functionally can be disabled.
+ system startup process. If not needed, this functionality can be disabled.
 
 Package: mdadm-udeb
 Section: debian-installer
@@ -27,7 +27,7 @@
 Architecture: any
 Depends: ${shlibs:Depends}
 Description: tool to administer Linux MD arrays (software RAID)
- mdadm is a program that can be used to create, manage, and monitor MD
- arrays (e.g. software RAID, multipath devices).
+ The mdadm utility can be used to create, manage, and monitor MD
+ (multi-disk) arrays for software RAID or multipath I/O.
  .
- mdadm-udeb is a minimal package used by the debian-installer.
+ This is a minimal package used by the debian-installer.
--- mdadm.old/debian/changelog	2007-12-16 21:28:20.042026695 +0100
+++ mdadm/debian/changelog	2008-02-23 09:18:48.381122933 +0100
@@ -1,3 +1,20 @@
+mdadm (2.6.3+200709292116+4450e59-4) UNRELEASED; urgency=low
+
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+    english team as part of the Smith review project. Closes: #463673
+  * [Debconf translation updates]
+  * Japanese. Closes: #464438
+  * Galician. Closes: #464454
+  * French. Closes: #465984
+  * Czech. Closes: #466306
+  * Dutch. Closes: #466543
+  * Russian. Closes: #466577
+  * Portuguese. Closes: #466794
+  * German. Closes: #466989
+  * Vietnamese. Closes: #467118
+
+ -- Christian Perrier <bubulle at debian.org>  Sat, 23 Feb 2008 09:18:48 +0100
+
 mdadm (2.6.3+200709292116+4450e59-3) unstable; urgency=low
 
   * Patch by J?r?my Bobbio which completes the fix for #444682.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20080225/60ed06a5/attachment-0001.pgp

More information about the pkg-mdadm-devel mailing list