Bug#463673: Announce of the upcoming NMU for the mdadm package

Tue Apr 22 06:01:20 UTC 2008

Dear maintainer of mdadm and Debian translators,

On Sunday, April 06, 2008 I sent a notice to the maintainer of the mdadm Debian
package, mentioning the status of at least one old po-debconf translation update in the BTS (bug #463673).

I announced the intent to build and possibly upload a non-maintainer upload
for this package in order to fix this long-time pending localization
bug as well as all other pending translations.

The package maintainer agreed for the NMU or did not respond in two
weeks, so I will proceed with the NMU.

The full planned schedule is available at the end of this mail.

The package is currently translated to: cs de es fi fr gl ja nl pt pt_BR ru sv vi

Among these, the following translations are incomplete: es pt_BR sv

If you did any of the, currently incomplete, translations you will get
ANOTHER mail with the translation to update.

Other translators also have the opportunity to create new translations
for this package. Once completed, please send them as a bug report
against the mdadm package so I can incorporate them in the build.

The deadline for receiving updates and new translations is Friday, May 02, 2008. If you
are not in time you can always send your translation to the BTS.

The POT file is attached to this mail.

If the maintainer objects to this process I will immediately abort my NMU
and send him/her all updates I receive.

Otherwise the following will happen (or already has):

 Sunday, April 06, 2008   : send the first intent to NMU notice to
                 the package maintainer.
 Tuesday, April 22, 2008       : send this notice
 Friday, May 02, 2008       : deadline for receiving translation updates
 Saturday, May 03, 2008       : build the package and upload it to DELAYED/0-day
                 send the NMU patch to the BTS
 Sunday, May 04, 2008       : NMU uploaded to incoming

Thanks for your efforts and time.

-- 

-- 

-------------- next part --------------
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: mdadm at packages.debian.org\n"
"POT-Creation-Date: 2008-02-06 18:49+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../mdadm.templates:2001
msgid "MD arrays needed for the root file system:"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:2001
msgid ""
"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)."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid "for internal use - only the long description is needed."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid ""
"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."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid ""
"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."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid ""
"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."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:4001
msgid "An error occurred: device node does not exist"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:5001
msgid "An error occurred: not a block device"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:6001
msgid "An error occurred: not an MD array"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:7001
msgid "An error occurred: array not listed in mdadm.conf file"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid "Start arrays not listed in mdadm.conf?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"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."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend "
"to continue."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"This warning is only relevant if you need arrays to be started from the "
"initial ramdisk to be able to boot. If you use kernel autostarting, or do "
"not need any arrays to be started as early as the initial ramdisk is loaded, "
"you can simply continue. Alternatively, choose not to continue and enter "
"'none' when prompted which arrays to start from the initial ramdisk."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid "Do you want to start MD arrays automatically?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"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)."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid ""
"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."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:11001
msgid "Do you want to start the MD monitoring daemon?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:11001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:11001
msgid "Enabling this option is recommended."
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:12001
msgid "Recipient for email notifications:"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:12001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
-------------- 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/20080422/c0e20520/attachment.pgp 