Dear maintainer of efingerd and Debian translators,

Some days ago, I sent a notice to the maintainer of the efingerd Debian
package, mentioning the status of at least one old 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, so I will
proceed with the NMU.

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

The package debconf templates are currently completely translated to:
cs da de es fr nl pt_BR pt ru sk sv vi.

On top of these, the following translation is incomplete:

language        translated     fuzzy     untranslated
-----------------------------------------------------
  lt                0            6            3

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 efingerd package so I can incorporate them in the build.

The deadline for receiving updates and new translations is Monday,
August 27, 2012. 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, August 19, 2012      : send the first intent to NMU notice to
                                the package maintainer.
 Wednesday, August 22, 2012   : send this notice
 Monday, August 27, 2012      : deadline for receiving translation
                                updates
 Tuesday, August 28, 2012     : build the package and upload it to
                        DELAYED/3-day, send the NMU patch to the BTS.
 Thursday, August 31, 2012   :  NMU reaches incoming

Regards

David

# 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@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: efing...@packages.debian.org\n"
"POT-Creation-Date: 2010-01-01 21:30+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@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: boolean
#. Description
#: ../templates:1001
msgid "Permit users to have their own configurable finger replies?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:1001
msgid "You can decide if efingerd honours users' ~/.efingerd files."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"If someone from network fingers given user, and the user has ~/.efingerd "
"file readable and executable for efingerd daemon, this file will be executed "
"and its output will be sent to the fingerer."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"This can be either desired or not, depending on your system policy. In "
"particular, allowing .efingerd files allows users to cheat about their real "
"identity. However, efingerd can be configured to display users' full names "
"(from passwd) as the first line of the reply, so they cannot hide themselves "
"completely."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"There is however a slight security concern: if you allow .efingerd files, "
"these files will be executed under efingerd UID, so malicious users gain "
"access to all files owned by efingerd - this becomes important when you make "
"efingerd to log into some files writable by the daemon, unless you take "
"appropriate precautions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"If you are the only user, or you trust your users, there is no reason to "
"disable .efingerd files (and this is probably a reason you want to install "
"efingerd for). However, if you expect your users to be nasty, you should "
"better think about protecting from them - in particular, if you enable "
"logging, make sure they cannot fiddle with the logfile - this is UP TO YOU."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Display users' real names?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"By default, efingerd displays users real names (from passwd) as the first "
"line of finger reply. You may want to suppress it, but if you allow the use "
"of .efingerd files at the same time, be aware that users can hide their "
"identity for the fingerer."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid "If in doubt, select this option."
msgstr ""

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to