Your message dated Wed, 31 May 2006 16:32:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323988: fixed in mdadm 2.4.1-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mdadm
Version: N/A
Severity: wishlist
Tags: patch l10n
Hello,
Please find the attached fr.po file, which is an update of the french
translation of the debconf templates. This file has been reviewed by
the contributors of the debian-l10n-french mailing-list.
Could you put this file to the debian/po/ directory of this package,
in remplacement of the old fr.po file ?
Thanks.
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2005-07-24 17:52+0200\n"
"PO-Revision-Date: 2005-08-13 12:30+0200\n"
"Last-Translator: Eric Madesclair<[EMAIL PROTECTED]>\n"
"Language-Team: French <[email protected]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: note
#. Description
#: ../mdadm.templates:3
msgid "Initialise the superblock if you reuse hard disks"
msgstr "Si vous réutilisez des disques durs, initialisez leur superbloc."
#. Type: note
#. Description
#: ../mdadm.templates:3
msgid ""
"WARNING! If you are using hard disks which have a md superblock from an "
"earlier installation in a different RAID array, you MUST zero the superblock "
"before activating the autostart feature."
msgstr ""
"ATTENTION : Si vous utilisez des disques durs dont le superbloc a déjà été "
"écrit par md lors d'une installation dans une autre matrice RAID, vous DEVEZ "
"effacer leur superbloc avant d'activer le démarrage automatique."
#. Type: note
#. Description
#: ../mdadm.templates:3
msgid ""
"To do this, do not start the RAID devices automatically. First, zero the "
"superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-reconfigure "
"mdadm` to reactivate the autostart feature."
msgstr ""
"Pour faire cela, vous ne devez pas démarrer automatiquement les "
"périphériques RAID. Commencez par effacer le superbloc (mdadm --zero-"
"superblock /dev/xxx) puis activez le démarrage automatique en utilisant "
"« dpkg-reconfigure mdadm »."
#. Type: boolean
#. Description
#: ../mdadm.templates:15
msgid "Do you want to start the RAID devices automatically?"
msgstr "Voulez-vous démarrer automatiquement les périphériques RAID ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:15
msgid ""
"If RAID devices are started automatically, all RAID devices are discovered "
"and assembled automatically at system startup. This option should only be "
"used if the md driver is compiled as a module. If it is compiled into your "
"kernel, the automatic startup will be performed at boot time by the kernel "
"and therefore you should not choose this option."
msgstr ""
"Si les périphériques RAID sont démarrés automatiquement, ceux-ci peuvent "
"être recherchés et réunis automatiquement au démarrage du système. Cela "
"n'est possible que si vous utilisez le pilote md en module. S'il est compilé "
"dans le noyau, celui-ci démarre les périphériques automatiquement et vous "
"n'avez donc pas besoin de sélectionner cette option."
#. Type: boolean
#. Description
#: ../mdadm.templates:25
msgid "Do you want to start the RAID monitor daemon?"
msgstr "Voulez-vous démarrer le démon de surveillance RAID ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:25
msgid ""
"When the RAID monitor daemon runs, email notifications are sent when a disk "
"belonging to a RAID array fails or changes its status for some reason."
msgstr ""
"Quand le démon de surveillance des périphériques RAID est utilisé, une "
"notification par courriel est envoyée en cas de défaillance ou de changement "
"d'état d'un disque appartenant à un ensemble RAID."
#. Type: string
#. Description
#: ../mdadm.templates:32
msgid "Recipient for daemon email notifications:"
msgstr "Destinataire des notifications par courriel :"
#. Type: string
#. Description
#: ../mdadm.templates:32
msgid ""
"Please enter the email address of the user who should get the email "
"notification if the status of a RAID array changes."
msgstr ""
"Veuillez indiquer l'adresse électronique de l'utilisateur qui doit recevoir "
"les notifications si l'état des périphériques RAID change."
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.4.1-2
We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive:
mdadm-udeb_2.4.1-2_i386.udeb
to pool/main/m/mdadm/mdadm-udeb_2.4.1-2_i386.udeb
mdadm_2.4.1-2.diff.gz
to pool/main/m/mdadm/mdadm_2.4.1-2.diff.gz
mdadm_2.4.1-2.dsc
to pool/main/m/mdadm/mdadm_2.4.1-2.dsc
mdadm_2.4.1-2_i386.deb
to pool/main/m/mdadm/mdadm_2.4.1-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <[EMAIL PROTECTED]> (supplier of updated mdadm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 31 May 2006 23:07:48 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian/Ubuntu mdadm maintainers <[EMAIL PROTECTED]>
Changed-By: martin f. krafft <[EMAIL PROTECTED]>
Description:
mdadm - tool to administer Linux MD device arrays (software RAID)
mdadm-udeb - tool to administer Linux MD device arrays (software RAID) (udeb)
Closes: 271033 299623 310247 318230 321751 323950 323988 333486 337903 344714
345667 345669 352798 356153 360290 361116 363592
Changes:
mdadm (2.4.1-2) unstable; urgency=low
.
* The "this took way longer than I thought" release.
* Migrating to unstable.
* If the init.d script creates the mdadm.conf file, it should remove it on
purge. To accomplish this, I create a semaphore in /var/lib/mdadm if it
was generated, and only remove the conffile on purge if the semaphore
exists.
* Added a little helper /usr/share/mdadm/mkconf to aid generation of
configuration file.
* Added a bug script to collect some important information when the user
uses Debian bug reporting tools (such as reportbug).
* Added a debian/watch file.
.
mdadm (2.4.1-1) experimental; urgency=low
.
* The "I'll kill that maintainer... uh, wait, it's me" release. Sorry for
the delay, here's the long awaited new upstream release,
which closes: Bug#318230, Bug#321751, Bug#337903, Bug#352798, Bug#363592,
Bug#356153, Bug#271033
Oh, and we're moving away from that arch nightmare too. Sorry for the
confusion.
* Experimental release, because I really don't want to be responsible for
data loss. Though I am quite sure that the upgrade is painless, I also
don't have access to 18 drive RAID 10 with multipath on s390 or similar
arrangements.
* We now make the /dev/md* devices in postinst unless /dev/md15 exists (no
longer checking for /dev/md0), or unless devfs is in use. If udev is used,
/dev/md15 will only exist in complex setups, so the devices will be made
in /dev/.static by MAKEDEV, which is not really a concern. I opted against
unconditionally calling MAKEDEV until #367407 is fixed so as to preserve
custom permissions or owner settings. This also acknowledges the NMU
(#299623).
closes: Bug#310247, Bug#299623
* Patched some of the code to make mdadm honour /etc/mdadm/mdadm.conf over
/etc/mdadm.conf (see NEWS).
* Fixed a couple of typos in the mdadm(8) manpage; thanks to Reuben Thomas.
closes: Bug#345669, Bug#345667
* Pushed Standards-Version to 3.7.2; no changes required.
* Updated Debconf translations:
- Vietnamese by Clytie Siddall (closes: Bug#323950)
- Czech by Miroslav Kure (closes: Bug#360290)
- Russian by Yuri Kozlov (closes: Bug#361116)
- French by Eric Madesclair (closes: Bug#323988)
* Added new Debconf translations:
- Swedish by Daniel Nylander (closes: Bug#333486)
- Dutch by Frans Pop (closes: Bug#344714)
Files:
903361e3e085c58ee8b47f25412a52ca 719 admin optional mdadm_2.4.1-2.dsc
62f7d6779cf7f4b3b85915999e0d0e1a 41979 admin optional mdadm_2.4.1-2.diff.gz
c11656ab6878c901f21ad5a0de43e6c6 148264 admin optional mdadm_2.4.1-2_i386.deb
3618c53f064f245931a77c2619a1698d 70378 debian-installer optional
mdadm-udeb_2.4.1-2_i386.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEfiGvIgvIgzMMSnURAql9AKCO7ya0N3DEvL+3sXWWQJ/nII/okgCeKJ0w
xW/CHA1Ckx7JdKnfO57RSfw=
=uz8i
-----END PGP SIGNATURE-----
--- End Message ---
