Dear maintainer of bandwidthd and Debian translators, Some days ago, I sent a notice to the maintainer of the bandwidthd Debian package, mentioning the status of at least one old po-debconf translation update in the BTS.
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 four
days, 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 fr ja nl pt ru sv
Among these, the following translations are incomplete: <none>
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 bandwidthd package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Wednesday, May 05,
2010. 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):
Thursday, April 29, 2010 : send the first intent to NMU notice to
the package maintainer.
Thursday, April 29, 2010 : send this notice
Wednesday, May 05, 2010 : (midnight) deadline for receiving translation
updates
Thursday, May 06, 2010 : build the package and upload it to DELAYED/7-day
send the NMU patch to the BTS
Thursday, May 13, 2010 : NMU uploaded to incoming
Thanks for your efforts and time.
--
--
# 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 <em...@address>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: andr...@fatal.se\n" "POT-Creation-Date: 2007-03-23 10:46+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <em...@address>\n" "Language-Team: LANGUAGE <l...@li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. Type: select #. Description #: ../templates:1001 msgid "Interface to listen on:" msgstr "" #. Type: select #. Description #: ../templates:1001 msgid "" "Bandwidthd needs to know which interface it should listen for traffic on. " "Only a single interface can be specified. If you want to listen on all " "interfaces you should specify the metainterface \"any\". Running " "\"bandwidthd -l\" will list available interfaces." msgstr "" #. Type: string #. Description #: ../templates:2001 msgid "Subnets to log details about:" msgstr "" #. Type: string #. Description #: ../templates:2001 msgid "" "Bandwidthd can create graphs for one or several ip-subnets. Subnets are " "specified either in dotted-quad format (192.168.0.0 255.255.0.0) or in CIDR " "format (192.168.0.0/16) and separated by a comma. Example: 192.168.0.0/16, " "10.0.0.0 255.0.0.0, 172.16.1.0/24. If you don't know what to specify then " "you can use 0.0.0.0/0 but it is strongly discouraged." msgstr "" #. Type: boolean #. Description #: ../templates:3001 msgid "Output CDF data logs?" msgstr "" #. Type: boolean #. Description #: ../templates:3001 msgid "" "Bandwidthd can log captured traffic information to Common Data File (CDF) " "logs. These logs are required if you want to keep old information stored " "between restarts of the bandwidthd daemon. Also see the recovercdf " "configuration option." msgstr "" #. Type: boolean #. Description #: ../templates:4001 msgid "Recover old data from logs on restart?" msgstr "" #. Type: boolean #. Description #: ../templates:4001 msgid "" "If old data is going to be outputed in the graphs, it needs to be read when " "BandwidthD is restarted. Parsing the CDF logs can take quite some time on a " "slow machine so you might want to disable it, but then you'll lose the " "information in the graphs after a reboot and similar.... Also make sure the " "output_cdf config option is enabled." msgstr "" #. Type: string #. Description #: ../templates:5001 msgid "Graph webpage autorefresh delay (seconds):" msgstr "" #. Type: string #. Description #: ../templates:5001 msgid "" "With this option you can tweak the delay used in the html as \"META REFRESH" "\" value. The default is 150 seconds (2.5 minutes). To disable automatic " "reloads of the webpage enter 0. This way the visitor will have to manually " "push refresh in his browser to get updated graphs." msgstr "" #. Type: boolean #. Description #: ../templates:6001 msgid "Put interface in PROMISC mode?" msgstr "" #. Type: boolean #. Description #: ../templates:6001 msgid "" "If this option is enabled, all interfaces used to capture traffic " "information will be put in promiscuous mode. This way traffic thats not " "routed via the machine running bandwidthd might be trackable anyway. " "Enabling promiscuous mode will probably not be able to capture any more " "traffic in a normal switched network. Also rootkit detectors might warn " "about bandwidthd being a virus if using promiscuous mode. You should " "probably leave this option disabled." msgstr "" #. Type: string #. Description #: ../templates:7001 msgid "This sensors identification string:" msgstr "" #. Type: string #. Description #: ../templates:7001 msgid "" "Each sensor should have an identification string to be able to tell from " "where the traffic in the PostgreSQL-database was detected on. This option is " "usually set to the fully qualified hostname of the machine running the " "bandwidthd sensor. This needs to be a unique string which no other " "bandwidthd sensor that reports to the same database uses." msgstr ""
signature.asc
Description: Digital signature
