Dear maintainer of scponly and Debian translators, Some days ago, I sent a notice to the maintainer of the scponly 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 es eu fi fr gl it ja nl pt pt_BR ru sv tr vi
Among these, the following translations are incomplete: cs es eu fi gl it nl
pt_BR tr vi
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 scponly package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Thursday, February
11, 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):
Sunday, January 31, 2010 : send the first intent to NMU notice to
the package maintainer.
Friday, February 05, 2010 : send this notice
Thursday, February 11, 2010 : (midnight) deadline for receiving
translation updates
Friday, February 12, 2010 : build the package and upload it to
DELAYED/7-day
send the NMU patch to the BTS
Friday, February 19, 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: [email protected]\n" "POT-Creation-Date: 2009-07-10 13:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <em...@address>\n" "Language-Team: LANGUAGE <[email protected]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../scponly.templates:1001 ../scponly-full.templates:1001 msgid "Install the chrooted binary /usr/sbin/scponlyc SUID root?" msgstr "" #. Type: boolean #. Description #: ../scponly.templates:1001 ../scponly-full.templates:1001 msgid "" "If you want scponly to chroot into the user's home directory prior to doing " "its work, the scponly binary has to be installed in /usr/sbin/scponlyc and " "has to have the suid-root-bit set." msgstr "" #. Type: boolean #. Description #: ../scponly.templates:1001 ../scponly-full.templates:1001 msgid "" "This could lead (in the worst case) to a remotely exploitable root hole. If " "you don't need the chroot- functionality, don't install the file." msgstr "" #. Type: note #. Description #: ../scponly-full.templates:2001 msgid "Potential security hazard" msgstr "" #. Type: note #. Description #: ../scponly-full.templates:2001 msgid "" "WARNING: this package was compiled with rsync, unison and SVN support, which " "can be a potential SECURITY hazard if not configured correctly! Please read " "the file /usr/share/doc/scponly-full/SECURITY!" msgstr ""
signature.asc
Description: Digital signature
