Dear maintainer of lilo and Debian translators,
Some days ago, I sent a notice to the maintainer of the lilo 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 two
weeks, 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:
ar cs da de el es eu fi fr gl it ja nl pt pt_BR ru sv tr uk vi zh_CN
Among these, the following translations are incomplete: da el eu fi gl nl pt_BR tr uk zh_CN
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 lilo package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Sunday, September 13, 2009. 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):
Wednesday, September 02, 2009 : send the first intent to NMU notice to
the package maintainer.
Monday, September 07, 2009 : send this notice
Sunday, September 13, 2009 : (midnight) deadline for receiving translation updates
Monday, September 14, 2009 : build the package and upload it to DELAYED/7-day
send the NMU patch to the BTS
Monday, September 21, 2009 : 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 <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: lilo@packages.debian.org\n"
"POT-Creation-Date: 2008-10-27 11:51+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: note
#. Description
#: ../lilo.templates:1001
msgid "LILO configuration"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:1001
msgid ""
"It seems to be your first LILO installation. It is absolutely necessary to "
"run liloconfig(8) when you complete this process and execute /sbin/lilo "
"after this."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:1001
msgid "LILO won't work if you don't do this."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid "Deprecated parameters in LILO configuration"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid ""
"Deprecated files have been found on your system. You must update the "
"'install=' parameter in your LILO configuration file (/etc/lilo.conf) in "
"order to properly upgrade the package."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid "The new 'install=' options are:"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid ""
" new: install=bmp\n"
" old: install=/boot/boot-bmp.b"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid ""
" new: install=text\n"
" old: install=/boot/boot-text.b"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:2001
msgid ""
" new: install=menu\n"
" old: install=/boot/boot-menu.b or boot.b"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:3001
msgid "Do you want to add the large-memory option?"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:3001
msgid ""
"By default, LILO loads the initrd file into the first 15MB of memory to "
"avoid a BIOS limitation with older systems (earlier than 2001)."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:3001
msgid ""
"However, with newer kernels the combination of kernel and initrd may not fit "
"into the first 15MB of memory and so the system will not boot properly. It "
"seems that the boot issues appear when the kernel+initrd combination is "
"larger than 8MB."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:3001
msgid ""
"If this machine has a recent BIOS without the 15MB limitation, you can add "
"the 'large-memory' option to /etc/lilo.conf to instruct LILO to use more "
"memory for passing the initrd to the kernel. You will need to re-run the "
"'lilo' command to make this option take effect."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:3001
msgid ""
"If this machine has an older BIOS, you may need to reduce the size of the "
"initrd *before* rebooting. Please see the README.Debian file for tips on how "
"to do that."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:4001
msgid "Do you want to run /sbin/lilo now?"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:4001
msgid ""
"It was detected that it's necessary to run /sbin/lilo in order to update the "
"new LILO configuration."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:4001
msgid ""
"WARNING: This procedure will write data in your MBR and may overwrite some "
"things in that place. If you skip this step, you must run /sbin/lilo before "
"reboot your computer or your system may not boot again."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:5001
msgid "Invalid bitmap path"
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:5001
msgid ""
"A deprecated bitmap path entry has been discovered in your LILO "
"configuration file (/etc/lilo.conf). You must upgrade this path in order to "
"run LILO. You can also run liloconfig(8) and get a fresh configuration file."
msgstr ""
#. Type: title
#. Description
#: ../lilo.templates:6001
msgid "LILO configuration."
msgstr ""
#. Type: text
#. Description
#: ../lilo.templates:7001
msgid ""
"LILO, the LInux LOader, sets up your system to boot Linux directly from your "
"hard disk, without the need for a boot floppy."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:8001
msgid ""
"Hmm. I think you're configuring the base filesystem, and I'm therefore "
"simply going to exit successfully without trying to actually configure LILO "
"properly. If you're not doing that, this is an important bug against "
"Debian's lilo package, and should be reported as such..."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:9001
msgid ""
"You already have a LILO configuration in the file ${liloconf}. If you want "
"to use the new LILO boot menu, please take a look to /usr/share/doc/lilo/"
"examples/conf.sample and choose one of the bitmaps located on /boot."
msgstr ""
#. Type: error
#. Description
#. Type: error
#. Description
#. Type: error
#. Description
#. Type: error
#. Description
#: ../lilo.templates:10001 ../lilo.templates:12001 ../lilo.templates:17001
#: ../lilo.templates:18001
msgid "WARNING!"
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:10001
msgid ""
"You have an old incompatible lilo configuration file! Read the file /usr/"
"share/doc/lilo/INCOMPAT.gz and rerun /sbin/lilo to write the changes to your "
"boot sectors"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:11001
msgid "Install a boot block using your current LILO configuration?"
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:12001
msgid ""
"Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for "
"changes in the usage of the ${liloconf} file. If needed: edit ${liloconf} "
"and rerun '/sbin/lilo -v'"
msgstr ""
#. Type: select
#. Description
#: ../lilo.templates:13001
msgid "The following is the list of the available bitmaps"
msgstr ""
#. Type: error
#. Description
#. Type: error
#. Description
#. Type: error
#. Description
#: ../lilo.templates:14001 ../lilo.templates:23001 ../lilo.templates:25001
msgid "ERROR!"
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:14001
msgid "Correct ${liloconf} manually and rerun /sbin/lilo."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:15001
msgid "Wipe out your old LILO configuration and make a new one?"
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:16001
msgid "No changes made."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:17001
msgid ""
"Either your ${fstab} configuration file is missing, or it doesn't contain a "
"valid entry for the root filesystem! This generally means that your system "
"is very badly broken. Configuration of LILO will be aborted; you should try "
"to repair the situation and then run /usr/sbin/liloconfig again to retry the "
"configuration process."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:18001
msgid ""
"Your ${fstab} configuration file gives device ${device} as the root "
"filesystem device. This doesn't look to me like an \"ordinary\" block "
"device. Either your fstab is broken and you should fix it, or you are using "
"hardware (such as a RAID array) which this simple configuration program does "
"not handle."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:18001
msgid ""
"You should either repair the situation or hand-roll your own ${liloconf} "
"configuration file; you can then run /usr/sbin/liloconfig again to retry the "
"configuration process. Documentation for LILO can be found in /usr/share/doc/"
"lilo/."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:19001
msgid "Booting from hard disk."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:19001
msgid ""
"You must do three things to make the Linux system boot from the hard disk. "
"Install a partition boot record, install a master boot record, and set the "
"partition active. You'll be asked to perform each of these tasks. You may "
"skip any or all of them, and perform them manually later on."
msgstr ""
#. Type: note
#. Description
#: ../lilo.templates:19001
msgid ""
"This will result in Linux being booted by default from the hard disk. If "
"your setup is complicated or unusual you should consider writing your own "
"customised ${liloconf}. To do this you should exit this configuration "
"program and refer to the comprehensive lilo documentation, which can be "
"found in /usr/share/doc/lilo/."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:20001
msgid "Install a partition boot record to boot Linux from ${device}?"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:21001
msgid "Use LBA32 for addressing big disks using new BIOS features?"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:22001
msgid "Install a master boot record on ${disk}?"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:22001
msgid ""
"A master boot record is required to run the partition boot record. If you "
"are already using a boot manager, and want to keep it, answer \"no\" to the "
"following question. If you don't know what a boot manager is or whether you "
"have one, answer \"yes\"."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:23001
msgid "install-mbr failed! Your system may not be bootable."
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:24001
msgid "Make ${device} the active partition"
msgstr ""
#. Type: boolean
#. Description
#: ../lilo.templates:24001
msgid ""
"The master boot record will boot the active partition. If you want your "
"system to boot another operating system, such as DOS or Windows, by default, "
"answer \"no\" to the following question. You may still use your boot manager "
"or the master boot record to boot Linux. If you want the system to boot "
"Linux by default, answer \"yes\". In this case you could still boot some "
"other OS if you know what partition it is on."
msgstr ""
#. Type: error
#. Description
#: ../lilo.templates:25001
msgid "activate failed! Your system may not be bootable."
msgstr ""
Attachment:
signature.asc
Description: Digital signature