Your message dated Sun, 08 Oct 2006 05:17:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391215: fixed in mdadm 2.5.3.git200608202239-8
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
*** ../patch-update.txt
Hi,
Please find attached the French debconf templates translation update,
proofread by the debian-l10n-french mailing list contributors.
Regards
Jean-Luc
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-k8-2
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
#
# 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.
#
# Éric Madesclair <[EMAIL PROTECTED]>, 2005, 2006.
# Florentin Duneau <[EMAIL PROTECTED]>, 2006.
# Jean-Luc Coulon (f5ibh) <[EMAIL PROTECTED]>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: [EMAIL PROTECTED]"
"POT-Creation-Date: 2006-09-16 13:03+0200\n"
"PO-Revision-Date: 2006-09-30 17:56+0200\n"
"Last-Translator: Florentin Duneau <[EMAIL PROTECTED]>\n"
"Language-Team: French <[email protected]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "MD arrays needed for the root filesystem:"
msgstr "Ensembles MD requis par le système de fichiers racine :"
#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "${msg}"
msgstr "${msg}"
#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid ""
"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\"."
msgstr ""
"Veuillez indiquer une liste de périphériques, séparés par des espaces, "
"« all » ou « none ». Vous pouvez omettre « /dev/ » et simplement indiquer "
"par exemple, « md0 md1 » ou « md/1 md/d0 »."
#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid "for internal use - only the long description is needed."
msgstr "pour utilisation interne - seule la description longue est nécessaire"
#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"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 a "
"logical volume (LVM), which is on MD, all constituent arrays need to be "
"started."
msgstr ""
"Si le système de fichiers racine se trouve sur un ensemble MD (RAID), il "
"doit être lancé au début de la procédure de démarrage. Si le système de "
"fichiers racine se trouve sur un volume logique (« LVM »), qui se trouve "
"aussi sur un volume MD, tous les composants de l'ensemble doivent être "
"démarrés."
#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you know exactly which arrays are needed to bring up the root filesystem, "
"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 ""
"Si vous savez exactement quels sont les ensembles RAID nécessaires au "
"démarrage du système de fichiers racine et si vous souhaitez différer le "
"démarrage de tous les autres ensembles, veuillez les indiquer ici. Vous "
"pouvez aussi indiquer « all » pour démarrer tous les ensembles existants."
#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you do not need or want to start any arrays for the root filesystem, "
"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 ""
"Si vous n'avez pas besoin ou ne souhaitez pas démarrer d'ensemble RAID pour "
"le système de fichiers racine, veuillez laissez l'entrée vide (ou indiquez "
"« none »). Ceci peut être le cas si vous utilisez l'option autostart "
"démarrage ou si vous n'avez besoin d'aucun ensemble pour démarrer."
#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid "An error occurred: device node does not exist"
msgstr "Erreur : périphérique inconnu"
#. Type: text
#. Description
#: ../mdadm.templates:4001
msgid "An error occurred: not a block device"
msgstr "Erreur : ce n'est pas un périphérique en mode bloc"
#. Type: text
#. Description
#: ../mdadm.templates:5001
msgid "An error occurred: not an MD array"
msgstr "Erreur : ce n'est pas un ensemble RAID"
#. Type: text
#. Description
#: ../mdadm.templates:6001
msgid "An error occurred: array not listed in mdadm.conf file"
msgstr "Erreur : ensemble non mentionné dans le fichier mdadm.conf"
#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid "Proceed with starting arrays not listed in mdadm.conf?"
msgstr ""
"Faut-il continuer et démarrer les ensembles RAID non mentionnés dans "
"mdadm.conf ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"The array you have specified (${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 ""
"L'ensemble (${array}) que vous avez spécifié n'est pas mentionné dans le "
"fichier de configuration ${config}. Il ne sera donc pas démarré à moins que "
"vous corrigiez le fichier de configuration et que vous génériez de nouveau "
"le disque mémoire initial (« ramdisk »)."
#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend "
"to continue."
msgstr ""
"Veuillez consulter /usr/share/doc/mdadm/README.upgrading-2.5.3.gz si vous "
"souhaitez continuer."
#. Type: boolean
#. Description
#: ../mdadm.templates:7001
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 ""
"Cet avertissement n'a de signification que s'il est nécessaire que "
"l'ensemble RAID soit lancé à partir du disque mémoire initial afin de pouvoir "
"démarrer le système. Si vous utilisez le démarrage automatique par le noyau, "
"ou si vous n'avez pas besoin de lancer d'ensemble RAID en même temps que le "
"disque mémoire initial, vous pouvez simplement poursuivre. Vous pouvez aussi "
"choisir de ne pas poursuivre et entrer « none » lorsque vous sera demandé le "
"nom des ensembles RAID à démarrer à partir du disque mémoire initial."
#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid "Do you want to start MD arrays automatically?"
msgstr "Faut-il démarrer automatiquement les ensembles RAID ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"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."
msgstr ""
"Lorsque le système de base a démarré, mdadm peut démarrer tous les ensembles "
"(RAID) indiqués dans /etc/mdadm/mdadm.conf qui n'ont pas encore été démarrés. "
"Cela est recommandé, sauf si la gestion MD a été compilée dans le noyau et "
"que toutes les partitions faisant partie d'un ensemble RAID ont été marquées "
"avec le type 0xfd (car seul ce type de partition sera démarré automatiquement "
"par le noyau), ce qui est probablement ce que vous désirez."
#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Faut-il vérifier chque mois la redondance des ensembles RAID ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"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. 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 ""
"Si le noyau le gère (à partir de la version 2.6.14), mdadm peut vérifier "
"périodiquement la redondance des périphériques RAID. Cette action peut "
"demander beaucoup de ressources selon la configuration, mais cela aide à "
"prévenir les rares cas de pertes de données. Notez que ce test est réalisé "
"en lecture seule à moins que des erreurs ne soient rencontrées. Si des "
"erreurs sont détectées, mdadm essayera de les corriger, ce qui entraînera "
"des écritures sur le média."
#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"The default, if turned on, is to run the checks on the first Sunday of every "
"month at 01:06 o'clock."
msgstr ""
"Par défaut, la vérification s'effectuera tous les premiers dimanche du mois "
"à 01 h 06."
#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Faut-il démarrer le démon de surveillance MD ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid ""
"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."
msgstr ""
"Le démon de surveillance MD envoie des notifications par courriel lors "
"d'importants événements MD (comme une panne de disque dur). Il est "
"recommandé de l'activer."
#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid "Recipient for email notifications:"
msgstr "Destinataire des notifications par courriel :"
#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid ""
"Please enter the email address of the user who should get the email "
"notification for important MD events."
msgstr ""
"Veuillez indiquer l'adresse électronique de l'utilisateur qui doit recevoir "
"les notifications lors d'importants événements MD."
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.5.3.git200608202239-8
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.5.3.git200608202239-8_amd64.udeb
to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-8_amd64.udeb
mdadm_2.5.3.git200608202239-8.diff.gz
to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-8.diff.gz
mdadm_2.5.3.git200608202239-8.dsc
to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-8.dsc
mdadm_2.5.3.git200608202239-8_amd64.deb
to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-8_amd64.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: Fri, 6 Oct 2006 15:03:46 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 2.5.3.git200608202239-8
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]>
Changed-By: martin f. krafft <[EMAIL PROTECTED]>
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 390311 390955 391215
Changes:
mdadm (2.5.3.git200608202239-8) unstable; urgency=low
.
* This revision is dedicated to Peter Samuelson for his RAID10 expertise^W
educated guess^W^W pure luck. (:
* Now writes minimal mdadm.conf file even if the MD subsystem has not been
loaded and the scan for arrays thus failed.
* Now tries to ensure that the configuration file used for the initramfs
actually defines arrays.
* Now preserves MAILADDR from an existing mdadm.conf when generating a new
one.
* Documentation updates.
* Updated debconf translations:
- German by Mario JouÃen.
- Vietnamese by Clytie Siddall (closes: #390311).
- Dutch by Frans Pop (closes: #390955).
- French by Jean-Luc Coulon (closes: #391215).
Files:
d1ae297b0ece8951ecddaed8e40e22af 819 admin optional
mdadm_2.5.3.git200608202239-8.dsc
75c72bd3efd207830dc9cd03a3beeb1d 94204 admin optional
mdadm_2.5.3.git200608202239-8.diff.gz
06f391836915b1fdd9e227e35874e465 210720 admin optional
mdadm_2.5.3.git200608202239-8_amd64.deb
7496dd2a7c5a5fb2d7b4a2dc16c412b4 70900 debian-installer optional
mdadm-udeb_2.5.3.git200608202239-8_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFKOhdIgvIgzMMSnURAgGEAKDkVd/xFSiV589jqg3Py20/SFHslwCgt3Rk
k+ZL5uYY0Tmpbqdef0ZTIkc=
=R3UO
-----END PGP SIGNATURE-----
--- End Message ---
