[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#956350: marked as done (mdadm: [INTL:de] updated German debconf translation)



Your message dated Sun, 13 Sep 2020 04:18:28 +0000
with message-id <E1kHJTA-000HDk-J7@fasolo.debian.org>
and subject line Bug#956350: fixed in mdadm 4.1-6
has caused the Debian Bug report #956350,
regarding mdadm: [INTL:de] updated German debconf translation
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
956350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956350
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 4.1-5
Severity: wishlist
Tags: patch l10n

Please find the updated German debconf translation for mdadm
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics <pofile.po>'
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
            Helge
# 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.
#
# (C) Mario Joussen <joussen@debian.org>, 2009.
# (C) Helge Kreutzmann <debian@helgefjell.de>, 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 4.1.5\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-04-10 09:40+0200\n"
"Last-Translator: Mario Joussen <joussen@debian.org>\n"
"Language-Team: German <debian-l10n-german@lists.debian.org>\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
"Soll Mdadm monatlich die Redundanz��auf den RAID-Verb�"
"ausf�"

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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 ""
"Falls Ihr Kernel es unterst�Versionen gr� als 2.6.14) kann Mdadm "
"regelm�g die Redundanz Ihrer MD-Verb�RAID) ��Dies kann "
"abh�ig von Ihrer Installation ein ressourcenintensiver Vorgang sein, der "
"aber helfen kann, seltene F�e von Datenverlust zu vermeiden. Bitte "
"beachten Sie, dass diese �erpr�nur lesend erfolgt, solange keine "
"Fehler gefunden werden. Falls Fehler gefunden werden, wird Mdadm versuchen, "
"diese zu beheben, was zu schreibendem Zugriff auf das Medium f�kann."

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Die Voreinstellung ist, falls eingeschaltet, die �erpr�am ersten "
"Sonntag jedes Monats um 01:06 Uhr durchzuf�"

#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Soll Mdadm einmal t�ich auf degradierte Verb�r�

#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"Mdadm kann einmal t�ich auf degradierte Verb�nd fehlende "
"Ausweichmedien pr�um sicherzustellen, dass diese Ereignisse bemerkt "
"werden."

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "M�en Sie den RAID-�erwachungsd�n starten?"

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Der MD- (RAID-)�erwachungsd�n verschickt Benachrichtigungen als Reaktion "
"auf wichtige RAID-Ereignisse (wie zum Beispiel Festplattenfehler)."

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Das Aktivieren dieser Option ist empfohlen."

#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Empf�er der E-Mail-Benachrichtungen:"

#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Geben Sie bitte die E-Mail-Adresse des Benutzers an, der die E-Mail-"
"Benachrichtigung f�htigen MD-Ereignisse erhalten soll."

#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "F� Wurzeldateisystem ben�te MD folgende Verb�

#~ 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 ""
#~ "Bitte geben Sie �all�, �none� oder eine leerzeichenseparierte Ger�liste "
#~ "wie zum Beispiel �md0 md1� oder �md/1 md/d0� ein (das f�e �/dev� "
#~ "kann weggelassen werden)."

#~ msgid "for internal use - only the long description is needed."
#~ msgstr ""
#~ "f�ernen Gebrauch - es wird nur die ausf�he Beschreibung "
#~ "ben�t."

#~ 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 ""
#~ "Wenn das Wurzeldateisystem Ihres Systems auf einem MD-Verbund (RAID) "
#~ "liegt, muss es fr�ig w�end des Bootvorgangs gestartet werden. Wenn "
#~ "sich Ihr Wurzeldateisystem auf einem logischen Laufwerk (LVM) befindet, "
#~ "das sich wiederum auf einem MD Verbund befindet, m�alle zugeh�en "
#~ "Verb�estartet werden."

#~ 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 ""
#~ "Wenn Sie genau wissen, welche Verb�en�t werden, um das "
#~ "Wurzeldateisystem zu starten, und Sie den Start der anderen Verb�uf "
#~ "einen sp�ren Zeitpunkt in der Bootreihenfolge verschieben wollen, geben "
#~ "Sie die zu startenden Verb�ier ein. Alternativ geben Sie �all� ein, "
#~ "um alle verf�n Verb�u starten."

#~ 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 ""
#~ "Falls Sie keine RAID-Verb�� Wurzeldateisystem ben�en oder "
#~ "starten wollen, lassen Sie die Antwort leer (oder geben �none� ein). Dies "
#~ "k�e der Fall sein, wenn Sie entweder die Autostartfunktion des Kernels "
#~ "verwenden oder keine Verb�um Booten ben�en."

#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Ein Fehler ist aufgetreten: Ger�knoten existiert nicht"

#~ msgid "An error occurred: not a block device"
#~ msgstr "Ein Fehler ist aufgetreten: kein Blockger�

#~ msgid "An error occurred: not an MD array"
#~ msgstr "Ein Fehler ist aufgetreten: kein RAID-Verbund"

#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr ""
#~ "Ein Fehler ist aufgetreten: Verbund nicht in der Datei mdadm.conf "
#~ "aufgef�
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Nicht in mdadm.conf aufgef�Verb�tarten?"

#~ 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 ""
#~ "Der angegebene Verbund (${array}) ist in der Konfigurationsdatei "
#~ "${config} nicht aufgef�Deshalb kann er w�end des Bootvorgangs "
#~ "nicht gestartet werden, es sei denn, Sie korrigieren die "
#~ "Konfigurationsdatei und erzeugen die initiale Ramdisk neu."

#~ 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 ""
#~ "Diese Warnung ist nur von Bedeutung, wenn Sie RAID-Verb�die von der "
#~ "initialen Ramdisk gestartet werden, ben�en, um booten zu k�n. Falls "
#~ "Sie die Autostartfunktion des Kernels verwenden oder kein RAID-Verbund "
#~ "zum fr�eitpunkt des Ladens der initialen Ramdisk gestartet werden "
#~ "muss, k�n Sie einfach fortfahren. Alternativ w�en Sie, nicht "
#~ "fortzufahren und geben �none� ein, wenn Sie gefragt werden, welche RAID-"
#~ "Verb�on der initialen Ramdisk gestartet werden sollen."

#~ msgid "Initialise the superblock if you reuse hard disks"
#~ msgstr ""
#~ "Initialisieren Sie den Superblock, wenn Sie Festplatten wieder verwenden."

#~ msgid ""
#~ "WARNING! If you are using hard disks which have RAID superblocks from "
#~ "earlier installations in different RAID arrays, you MUST zero each "
#~ "superblock *before* activating the autostart feature."
#~ msgstr ""
#~ "WARNUNG! Wenn Sie Festplatten verwenden, die bereits einen md-Superblock "
#~ "von einer vorherigen Installation in einem anderen RAID-Verbund besitzen, "
#~ "so M�SEN Sie diesen l�en, *bevor* Sie die Autostart-Funktion "
#~ "aktivieren."

#~ 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 ""
#~ "Dazu starten Sie die RAID-Laufwerke nicht automatisch und l�en dann "
#~ "erst den Superblock (mdadm --zero-superblock /dev/mdX). Danach k�n Sie "
#~ "mit �dpkg-reconfigure mdadm� die Autostart-Funktion aktivieren."

#~ msgid ""
#~ "You have the option to start all other arrays (those not needed for the "
#~ "root filesystem) later in the boot sequence. Doing so will give you "
#~ "greater control over the arrays with the mdadm configuration file. "
#~ "Starting all arrays at boot-time may be safer though."
#~ msgstr ""
#~ "Sie haben die Option, alle anderen Verb�diese die nicht f� "
#~ "Wurzeldateisystem ben�t werden) sp�r w�end des Bootvorgangs zu "
#~ "starten. Damit haben Sie gr�e Kontrolle �ie Verb�it Hilfe "
#~ "der Mdadm-Konfigurationsdatei. Es ist jedoch sicherer, alle Verb�eim "
#~ "Booten zu starten."

#~ 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 ""
#~ "Wenn die RAID-Laufwerke automatisch gestartet werden, werden alle RAID-"
#~ "Laufwerke beim Systemstart automatisch gefunden und gestartet. Diese "
#~ "Option sollte nur benutzt werden, falls der md-Treiber als Modul "
#~ "kompiliert wurde. Falls er in den Kernel einkompiliert wurde, f�er "
#~ "Kernel den automatischen Start beim Booten durch und Sie sollten diese "
#~ "Option deshalb nicht ausw�en."

#~ 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 ""
#~ "Wird der RAID-�erwachungsdaemon gestartet, so werden E-Mail-"
#~ "Benachrichtigungen verschickt, falls ein zum RAID geh�des Laufwerk "
#~ "ausf�t oder den Status �ert."

--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 4.1-6
Done: Felix Lechner <felix.lechner@lease-up.com>

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.

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 956350@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felix Lechner <felix.lechner@lease-up.com> (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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 12 Sep 2020 20:46:58 -0700
Source: mdadm
Architecture: source
Version: 4.1-6
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner <felix.lechner@lease-up.com>
Changed-By: Felix Lechner <felix.lechner@lease-up.com>
Closes: 619043 872118 915182 916946 924367 932791 933773 935184 940851 956350 960132 962946
Changes:
 mdadm (4.1-6) unstable; urgency=medium
 .
   * Install misc/mdcheck; thanks Richard Laager. (Closes: #960132)
   * Update French, Dutch and German debconf translations. (Closes: #935184,
     #940851, #956350)
   * Bring command-line help in line with manual page. (Closes: #932791)
   * Fix spelling and groff macro issues in manual pages. (Closes: #915182,
     #916946, #962946)
   * Explain 'max' keyword in command-line option --size. (Closes: #933773)
   * Patch d/README.recipes for clarity. (Closes: #619043)
   * Enable autopkgtest for installed version. Requires isolation-machine,
     untested. (Closes: #872118)
   * Adopt package. (Closes: #924367)
   * Turn on hardening.
   * Avoid a race condition in d/mdadm-shutdown.service.
   * Implement missing status option in /etc/init.d/mdadm-waitidle.
   * Add missing Documentation keys to several service files.
   * Upgrade debhelper compat to 13; use new prerequisite style.
   * Set Rules-Requires-Root: no.
   * Bump Standards-Version to 4.5.0.
   * Convert copyright to DEP-5 machine-readable format.
   * Host Vcs on salsa.d.o.
   * Adopt DEP-14 branch naming in Vcs-Git
   * Enable standard Salsa CI pipeline.
   * Fix typos in executables.
   * Explain that --name does not work in Grow mode.
   * Convert international debconf translations to UTF-8.
   * Capitalize first word in package synopsis.
   * Add Lintian overrides for tags that may not be appropriate.
Checksums-Sha1:
 873a812a68104f767be0d35b2b5c7e6e55b412d7 2148 mdadm_4.1-6.dsc
 7b5116fb99260d795b519f7c45e2590ca0f90784 100380 mdadm_4.1-6.debian.tar.xz
 948c8399bf8723b200e98c78366dd04928c24b02 5486 mdadm_4.1-6_source.buildinfo
Checksums-Sha256:
 c3116debefb5234d347fd3ac7aa3536ae4753ec80b9ec74fd4c628fd9db05148 2148 mdadm_4.1-6.dsc
 b95fd225cdc8576e785b72d53d2e3d6d5aa243c73228645a0aab5084ef267bcc 100380 mdadm_4.1-6.debian.tar.xz
 36c88aa092bec9037ef22dc4e347d0e7d80aa58ec4dea6e6aed8847b9ab22d3e 5486 mdadm_4.1-6_source.buildinfo
Files:
 4ff5b02c7cd441930b18151855880e64 2148 admin optional mdadm_4.1-6.dsc
 53eba9fdd269fff44726764c4c0f9cb4 100380 admin optional mdadm_4.1-6.debian.tar.xz
 a519f85c9e40526085e18b37f95e6fe4 5486 admin optional mdadm_4.1-6_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKvBAEBCgCZFiEE8E0cIgLi+g0BiFTarFipTxFhjuAFAl9dmHVfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw
NEQxQzIyMDJFMkZBMEQwMTg4NTREQUFDNThBOTRGMTE2MThFRTAbHGZlbGl4Lmxl
Y2huZXJAbGVhc2UtdXAuY29tAAoJEKxYqU8RYY7gQwkQAMgy5/OaE5b/pfuguw18
dubix9jfO9QzGz5Kd1nv6KDMRflYNuLjLRdZM088nRs1eVSrd9Ezc6GgS2UhuY02
3+QE8b4YDa6QaYHZZWoxVAkmKPGq9LNlmikI3RjxjmhrIwWPXqzJXOHsc2QI1Dn0
p/rFz7DeOQEgcm0+x5GUQSTuZ3v6FkewL0Ua8EEF5OPH34tUDelrjibiCa+6r9m8
TThLynOYCLYjHW6Remn74oPzL+wbxZQLp5tpDuhiv/2IHjvpqXOHsqKZlWu/Ikvw
y0R8Sl6ssN6CYbIQ3QnXnoBfw+J0NQrMiSW5mBL0klicVy/7CppdQU9lGzEtZult
oc2pu/uods7REM9i3NgLdlH7qNts5hJkZr5gdM1r1W/89TIZz8znE8ShFF6ewv4u
Jcx2jQuebQpkewll+1jYlhPDU3cCSBrZFtehJGIeHsUH3hEEFeel5HKY75E7yc02
jzXTbJQFhhmctmXkHb57IeEaw2F0LhoWTYsITSyfP86RcDPDRmH0tzAg4Pe2nJXO
r98NfNFqAiX+I/NY7tAWQjSonl54lOus/jrR14QX2r6EQO6JYlS0jIqnJ5mJxBu2
zvHs1qT7XSxxI31U3+aZtguFXrFIn0afpFa+wh9a8qFtBJUITBZ0yA06KYf361Zy
G6N3ANCsjUgzE0E9+wodE/gp
=mRDk
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: