Bug#463673: mdadm: [debconf_rewrite] Debconf templates and debian/control review

Christian Perrier bubulle at debian.org
Sat Feb 2 06:27:24 UTC 2008 

Package: mdadm
Version: N/A
Severity: normal
Tags: patch

Dear Debian maintainer,

On Tuesday, December 18, 2007, I notified you of the beginning of a review process
concerning debconf templates for mdadm.

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 mdadm with these changes right now.

The second phase of this process will begin on Tuesday, February 05, 2008, 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 Tuesday, February 26, 2008. 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 Wednesday, February 27, 2008, 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')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-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
-------------- 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.

More information about the pkg-mdadm-devel mailing list