Re: D-I Stretch Alpha 1: block-udeb * for a few days?
Quoting Cyril Brulebois (k...@debian.org): Hello release team, Now that linux is built on all archs, we're able to contemplate a d-i release. I'm wondering whether enabling all block-udeb entries from the freeze hints file would be appropriate to make sure that no last moment update reaches testing while finishing up the Alpha 1 preparation. On a related note, it might be worth considering aging linux, it's been in a suitable state for a while, except for the FTBFS on ppc64el. I've put kernel maintainers in copy accordingly. I still have many l10n uploads to do, because of the massive update done by the Turkish translator, apparently fixing details nearly everywhere. I'm very slow at this, as I'm focused on other issues than Debian, so I end up uploading 1 or 2 packages a day...:-) This is not great importance, though, and shouldn't delay the release. signature.asc Description: Digital signature
Re: New debconf template for the linux package
Quoting Aurelien Jarno (aurel...@aurel32.net): +Template: linux-image-@abiname@@localversion@/postinst/mips-initrd-@abiname@@localversion@ +Type: note +_Description: Boot loader configuration must be updated to load initramfs + This kernel package will build an initramfs file + (/boot/initrd.img-@abiname@) for the boot loader to use in + addition to the kernel itself. This method, formerly unsupported + on MIPS, enables a more flexible boot process, and future kernel + versions may require a corresponding initrd.img to boot. + . + The currently running kernel has been booted without an initramfs. + You should reconfigure your boot loader to load the initramfs for + Linux version @abiname@ and for each later version. To achieve that + you might use the initrd.img symlink created by this kernel. The only remark I have would be suggesting top replace your boot laoder by the boot loader or the system's boot loader Ah, and maybe replace symlink by symbolic link in our dejargonization efforts...:-) signature.asc Description: Digital signature
Re: New debconf template for the linux package
Quoting Ben Hutchings (b...@decadent.org.uk): I would write something like: Boot loader configuration must be updated to load initramfs This kernel package will build an 'initramfs' file (/boot/initrd.img-@abiname@) that should be loaded by the boot loader in addition to the kernel itself. The initramfs enables a more flexible boot process, and it is likely that future kernel versions will not boot without an initramfs. . The currently running kernel has been booted without an initramfs. You should reconfigure your boot loader to load the initramfs for Linux version @abiname@ and for each later version. But I think that still needs improvement, for example to say clearly that each kernel version needs its own initramfs. Ben's version has the advantage (seen from my POV) to drop the your kernel which I was about to suggest to change (this is indeed not my kernel but the one running on the machine, which is not necessarily mine). OTOH, the same remark stands for your boot loader which I would replace by the boot loader. And, of course, Ben's rewrite puts a big reviewed by native speaker sticker on the template, which is great..:-) signature.asc Description: Digital signature
Bug#688423: [INTL:sv] Swedish strings for firmware-nonfree debconf
Quoting Martin Bagge (brot...@bsnet.se): package: firmware-nonfree severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. Unfuzzied file attached. sv.po Description: application/gettext signature.asc Description: Digital signature
Bug#685579: firmware-nonfree: General update after the debconf review process
Dear Debian maintainer, On Saturday, September 22, 2012, I sent you a notification about the beginning of a review action on debconf templates for firmware-nonfree. Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please consider using it EVEN if you committed files to your development tree as long as they were reported. This is particularly important for this package, as a late change in reviewed templates forced me to unfuzzy files as they were coming. The attached tarball contains: - debian/changelog with the list of changes - debian/control with rewrites of packages' descriptions - debian/templates with all the rewritten templates file(s) - debian/po/*.po with all PO files (existing ones and new ones) As said, please use *at least* the PO files as provided here, preferrably over those sent by translators in their bug reports. All of them have been checked and reformatted. In some cases, formatting errors have been corrected. The patch.rfr file contains a patch for the templates and control file(s) alone. Please note that this patch applies to the templates and control file(s) of your package as of Saturday, September 22, 2012. If your package was updated in the meantime, I may have updated my reference copybut I also may have missed that. This is indeed why I suggested you do not modified such files while the review process was running, remember..:-) It is now safe to upload a new package version with these changes. Please notify me of your intents with regards to this. There is of course no hurry to update your package but feel free to contact me in case you would need sponsoring or any other action to fix this. -- patch.tar.gz Description: Binary data --- firmware-nonfree.old/debian/templates/templates.license.in 2012-08-22 06:51:30.031755144 +0200 +++ firmware-nonfree/debian/templates/templates.license.in 2012-09-05 07:12:41.441931791 +0200 @@ -1,15 +1,24 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# debian-l10n-engl...@lists.debian.org for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: firmware-@package@/license/accepted Type: boolean Default: false -Description: Do you agree to the @license-title@? +_Description: Do you agree to the @license-title@? In order to install this package, you must agree to the following terms, the @license-title@. If you do not agree, the installation will be canceled. Template: firmware-@package@/license/error Type: error -Description: Declined @license-title@ - If you do not agree to the @license-title@ +_Description: Declined @license-title@ + If you do not agree to the @license-title@ license terms you cannot install this software. . The installation of this package has been canceled. --- firmware-nonfree.old/debian/changelog 2012-08-22 06:51:30.027755036 +0200 +++ firmware-nonfree/debian/changelog 2012-09-22 22:37:49.634926524 +0200 @@ -1,3 +1,23 @@ +firmware-nonfree (0.37) UNRELEASED; urgency=low + + * Debconf templates and debian/control reviewed by the debian-l10n- +english team as part of the Smith review project. Closes: #685579 + * [Debconf translation updates] + * Polish (Michał Kułach). Closes: #686601 + * Slovak (Slavko). Closes: #686678 + * Russian (Yuri Kozlov). Closes: #686681 + * Portuguese (Rui Branco). Closes: #686761 + * Danish (Joe Hansen). Closes: #687085 + * French (Christian Perrier). Closes: #687132 + * German (Chris Leick). Closes: #687338 + * Italian (Beatrice Torracca). Closes: #687768 + * Spanish; (Camaleón). Closes: #688029 + * Czech (Michal Simunek). Closes: #688131 + * Romanian (Andrei POPESCU). Closes: #688132 + * Swedish (Martin Bagge / brother). Closes: #688423 + + -- Christian Perrier bubu...@debian.org Wed, 22 Aug 2012 07:13:08 +0200 + firmware-nonfree (0.36) unstable; urgency=low * debian/control: Set Multi-Arch: foreign signature.asc Description: Digital signature
Bug#688131: [l10n:cs] Initial Czech translation of PO debconf template for firmware-nonfree 0.37
Quoting Michal Šimůnek (michal.simu...@gmail.com): Package: firmware-nonfree Version: 0.37 Severity: wishlist Tags: l10n, patch In attachment there is initial Czech translation of PO debconf template (cs.po) for package firmware-nonfree, please include it. Unfuzzied file cs.po Description: application/gettext signature.asc Description: Digital signature
Bug#688132: firmware-nonfree: Romanian translation of the debconf template
Quoting Andrei POPESCU (andreimpope...@gmail.com): Source: firmware-nonfree Severity: wishlist Tags: patch l10n Dear Maintainer, See attached the Romanian translation of the debconf template. Unfuzzied file. ro.po Description: application/gettext signature.asc Description: Digital signature
Reminder for firmware-nonfree translation updates (WAKE UP)
CZECH TEAM, WAKE UP! SPANISH TEAM, WAKE UP! SWEDISH TEAM^Martin, WAKE UP! This is a reminder for the running translation round for debconf templates of firmware-nonfree. Currently complete languages: da de fr it pl pt ru sk Currently existing but incomplete languages: Please send out updates before Wednesday, September 19, 2012. On Thursday, September 20, 2012, I will notify the firmware-nonfree maintainers that they can upload a new package version. So, if you have something being worked on, please send it as soon as possible. Please contact me privately if you want to obtain the PO file for incomplete languages. The POT file can be obtained from the list archives. There is always a chance that a translation you or your team sent slipped through my mail and spam filters. If you indeed send an update as a bug report and your language is still listed here, please point me to the bug number. -- signature.asc Description: Digital signature
Bug#688029: [INTL:es] Spanish debconf template translation for firmware-nonfree
Quoting Camaleón (noela...@gmail.com): Package: firmware-nonfree Version: 0.37 Severity: wishlist Tags: l10n patch Greetings, -- Camaleón And, as I did for other translations, here's the same translation unfuzzied after fixing the double space problem that was in the POT file sent to translators. To Camaleon: nothing to do on your side, don't worry. es.po Description: application/gettext signature.asc Description: Digital signature
Bug#687768: [INTL: it] Italian translation of debconf messages - firmware-nonfree
Quoting Beatrice Torracca (beatri...@libero.it): Package: firmware-nonfree Severity: wishlist Tags: l10n patch Hi. Please find attached the Italian translation of firmware-nonfree debconf messages proofread by the Italian localization team. As a string has double spaces, I fixed it in the English version...which fuzzies the translation. Unfuzzied translation attached. it.po Description: application/gettext signature.asc Description: Digital signature
Bug#687338: firmware-nonfree: [INTL:de] Initial German debconf translation
Quoting Chris Leick (c.le...@vollbio.de): Package: firmware-nonfree Version: 0.37 Severity: wishlist Tags: l10n patch Hi, please find attached the German translation of firmware-nonfree. As a double space wasdiscovered after the call for translation, a string would be fuzzied when it's fixed. Fixed translation attached. de.po Description: application/gettext signature.asc Description: Digital signature
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os-prober is run in the installer environment: umount: can't umount /var/lib/os-prober/mount: Invalid argument grub-probe: error: no such disk. grub-probe: error: no such disk. grub-probe: error: no such disk. Could be something like #686314. Can you try (in the installer) to do the workaround found there (loading the fuse module)? signature.asc Description: Digital signature
Bug#687132: firmware-nonfree: [INTL:fr] French debconf templates translation update
Package: firmware-nonfree Version: N/A Severity: wishlist Tags: patch l10n Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors. Thanks for taking care of warning translators before uploading a new version with string changes. It's highly appreciated. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash # Copyright (C) 2012 Debian French l10n team debian-l10n-fre...@lists.debian.org # This file is distributed under the same license as the formware-nonfree package. # # Translators: # Christian Perrier bubu...@debian.org, 2012. msgid msgstr Project-Id-Version: firmware-nonfree\n Report-Msgid-Bugs-To: firmware-nonf...@packages.debian.org\n POT-Creation-Date: 2012-09-05 07:12+0200\n PO-Revision-Date: 2012-09-05 07:10+0200\n Last-Translator: Christian Perrier bubu...@debian.org\n Language-Team: French debian-l10n-fre...@lists.debian.org\n Language: fr\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n 1);\n X-Generator: Lokalize 1.4\n #. Type: boolean #. Description #: ../templates/templates.license.in:2001 msgid Do you agree to the \@license-title@\? msgstr Acceptez-vous « @license-title@ » ? #. Type: boolean #. Description #: ../templates/templates.license.in:2001 msgid In order to install this package, you must agree to the following terms, the \@license-title@\. If you do not agree, the installation will be canceled. msgstr Afin de pouvoir installer ce paquet, il est indispensable d'accepter ce qui suit, « @license-title@ ». Si vous choisissez de ne pas accepter, l'installation sera interrompue. #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid Declined @license-title@ msgstr Refus de « @license-title@ » #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid If you do not agree to the \@license-title@\ license terms you cannot install this software. msgstr Comme vous n'avez pas accepté « @license-title@ », il n'est pas possible d'installer ce logiciel. #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid The installation of this package has been canceled. msgstr L'installation du paquet a donc été interrompue.
Bug#687085: [INTL:da] Danish translation of the debconf templates firmware-nonfree
Quoting Joe Dalton (joedalt...@yahoo.dk): Package: firmware-nonfree Severity: wishlist Tags: l10n patch Please include the attached Danish firmware-nonfree translations. Translation fixed after fixing the double space issue I lately discovered. da.po Description: application/gettext signature.asc Description: Digital signature
Bug#686678: firmware-nonfree: [INTL:sk] Slovak po-debconf translation
Le 06/09/2012 18:06, Slavko a écrit : Hi, Dňa Wed, 5 Sep 2012 07:19:13 +0200 Christian PERRIER bubu...@debian.org napísal: Fixed file attached. I am sorry, the attached sk.po file has no fuzzy strings. regards That's correct as I fixed the file..:-) -- Christian Perrier Chef du service Informatique Individuelle et Départementale Direction des Réseaux et de l'Informatique ONERA -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5048cd4c.5010...@onera.fr
Bug#686761: firmware-nonfree 0.37: [INTL:pt] Portuguese translation for debconf messages
As a spurious trailing space was discovered in one template, the fix for it fuzzies one string in this translation. Fixed file attached as fixing this requires no skills in Portuguese..:-) pt.po Description: application/gettext signature.asc Description: Digital signature
Bug#685579: Final update for English review (2nd take)
Quoting Christian PERRIER (bubu...@debian.org): Dear Debian maintainer, On Thursday, August 30, 2012, I notified you of the beginning of a review process concerning debconf templates for firmware-nonfree. The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original bug report. Please review the suggested changes, and if you have any objections, let me know in the next 3 days. However, please try to avoid uploading firmware-nonfree with these changes right now. The second phase of this process will begin on Sunday, September 02, 2012, when I will coordinate updates to translations of debconf templates. I just discovered a spurious trailing space in one template. I just correctedthis in the attached patch. I will fix translations as they come, as well as translations that already have been sent. --- firmware-nonfree.old/debian/templates/templates.license.in 2012-08-22 06:51:30.031755144 +0200 +++ firmware-nonfree/debian/templates/templates.license.in 2012-09-05 07:12:41.441931791 +0200 @@ -1,15 +1,24 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# debian-l10n-engl...@lists.debian.org for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: firmware-@package@/license/accepted Type: boolean Default: false -Description: Do you agree to the @license-title@? +_Description: Do you agree to the @license-title@? In order to install this package, you must agree to the following terms, the @license-title@. If you do not agree, the installation will be canceled. Template: firmware-@package@/license/error Type: error -Description: Declined @license-title@ - If you do not agree to the @license-title@ +_Description: Declined @license-title@ + If you do not agree to the @license-title@ license terms you cannot install this software. . The installation of this package has been canceled. --- firmware-nonfree.old/debian/changelog 2012-08-22 06:51:30.027755036 +0200 +++ firmware-nonfree/debian/changelog 2012-09-04 19:27:28.434193231 +0200 @@ -1,3 +1,14 @@ +firmware-nonfree (0.37) UNRELEASED; urgency=low + + * Debconf templates and debian/control reviewed by the debian-l10n- +english team as part of the Smith review project. Closes: #685579 + * [Debconf translation updates] + * Polish (Michał Kułach). Closes: #686601 + * Slovak (Slavko). Closes: #686678 + * Russian (Yuri Kozlov). Closes: #686681 + + -- Christian Perrier bubu...@debian.org Wed, 22 Aug 2012 07:13:08 +0200 + firmware-nonfree (0.36) unstable; urgency=low * debian/control: Set Multi-Arch: foreign signature.asc Description: Digital signature
Bug#686601: [INTL:pl] Polish debconf translation
Quoting Michał Kułach (michalkul...@gmail.com): Package: firmware-nonfree Severity: wishlist Tags: l10n patch Hi! Please add the attached Polish debconf translation. Thanks in advance, Meanwhile, I discovered a spurious trailing space in one template. This has been fixed but fuzzies the translation originally sent. Fixed file attached. pl.po Description: application/gettext signature.asc Description: Digital signature
Bug#686678: firmware-nonfree: [INTL:sk] Slovak po-debconf translation
Quoting Slavko (sla...@slavino.sk): Package: firmware-nonfree Severity: wishlist Tags: l10n patch Version: 0.37 The sk.po attached. Meanwhile, I discovered a spurious trailing space in one template. This has been fixed but fuzzies the translation originally sent. Fixed file attached. sk.po Description: application/gettext signature.asc Description: Digital signature
Bug#686681: firmware-nonfree: [INTL:ru] Russian debconf templates translation
Quoting Yuri Kozlov (yu...@komyakino.ru): Russian debconf templates translation is attached. Meanwhile, I discovered a spurious trailing space in one template. This has been fixed but fuzzies the translation originally sent. Fixed file attached. ru.po Description: application/gettext signature.asc Description: Digital signature
Bug#685579: [BTS#685579] templates://firmware-nonfree/{templates/templates.license.in} : Final update for English review
Dear Debian maintainer,
On Thursday, August 30, 2012, I notified you of the beginning of a review
process
concerning debconf templates for firmware-nonfree.
The debian-l10n-english contributors have now reviewed these templates,
and the final proposed changes are attached to this update to the
original bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading firmware-nonfree with these changes
right now.
The second phase of this process will begin on Sunday, September 02, 2012, when
I will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Sunday, September 23, 2012. Please avoid uploading a package with fixed
or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Monday, September 24, 2012, I will contact you again and will send a
final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
--
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: firmware-@package@/license/accepted
Type: boolean
Default: false
_Description: Do you agree to the @license-title@?
In order to install this package, you must agree to the following terms,
the @license-title@.
If you do not agree, the installation will be canceled.
Template: firmware-@package@/license/error
Type: error
_Description: Declined @license-title@
If you do not agree to the @license-title@
license terms you cannot install this software.
.
The installation of this package has been canceled.
Source: firmware-nonfree
Section: non-free/kernel
Priority: optional
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Uploaders: Bastian Blank wa...@debian.org, Frederik Schüler
f...@debian.org, Steve Langasek vor...@debian.org, dann frazier
da...@debian.org, maximilian attems m...@debian.org, Ben Hutchings
b...@decadent.org.uk
Standards-Version: 3.8.4
Build-Depends: debhelper (= 5)
Vcs-Svn: svn://svn.debian.org/kernel/dists/trunk/firmware-nonfree/
Vcs-Browser: http://svn.debian.org/wsvn/kernel/dists/trunk/firmware-nonfree/
Package: firmware-linux
Architecture: all
Depends: firmware-linux-free, firmware-linux-nonfree (= ${binary:Version})
Description: Binary firmware for various drivers in the Linux kernel
(meta-package)
This package depends on both free and non-free firmware which was
previously included in the Linux kernel.
Package: firmware-atheros
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Atheros wireless cards
This package contains the binary firmware for USB wireless network and
Bluetooth cards supported by the ar9170, ath3k or ath9k_htc drivers.
.
Contents:
* Atheros AR3012 rev 1.2.0.1 patch (ar3k/AthrBT_0x01020001.dfu)
* Atheros AR3012 rev 1.2.2.0 patch (ar3k/AthrBT_0x01020200.dfu)
* Atheros AR3012 rev 1.2.0.1 config (ar3k/ramps_0x01020001_26.dfu)
* Atheros AR3012 rev 1.2.2.0 26 MHz config (ar3k/ramps_0x01020200_26.dfu)
* Atheros AR3012 rev 1.2.2.0 40 MHz config (ar3k/ramps_0x01020200_40.dfu)
* Atheros AR7010 rev 1.0 firmware (ar7010.fw)
* Atheros AR7010 rev 1.1 firmware (ar7010_1_1.fw)
* Atheros AR9170 firmware (ar9170.fw)
* Atheros AR9271 firmware (ar9271.fw)
* Atheros AR3011 firmware (ath3k-1.fw)
* Atheros AR7010 firmware, version 1.3 (htc_7010.fw)
* Atheros AR9271 firmware, version 1.3 (htc_9271.fw)
Multi-Arch: ${firmware:Multi-Arch}
Homepage: http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git
Package: firmware-bnx2
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Broadcom NetXtremeII
This package contains the binary firmware for Broadcom NetXtremeII network
adapters supported by the bnx2 driver.
.
Contents:
* Broadcom NetXtremeII 5706/5708 firmware (mips), version Linux 2.6.32
[RFR] templates://firmware-nonfree/{templates/templates.license.in}
Please find, for review, the debconf templates and packages descriptions for
the firmware-nonfree source package.
This review will last from Sunday, August 26, 2012 to Wednesday, September 05,
2012.
Please send reviews as unified diffs (diff -u) against the original
files. Comments about your proposed changes will be appreciated.
Your review should be sent as an answer to this mail.
When appropriate, I will send intermediate requests for review, with
[RFRn] (n=2) as a subject tag.
When we will reach a consensus, I send a Last Chance For
Comments mail with [LCFC] as a subject tag.
Finally, the reviewed templates will be sent to the package maintainer
as a bug report, and a mail will be sent to this list with [BTS] as
a subject tag.
Specific comment for this package: the main point is turning these
templates to be translatable. However, as the real templates are built
from the templates/templates.license.in file, I have some doubts about
the right way to have templates really translated.
Still, it doesn't hurt to start having translatability..:)
Rationale:
--- firmware-nonfree.old/debian/templates/templates.license.in 2012-08-22
06:51:30.031755144 +0200
+++ firmware-nonfree/debian/templates/templates.license.in 2012-08-26
14:30:20.280441129 +0200
@@ -1,10 +1,10 @@
Template: firmware-@package@/license/accepted
Type: boolean
Default: false
-Description: Do you agree to the @license-title@?
+_Description: Do you agree to the @license-title@?
In order to install this package, you must agree to the following terms,
the @license-title@.
- If you do not agree, the installation will be canceled.
+ If you do not agree, the installation will be cancelled.
Template: firmware-@package@/license/error
Type: error
@@ -12,5 +12,5 @@
If you do not agree to the @license-title@
license terms you cannot install this software.
.
- The installation of this package has been canceled.
+ The installation of this package has been cancelled.
Few changes. Only a spelling fix.
--
Template: firmware-@package@/license/accepted
Type: boolean
Default: false
_Description: Do you agree to the @license-title@?
In order to install this package, you must agree to the following terms,
the @license-title@.
If you do not agree, the installation will be cancelled.
Template: firmware-@package@/license/error
Type: error
Description: Declined @license-title@
If you do not agree to the @license-title@
license terms you cannot install this software.
.
The installation of this package has been cancelled.
--- firmware-nonfree.old/debian/templates/templates.license.in 2012-08-22
06:51:30.031755144 +0200
+++ firmware-nonfree/debian/templates/templates.license.in 2012-08-26
14:30:20.280441129 +0200
@@ -1,10 +1,10 @@
Template: firmware-@package@/license/accepted
Type: boolean
Default: false
-Description: Do you agree to the @license-title@?
+_Description: Do you agree to the @license-title@?
In order to install this package, you must agree to the following terms,
the @license-title@.
- If you do not agree, the installation will be canceled.
+ If you do not agree, the installation will be cancelled.
Template: firmware-@package@/license/error
Type: error
@@ -12,5 +12,5 @@
If you do not agree to the @license-title@
license terms you cannot install this software.
.
- The installation of this package has been canceled.
+ The installation of this package has been cancelled.
Source: firmware-nonfree
Section: non-free/kernel
Priority: optional
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Uploaders: Bastian Blank wa...@debian.org, Frederik Schüler
f...@debian.org, Steve Langasek vor...@debian.org, dann frazier
da...@debian.org, maximilian attems m...@debian.org, Ben Hutchings
b...@decadent.org.uk
Standards-Version: 3.8.4
Build-Depends: debhelper (= 5)
Vcs-Svn: svn://svn.debian.org/kernel/dists/trunk/firmware-nonfree/
Vcs-Browser: http://svn.debian.org/wsvn/kernel/dists/trunk/firmware-nonfree/
Package: firmware-linux
Architecture: all
Depends: firmware-linux-free, firmware-linux-nonfree (= ${binary:Version})
Description: Binary firmware for various drivers in the Linux kernel
(meta-package)
This package depends on both free and non-free firmware which was
previously included in the Linux kernel.
Package: firmware-atheros
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Atheros wireless cards
This package contains the binary firmware for USB wireless network and
Bluetooth cards supported by the ar9170, ath3k or ath9k_htc drivers.
.
Contents:
* Atheros AR3012 rev 1.2.0.1 patch (ar3k/AthrBT_0x01020001.dfu)
* Atheros AR3012 rev 1.2.2.0 patch (ar3k/AthrBT_0x01020200.dfu)
* Atheros AR3012 rev 1.2.0.1 config (ar3k/ramps_0x01020001_26.dfu)
* Atheros AR3012 rev 1.2.2.0 26 MHz config (ar3k/ramps_0x01020200_26.dfu)
* Atheros AR3012 rev 1.2.2.0 40 MHz config (ar3k/ramps_0x01020200_40.dfu)
Re: [RFR] templates://firmware-nonfree/{templates/templates.license.in}
Quoting Justin B Rye (j...@edlug.org.uk): Christian PERRIER wrote: [...] + If you do not agree, the installation will be cancelled. [...] + The installation of this package has been cancelled. Few changes. Only a spelling fix. Sorry, Christian, this is a (particularly fiddly) en_GB-versus-en_US spelling rule difference. Ah, doh. Just learned something (which I'll probably forget soon)..:-) So no double l in en_US? Should I revise the package descriptions? Most of the synopses have I would recommend not to. See Bastian's explanations. signature.asc Description: Digital signature
Bug#685579: [LCFC] templates://firmware-nonfree/{templates/templates.license.in}
This is the last call for comments for the review of debconf
templates for firmware-nonfree.
(I speeded up the process as proposed changes are very small)
The reviewed templates will be sent on Wednesday, August 29, 2012 to this bug
report
and a mail will be sent to this list with [BTS] as a subject tag.
--
Template: firmware-@package@/license/accepted
Type: boolean
Default: false
_Description: Do you agree to the @license-title@?
In order to install this package, you must agree to the following terms,
the @license-title@.
If you do not agree, the installation will be canceled.
Template: firmware-@package@/license/error
Type: error
_Description: Declined @license-title@
If you do not agree to the @license-title@
license terms you cannot install this software.
.
The installation of this package has been canceled.
Source: firmware-nonfree
Section: non-free/kernel
Priority: optional
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Uploaders: Bastian Blank wa...@debian.org, Frederik Schüler
f...@debian.org, Steve Langasek vor...@debian.org, dann frazier
da...@debian.org, maximilian attems m...@debian.org, Ben Hutchings
b...@decadent.org.uk
Standards-Version: 3.8.4
Build-Depends: debhelper (= 5)
Vcs-Svn: svn://svn.debian.org/kernel/dists/trunk/firmware-nonfree/
Vcs-Browser: http://svn.debian.org/wsvn/kernel/dists/trunk/firmware-nonfree/
Package: firmware-linux
Architecture: all
Depends: firmware-linux-free, firmware-linux-nonfree (= ${binary:Version})
Description: Binary firmware for various drivers in the Linux kernel
(meta-package)
This package depends on both free and non-free firmware which was
previously included in the Linux kernel.
Package: firmware-atheros
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Atheros wireless cards
This package contains the binary firmware for USB wireless network and
Bluetooth cards supported by the ar9170, ath3k or ath9k_htc drivers.
.
Contents:
* Atheros AR3012 rev 1.2.0.1 patch (ar3k/AthrBT_0x01020001.dfu)
* Atheros AR3012 rev 1.2.2.0 patch (ar3k/AthrBT_0x01020200.dfu)
* Atheros AR3012 rev 1.2.0.1 config (ar3k/ramps_0x01020001_26.dfu)
* Atheros AR3012 rev 1.2.2.0 26 MHz config (ar3k/ramps_0x01020200_26.dfu)
* Atheros AR3012 rev 1.2.2.0 40 MHz config (ar3k/ramps_0x01020200_40.dfu)
* Atheros AR7010 rev 1.0 firmware (ar7010.fw)
* Atheros AR7010 rev 1.1 firmware (ar7010_1_1.fw)
* Atheros AR9170 firmware (ar9170.fw)
* Atheros AR9271 firmware (ar9271.fw)
* Atheros AR3011 firmware (ath3k-1.fw)
* Atheros AR7010 firmware, version 1.3 (htc_7010.fw)
* Atheros AR9271 firmware, version 1.3 (htc_9271.fw)
Multi-Arch: ${firmware:Multi-Arch}
Homepage: http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git
Package: firmware-bnx2
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Broadcom NetXtremeII
This package contains the binary firmware for Broadcom NetXtremeII network
adapters supported by the bnx2 driver.
.
Contents:
* Broadcom NetXtremeII 5706/5708 firmware (mips), version Linux 2.6.32
(bnx2/bnx2-mips-06-5.0.0.j3.fw)
* Broadcom NetXtremeII 5706/5708 firmware (rv2p), version Linux 2.6.32
(bnx2/bnx2-rv2p-06-5.0.0.j3.fw)
* Broadcom NetXtremeII 5709/5716 firmware (mips), version Linux 2.6.32
(bnx2/bnx2-mips-09-5.0.0.j3.fw)
* Broadcom NetXtremeII 5709/5716 firmware (rv2p), version Linux 2.6.32
(bnx2/bnx2-rv2p-09-5.0.0.j3.fw)
* Broadcom NetXtremeII 5709 A0/A1 firmware (rv2p), version Linux 2.6.32
(bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw)
* bnx2/bnx2-rv2p-06-6.0.15.fw
* Broadcom NetXtremeII 5709/5716 firmware (rv2p), version Linux 2.6.37
(bnx2/bnx2-rv2p-09-6.0.17.fw)
* Broadcom NetXtremeII 5709 A0/A1 firmware (rv2p), version Linux 2.6.37
(bnx2/bnx2-rv2p-09ax-6.0.17.fw)
* Broadcom NetXtremeII 5706/5708 firmware (mips), version Linux 2.6.38
(bnx2/bnx2-mips-06-6.2.1.fw)
* Broadcom NetXtremeII 5706/5708 firmware (mips), version Linux 3.3
(bnx2/bnx2-mips-06-6.2.3.fw)
* Broadcom NetXtremeII 5709/5716 firmware (mips), version Linux 2.6.39
(bnx2/bnx2-mips-09-6.2.1a.fw)
* Broadcom NetXtremeII 5709/5716 firmware (mips), version Linux 3.3
(bnx2/bnx2-mips-09-6.2.1b.fw)
Multi-Arch: ${firmware:Multi-Arch}
Homepage: http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git
Package: firmware-bnx2x
Architecture: all
Provides:
Suggests: initramfs-tools, linux-image
Replaces:
Conflicts:
Description: Binary firmware for Broadcom NetXtreme II 10Gb
This package contains the binary firmware for Broadcom NetXtreme II 10Gb
network adapters supported by the bnx2x driver.
.
Contents:
* Broadcom NetXtreme II 10Gb 57710, version 5.0.21.0 (bnx2x-e1-5.0.21.0.fw)
* Broadcom NetXtreme II 10Gb 57711, version 5.0.21.0 (bnx2x-e1h-5.0.21.0.fw)
* Broadcom NetXtreme II 10Gb 57710, version 7.0.29.0
(bnx2x/bnx2x-e1-7.0.29.0.fw)
* Broadcom
Re: [RFR] templates://firmware-nonfree/{templates/templates.license.in}
Quoting Justin B Rye (j...@edlug.org.uk): I think this means our d-l-e review boils down to: -Description: Do you agree to the @license-title@? +_Description: Do you agree to the @license-title@? Indeed. Also the other Description which I turned out into _Description to make the paragraph translatablewhich was the original motivation for the process. As a consequence, I moved directly to LCFC stage to speed thigns up and move quickly to translation stage. signature.asc Description: Digital signature
Bug#685579: firmware-nonfree: [debconf_rewrite] Debconf templates and debian/control review proposal
Package: firmware-nonfree Version: N/A Severity: normal Dear Debian maintainer, Hello, I just noticed new or modified debconf templates appearing for this package. I would like to suggest you to consider calling for debconf templates review AND translation updates when you introduce new debconf templates or modify the existing templates in a package or, if you prefer, to send a call for translations after uploading the first version that introduces new templates or templates changes. If you're interested in suggestions for doing this, you can find some at the end of this bug report. The debian-l10n-english team will now start a review, on our own initiative. It will be conducted through this bug report. Suggestions for future debconf templates review 1) Getting debconf templates reviewed -- The Debian i18n contributors have developed a set of suggestions for the writing style of debconf templates, to give them an overall consistency all around Debian. These writing style suggestions are explained in the Developers Reference. Lintian also warns about common writing style concerns. Maintainers are welcome when they ask for a review of debconf templates and/or packages descriptions on debian-l10n-engl...@lists.debian.org. It is of course not needed to wait for someone (such as me right me) proposing you such a review. In such situations (whether the review is requested by the maintainer or proposed by someone else), someone from the debian-l10n-english team will pick up the review to do, handle it, and finally send you a bug report with the suggested templates. If you want, you can ask for being CC'ed to the various discussions when the templates are reviewed. 2) Call for new translations As soon as the templates have been reviewed, you can ask Debian translators for new translations: Just go to your package's build tree and use: $ podebconf-report-po --call This will propose you a generic mail which is to be sent to debian-i...@lists.debian.org and call for new translations. This utility will mention existing translations to avoid duplicate work. It will also attach the needed material to this mail. Please also think about giving a deadline to translators. We like deadlines..:-) 3) Always call for translation updates before uploading --- (of course only when you change the debconf templates!) If your package already includes debconf translations (ie *.po files in debian/po), please consider calling for translation updates if you happen to change something in the templates...or just in case when you release a new version. This is done with the following command: $ podebconf-report-po This will build private mails to translators (ie people listed in Last-Translator in the PO files) for translations that are incomplete. These mails will included the needed PO file for each translator. -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120822045726.23020.41046.report...@mykerinos.kheops.frmug.org
Bug#685579: Acknowledgement (firmware-nonfree: [debconf_rewrite] Debconf templates and debian/control review proposal)
Indeed, the problemis not new templates. This is more the current debconf templates not being marked for translation. My proposal is to go through a review of English of these templates then a full translation update round. signature.asc Description: Digital signature
Bug#684293: installation-reports: Installer hangs at iso-scan step while mounting an extended partition
Quoting M H (mh000...@yahoo.com):
As a workaround the process 1291 can be killed to continue with the
installation.
The hang is caused by the script iso-scan.postinst (package: iso-scan), where
the extended partition is not omitted from the device list.
This bug has the same cause as the mountmedia bug #683849.
The following untested patch should solve this issue:
I finally had time to test it andit doesn't work:
The problem lies here:
+ if [ $PARTITION_TYPE != 0x5 ] [
$PARTITION_TYPE != 0xf ]; then
+ DEVS=${DEVS:+$DEVS\\n}$tmpdev
+ fi
\n is literally inserted in the list of devices, so mount actually
attemps to mount /dev/sda1\n/dev/sda2\n. As you might expect,
that fails..:-)
So, the patch should indeed be corrected to really build a list of
devices with hard returns between them.
signature.asc
Description: Digital signature
Bug#684293: installation-reports: Installer hangs at iso-scan step while mounting an extended partition
Quoting Christian PERRIER (bubu...@debian.org):
\n is literally inserted in the list of devices, so mount actually
attemps to mount /dev/sda1\n/dev/sda2\n. As you might expect,
that fails..:-)
So, the patch should indeed be corrected to really build a list of
devices with hard returns between them.
The attached patch works (tested). It still looks ugly to me and
there's probably a cleaner way to achieve what we want, though.
--
diff --git a/debian/changelog b/debian/changelog
index 88acfc8..2d80f24 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+iso-scan (1.41) UNRELEASED; urgency=low
+
+ * Do not attempt to mount extended partitions because of #684293
+
+ -- Christian Perrier bubu...@debian.org Sun, 12 Aug 2012 21:37:13 +0200
+
iso-scan (1.40) unstable; urgency=low
* Team upload
diff --git a/debian/iso-scan.postinst b/debian/iso-scan.postinst
index e3c07e4..308d3cd 100755
--- a/debian/iso-scan.postinst
+++ b/debian/iso-scan.postinst
@@ -274,7 +274,18 @@ while :; do
mkdir /cdrom 2/dev/null || true
mkdir /hd-media 2/dev/null || true
- DEVS=$(list-devices partition; list-devices disk; list-devices
maybe-usb-floppy)
+tmpdevs=$(list-devices partition; list-devices disk;
list-devices maybe-usb-floppy)
+DEVS=
+# Remove extended partitions
+for tmpdev in $tmpdevs; do
+ PARTITION_TYPE=$(blkid -p -s PART_ENTRY_TYPE $tmpdev |
cut -d ' ' -f 2 | cut -d \ -f 2)
+ if [ $PARTITION_TYPE != 0x5 ] [
$PARTITION_TYPE != 0xf ]; then
+ DEVS=${DEVS}
+$tmpdev
+ fi
+done
+
+
log devices found: '$DEVS'
STATE=10
continue
signature.asc
Description: Digital signature
Summary for D-I hangs in some configurations issues
Today, I did some testing about these often reported issues of D-I hanging, most often when detecting network hardware or when mounting ISO images. These issue is a kernel issue. It is being dealt with in #684293. A workaround has been committed and uploaded in mountmedia. It is confirmed working by my tests. Another workaround for iso-scan has been sent in #684293 (when I sent it, I forgot that this was the bug that had been reassigned to the kernel, sorry). It is also confirmed as working but I think it is quite ugly (blame my bad shell programming skills). The bug has been tagged pending by the kernel maintainers, so I guess that a kernel patch is on its way. If a new kernel with that patch reaches wheezy, then we don't need the workarounds anymore: - no need to commit one for iso-scan - need to revert the one in mountmedia -- signature.asc Description: Digital signature
Re: Bug#684293: root cause of mount hang in installer [kernel bug]
reassign 684293 linux severity 684293 critical thanks Quoting Brian Potkin (claremont...@gmail.com): On Sat 11 Aug 2012 at 19:07:33 +0200, Christian PERRIER wrote: Quoting M H (mh000...@yahoo.com): After some googling I found out that the root cause of the recent mount problems with extended partitions (maybe also mounting disks like sda) are related to the infinite loop kernel bug in __getblk_slow. (see the explanation: https://patchwork.kernel.org/patch/1189121/) The affected debian kernels should get fixed with the patch offered in kernel 3.2.24 (http://lwn.net/Articles/508225/). Is it me or do both these URL return 404? Quickly tested both of them a minute ago. They worked for me. OK, reassigning to the Linux kernel. To Debian Kernel team: this bug has been revealed in D-I beta1. Any attempt to mount an extended partition (which is done in both mountmedia and iso-scan) loops forever and D-I appears to be hanged. This happens for instance each time D-I looks for missing firmware on existing devices. We had several bug reports about this. mountmedia has been fixed (more with a workaround than a real fix) but iso-scan is still affected. So, it seems that the patch described above is highly wished for wheezy. It would be great to have it before D-I beta2, indeed. For that reason, I set the bug's severity to critical (breaks unrelated packages). signature.asc Description: Digital signature
Re: Bug#684293: root cause of mount hang in installer [kernel bug]
Quoting M H (mh000...@yahoo.com): After some googling I found out that the root cause of the recent mount problems with extended partitions (maybe also mounting disks like sda) are related to the infinite loop kernel bug in __getblk_slow. (see the explanation: https://patchwork.kernel.org/patch/1189121/) The affected debian kernels should get fixed with the patch offered in kernel 3.2.24 (http://lwn.net/Articles/508225/). Thanks for the investigation and your care looking out for the root cause of this. This bug, and probably all other hang bugs, should be reassign to the kernelpackage. Before doing so, I'm awaiting for input from a Kerneal Team person. signature.asc Description: Digital signature
Re: Bug#661069: d-i: radeon: Please make sure firmware is installed or the user warned about its lack
Quoting Ben Hutchings (b...@decadent.org.uk): Maybe the linux-image packages should also warn in case 1, probably using a different message. I have no specific advice about this but if that's the plan, pretty please put me into the loop (as I guess this will be done through debconf) so that I can coordinate a translation update round. signature.asc Description: Digital signature
Re: Bug#661379: debian-installer: Keyboard connected via Logitech Unifying sender/receiver stops working during installation
reassign 661379 linux tags 661379 d-i retitle 661379 Missing hid_logitech_dj module in D-I kernel thanks Quoting Matt Horan (m...@matthoran.com): I am seeing this behavior as well, and it makes installing Debian with my wireless keyboard and mouse impossible. The keyboard and mouse work fine when the system is up and running under wheezy. However, I wanted to reinstall wheezy, but cannot because the keyboard and mouse do not work in the installer. When the system is up and running, I see that the hid_logitech_dj module is loaded. Not sure if this is possibly missing from the installer. The choice of modules in the D-I kernel is shorter (for size issues) so it's very likely that adding this module could help. I see this in debian/installer/modules/input-modules: hid usbhid hid-apple ? hid-belkin ? hid-microsoft ? hid-logitech ? hid-monterey ? hid-sunplus ? hid-cherry ? synaptics_usb ? wistron_btns ? Dunno what the ? means but anyway, I see no hid-logitech-dj here... I suspect it was named hid-logitech and got renamed to hid-logitech-dj Kernel team? signature.asc Description: Digital signature
Bug#666108: Failed to Install Debian 6.0 on Dell PERC H710P
Quoting Jonathan Nieder (jrnie...@gmail.com): First, thanks very much for writing. Let's get this fixed. :) As for your question, the short answer is: I don't know. I can provide an updated kernel to test (and would be very interested in the result), but I do not know how to tell the Debian installer to use it. d-i team: advice? This is a situation where Kenshi Muto's backported d-i (stable D-I with a backported kernel) might help: http://kmuto.jp/debian/d-i/ signature.asc Description: Digital signature
Bug#669935: Debian Installer does apply keymap used during installation to resulting initramfs
Quoting Sebastian Pipping (sebast...@pipping.org): Thanks for that explanation. For that keyboard hook to do its work, KEYMAP=y needs to be set in the initramfs configuration (see the code of the hook itself). What can be done to set KEYMAP=y in a controlled manner from within the installer? The currently resulting KEYMAP=n does not work. It should IMHO be the default value. Hence keeping this bug report affected to initramfs-tools. I guess the package maintainer(s) may have a rationale for this default value but we need to hear it. By design, the installer should *not* change default settings of installed tools and packages. signature.asc Description: Digital signature
Bug#669935: Debian Installer does apply keymap used during installation to resulting initramfs
Quoting Sebastian Pipping (sebast...@pipping.org): The problem is the same is users setup their console keymap to be something else than US *after the system installation*. Jérémy seems to understand that sentence but honetsly I don't. Could you elaborate? Sure. You install Debian by choosing a US keymap. Then, on the installed system, you reconfigure console-setup (dpkg-reconfigure console-setup) and pick for instance a German keymap. Then, the initramfs will also lack a german keymap to be setup when prompting you for the encrypted partition password. Which, in short, confirms that the problem is not in the installer itself (that does nothing wrt initramfs) but in the tools that create the initramfsor maybe in console-setup OTOH, when looking at dpkg -L initramfs-tools, I see a file named /usr/share/initramfs-tools/hooks/keymap that is apparently meant exactly for this..:) signature.asc Description: Digital signature
Bug#600132: Announce of the upcoming NMU for the mkvmlinuz package
Dear maintainer of mkvmlinuz and Debian translators, Some days ago, I sent a notice to the maintainer of the mkvmlinuz 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 da de es eu fi fr gl it ja nl pl pt pt_BR ro ru sv vi 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 mkvmlinuz package so I can incorporate them in the build. The deadline for receiving updates and new translations is Thursday, February 09, 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): Friday, January 27, 2012 : send the first intent to NMU notice to the package maintainer. Wednesday, February 01, 2012 : send this notice Thursday, February 09, 2012 : (midnight) deadline for receiving translation updates Friday, February 10, 2012 : build the package and upload it to DELAYED/7-day send the NMU patch to the BTS Friday, February 17, 2012 : NMU uploaded to incoming Thanks for your efforts and time. -- -- # #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. # #, fuzzy msgid msgstr Project-Id-Version: PACKAGE VERSION\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-10-31 08:09+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: select #. Description #: ../mkvmlinuz.templates:1001 msgid Bootloader to use: msgstr #. Type: select #. Description #: ../mkvmlinuz.templates:1001 msgid Your PowerPC sub-architecture supports more than one bootloader, please select the one you want to use. msgstr signature.asc Description: Digital signature
Intent to NMU mkvmlinuz to fix pending po-debconf l10n bugs
Dear Debian maintainer, The mkvmlinuz Debian package, which you are the maintainer of, has pending bug report(s) which include translation updates or fixes for po-debconf, namely bug number 600132 (and maybe other similar bugs). The i18n team is now hunting the very last bits of missing localization and your package went on our radar. You may have uploaded recently but, unfortunately for you, you then got *another* l10n bug report. So, sorry for this, but the radar beeped at your package and here am I with an NMU intent...:-) I have the intention, as part of a more general action of the Debian i18n Task Force to build and possibly upload a non-maintainer upload for mkvmlinuz in order to fix this as well as all pending translations for the debconf templates. Of course, an upload made by you would even be better...:-) Such changes are always harmless, which explains why I safely consider building NMU's for such issues even though they're obviously non critical. The schedule for the NMU (in case it happens, that is if you agree with it or if I don't receive any answer in 2 days) is roughly the following: Friday, January 27, 2012 : send this notice Tuesday, January 31, 2012 : post a NMU announcement to debian-i18n with you (maintainer) CC'ed this can happen earlier if the maintainer agrees In such case, the deadlines below will also happen earlier Wednesday, February 08, 2012 : (midnight) deadline for receiving translation updates Thursday, February 09, 2012 : build the package and upload it to DELAYED/7-day send the NMU patch to the BTS Thursday, February 16, 2012 : NMU reaches incoming If you intent to upload yourself, please notify me so that I interrupt the process on my side. Please also don't upload without a discussion with me. Some translators might send a few new translations and I can handle a round of translation updates for you. Really, don't upload silently...:-) In case I upload an NMU, I will subscribe to the Package Tracking System for mkvmlinuz and follow its life for 60 days after my NMU in order to fix any issue potentially introduced by my upload. Let me know, as soon as possible, if you have any kind of objection to this process. If you'd rather do the fix yourself, I will of course leave the package alone. Same if you have reasons not to do the update now. -- signature.asc Description: Digital signature
Bug#632422: Closing now useless translation bug ([INTL:ko] Korean debconf template translation for linux-base)
reopen 632422 reassign 632422 src:linux-base thanks Quoting Jonathan Nieder (jrnie...@gmail.com): Christian PERRIER wrote: This translation is no longer needed as this package is no longer in unstable. Are you sure? Hmm, ooops. I've been abused by one of the l10n status pages. Sorry for the trouble. signature.asc Description: Digital signature
Bug#636624: linux-latest-2.6: [INTL:fr] French debconf templates translation update
Package: linux-latest-2.6 Version: N/A Severity: wishlist Tags: patch l10n Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash # Translation of linux-latest-2.6 debconf templates to French # Copyright (C) 2011 Debian French l10n team debian-l10n-fre...@lists.debian.org # This file is distributed under the same license as the linux-latest-2.6 package. # # Translator: # Christian Perrier bubu...@debian.org, 2011. msgid msgstr Project-Id-Version: linux-latest-2.6 VERSION\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2011-07-24 16:15+0200\n PO-Revision-Date: 2011-07-26 14:32+0200\n Last-Translator: Christian Perrier bubu...@debian.org\n Language-Team: French debian-l10n-fre...@lists.debian.org\n Language: \n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: Lokalize 1.2\n Plural-Forms: nplurals=2; plural=(n 1);\n #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid This system requires a different kernel configuration msgstr Modification indispensable de la configuration du noyau #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE (Physical Address Extension). However, the CPU in this system does not support PAE. msgstr La configuration « 686 » du noyau de Debian a été remplacée par la configuration « 686-pae » qui utilise PAE (« Physical Address Extension » : extension des adresses physiques). Cependant, le micro- processeur de ce système ne gère pas PAE. #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid You should install linux-image-486 and remove linux-image-686 and/or linux- image-2.6-686 if they are currently installed. msgstr Vous devriez installer le paquet linux-image-486 et supprimer linux- image-686 ou linux-image-2.6-686 s'ils sont actuellement installés.
Re: Changes to Debian Installer release process
Quoting Otavio Salvador (ota...@ossystems.com.br): Mostly; the only addition situation we'll need to rebuild the installer is when the amount of translation changes for a specific language so we get the 'translation-status' file updated into the initrd. We might need to find a way to avoid rebuilding just because *one* language changed. Mostly because this happens really often..we don't really have control about the translator's schedule and they happen to commit things more or less randomly (with peaks when something is changed in a string, or when strings are added: some like to be 100% all time long..:-)). As I'm watching all this very regularly, we could maybe imagine something where the i18n coordinator can trigger an l10n-rebuild because (s)he notices that a given language changed significantly enough to be worth itor because it has been too much time since the last rebuild and many very small changes piled up. signature.asc Description: Digital signature
Bug#626220: Did not support Intel 82579LM Gigabit Ethernet (needs current e1000e)
Quoting Bastian Blank (wa...@debian.org): I don't think this is up to you. The kernel includes many backports for new hardware support. OK, thanks for taking this over, Bastian. signature.asc Description: Digital signature
Re: [PATCH base-installer] Update i386 kernel selection for new flavours in wheezy
Quoting Ben Hutchings (b...@decadent.org.uk): The '686-bigmem' flavour will be renamed to '686-pae'; support both names. The '686' flavour will be removed, but we can still offer it if available. I uploaded b-i as part of a mass upload today, but will upload again so that this important change is already supported in daily builds. Thanks for your patch (which I applied blindly, I have to admit!). signature.asc Description: Digital signature
Bug#623037: general: Usb flash drive crashes Debian
Quoting Ben Hutchings (b...@decadent.org.uk): Given that Atanas says says the drive could be mounted, I think this is a kernel bug. See the section 'required information' at http://kernel-handbook.alioth.debian.org/ch-bugs.html. We may need a confirmation about the crash, don't we? i.e. confirm this is really a full crash of the entire system and not just some component in the desktop environment. signature.asc Description: Digital signature
Bug#605924: firmware-ipw2x00: License accept/decline question can't be displayed entirely in graphical installer
Package: firmware-ipw2x00 Severity: important This issue is a serious usability issue with the graphical installer (I haven't checked, yet, if the issue also happens with the text installer). When the ipw2x00 deb file is found by D-I at initial steps of install, it displays its accept/decline license question. However, the license text make the Yes/No buttons disappear and users can't see them to notice that the default is declining the license. That may be a cdebconf issue but, at least having the default to true would allow users to blindly type Enter and be able to continue the installation process. Having Decline as default then requires user to blindly hit left arrow, then Enter. That's not really obvious..:-) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101204181948.3207.82171.report...@mykerinos.kheops.frmug.org
Bug#605924: firmware-ipw2x00: License accept/decline question can't be displayed entirely in graphical installer
reassign 605924 cdebconf tags 605924 patch thanks Quoting Ben Hutchings (b...@decadent.org.uk): However, the license text make the Yes/No buttons disappear and users can't see them to notice that the default is declining the license. That may be a cdebconf issue This seems like a bug in the graphical front-end. It should use a scrolling text area if necessary. Yes, that's one. Joey found a solution, or workaround. Patch attached. but, at least having the default to true would allow users to blindly type Enter and be able to continue the installation process. Having Decline as default then requires user to blindly hit left arrow, then Enter. That's not really obvious..:-) We're not supposed to let users install the firmware without presenting them with the licence conditions. Setting the default to 'accept' makes it possible that they never see them (due to a high required priority). Yes, I know users don't read them anyway. But if we don't go through this charade then we could be forbidden to distribute the firmware at all. I understand. Sad that this brings a strong usability issue in D-I (as users need to scroll down the license to find the Yes/no buttons). signature.asc Description: Digital signature
Re: [PATCH] d-i manual: nuke references to kernel-img.conf
Quoting maximilian attems (m...@stro.at): In squeeze it is no longer necessary or useful to generate or to consult kernel-img.conf. Thanks to the new bootloader policy, see: http://kernel-handbook.alioth.debian.org/ch-update-hooks.html Thanks for the patch. I added committing it to my TODO list (I'll also try to learn about updating translation files for the D-I manualwe're stil lin the process of taking things over after Frans' loss, for the D-I manual). signature.asc Description: Digital signature
Re: Processed: Re: Bug#595914: Re: Re: Bug#595914: Bug-report / installation-report
Quoting Ben Hutchings (b...@decadent.org.uk): reassign 595914 kernel-wedge thanks The BCM57780 needs a separate PHY driver module. It looks like these aren't currently packaged in d-i. You should include kernel/drivers/net/phy/*.ko in an appropriate package, presumably nic-extra-modules-*. Thanks for the complete analysis that well completes my original wild guess analysis, Ben. Otavio, you're the most familiar person with kernel-wedge. I suspect that the above suggestion is trivial to apply when one exactly knows what to do..:-) signature.asc Description: Digital signature
Bug#512546: Ethernet card not found
Quoting Vincent McIntyre (vince.mcint...@atnf.csiro.au): Hi, this problem is also occurring on Dell Optiplex 780 machines, the PCI ID of the network card is 8086:10de. I tried installing using this netboot image: http://ftp.au.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/debian-installer/i386/ which has the date stamp '20090123lenny7' in boot-screens/f1.txt. Have you tried with the netboot (*not netinst*) image which you can find at http://www.debian.org/devel/debian-installer under Daily builds? signature.asc Description: Digital signature
Bug#590923: (forw) AW: [Pkg-samba-maint] Bug#590923: smbclient: Mounted directory does not show all directories or hung up
- Forwarded message from Jaekle, Andreas andreas.jae...@stahlgruber.de - Date: Fri, 30 Jul 2010 13:55:47 +0200 From: Jaekle, Andreas andreas.jae...@stahlgruber.de To: Christian PERRIER bubu...@debian.org Subject: AW: [Pkg-samba-maint] Bug#590923: smbclient: Mounted directory does not show all directories or hung up X-CRM114-Status: UNSURE (1.2189) This message is 'unsure'; please train it! Dear Christian, this is my kernel version : Linux presenter 2.6.26-2-686 #1 SMP Tue Mar 9 17:35:51 UTC 2010 i686 GNU/Linux If necessary I can setup a new virtual machine with a testing or unstable version. Regards i. A. Andreas Jäkle Leiter PC-Support (dv-pc) STAHLGRUBER GmbH Gruber Straße 65 * 85586 Poing Postfach 11 60 * 85580 Poing Telefon: 08121 707-77551 Fax: 08121 707-66551 andreas.jae...@stahlgruber.de -Ursprüngliche Nachricht- Von: Christian PERRIER [mailto:bubu...@debian.org] Gesendet: Freitag, 30. Juli 2010 12:50 An: Jaekle, Andreas; 590...@bugs.debian.org Betreff: Re: [Pkg-samba-maint] Bug#590923: smbclient: Mounted directory does not show all directories or hung up Quoting Jaekle, Andreas (andreas.jae...@stahlgruber.de): Package: smbclient Version: 2:3.2.5-4lenny9 Severity: critical Justification: breaks the whole system When I cifs mount a directory from a Netapp-Filer ONTAP 7.3.2 with a lot of subdirectories in it (~3000) and do a ls to get a directory listing the machine hangs up or I can just see a part of the directories. Are you in position to try reproducing this with a machine using testing or unstable? There are chances that this is a problem in the cifs kernel module rather than client utilities. So, we also need to know the version of the kernel packages you're using - End forwarded message - -- signature.asc Description: Digital signature
Bug#578349: linux-2.6: General update after the debconf review process (2nd version)
Quoting Ben Hutchings (b...@decadent.org.uk): Translators have been working hard and here is now the result of their efforts. [...] It is now safe to upload a new package version with these changes. Please notify me of your intents with regards to this. [...] All applied, thanks. I made an exception to my usual policy and did *not* subscribe to the PTS inn order to receive bug reports for the said package, while the call for translations was running. So, I catched up with all pending translations by going to the BTS and grabbing all l10n bug reports. I *may* have missed some (because of the huge number of BR for linux-2.6) in case they're not tagged l10n (which happens as some translators do forget this). In case this happened, I'll notice this later on with the l10n radar that catches all opened debconf l10n bugsonce you've uploaded the release of linux-2.6 that fixes the bunch of bug reports that are included in my patch. BTW, I'm deeply impressed (should I say scared?) by the pile of bugs in linux-2.6. I'm indeed impressed to see you guys still able to maintain that package..without giving up when bugs pile up this way You deserve congratulations for that work. signature.asc Description: Digital signature
Bug#580915: Danish translation needs an update
Hello Joe, The file you sent in #580915 is outdated as the debconf templates for the linux-2.6 package have been reviewed by debian-l10n-english in the meantime. Resycning your PO file with the current templates gives the attached PO file. Would you mind updating it and sending it back to this bug report? (please CC me if you do so) -- da.po Description: application/gettext signature.asc Description: Digital signature
Bug#579864: No variable matching in german translation for linux-2.6
The translation sent in this bug report has the following problem:
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid An error occurred while running the ${loader} boot loader in test mode.
msgstr Bei der Ausführung des Bootloaders im Testmodus ist ein Fehler
aufgetreten.
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:5001
msgid An error occurred while running the ${loader} boot loader.
msgstr Bei der Ausführung des Bootloaders ist ein Fehler aufgetreten.
The ${loader} variable is completely dropped from the translation
which, imho, is not correct.
I think that the following would be OK:
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid An error occurred while running the ${loader} boot loader in test mode.
msgstr Bei der Ausführung des ${loader} Bootloaders im Testmodus ist ein
Fehler aufgetreten.
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:5001
msgid An error occurred while running the ${loader} boot loader.
msgstr Bei der Ausführung des ${loader} Bootloaders ist ein Fehler
aufgetreten.
--
signature.asc
Description: Digital signature
Bug#579019: Wrong variable matching in Estonian translation
Some ${loader} variables are incorrectly matched as $loader in the
proposed file.
Fixed file attached.
--
et.po
Description: application/gettext
signature.asc
Description: Digital signature
Reminder for linux-2.6 translation updates
This is a reminder for the running translation round for debconf templates of linux-2.6. Currently complete languages: de es et fr ru sv vi Currently existing but incomplete languages: cs (for cs, the files sent in #579268 has 3 unstranslated strings) Please send out updates before Sunday, May 09, 2010. On Monday, May 10, 2010, I will notify the linux-2.6 maintainers that they can upload a new package version. So, if you have something being worked on, please send it as soon as possible. Please contact me privately if you want to obtain the PO file for incomplete languages. The POT file can be obtained from the list archives. There is always a chance that a translation you or your team sent slipped through my mail and spam filters. If you indeed send an update as a bug report and your language is still listed here, please point me to the bug number. -- signature.asc Description: Digital signature
Bug#580538: Incomplete translation for one string?
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid The 'depmod' command exited with the exit code ${exit_value}
(${SIGNAL}${CORE}).
msgstr La orden «depmod» finalizó con el código de salida «${exit_value}
(${SIGNAL}».
That seems incomplete:
- missing ${CORE}
- unclosed parenthesis
Attempt to fix this in the attached file.
--
es.po
Description: application/gettext
signature.asc
Description: Digital signature
Bug#578349: Wrong patch sent in initial bug report
-free section of the Debian
- archive before you can install these firmware files.
+ Most firmware files are not included in the system because they do
+ not conform to the Debian Free Software Guidelines. You may need to
+ reconfigure the package manager to include the contrib and non-free
+ sections of the package archive before you can install these
+ firmware files.
--- linux-2.6.old/debian/changelog 2010-03-31 07:33:05.944954082 +0200
+++ linux-2.6/debian/changelog 2010-04-19 18:18:27.361612638 +0200
@@ -1,4 +1,4 @@
-linux-2.6 (2.6.32-11) UNRELEASED; urgency=low
+linux-2.6 (2.6.32-12) UNRELEASED; urgency=low
[ Ben Hutchings ]
* [sparc] Provide io{read,write}{16,32}be() (Closes: #574421)
@@ -30,7 +30,12 @@
[ Ian Campbell ]
* Include Xen hypervisor in reportbug related to list.
- -- maximilian attems m...@debian.org Wed, 17 Mar 2010 18:48:22 +0100
+ [ Christian Perrier ]
+ * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project. Closes: #578349
+ * [Debconf translation updates]
+
+ -- Christian Perrier bubu...@debian.org Mon, 19 Apr 2010 18:18:24 +0200
linux-2.6 (2.6.32-10) unstable; urgency=low
signature.asc
Description: Digital signature
Bug#578349: Yet another patch
. You may need to reconfigure
- the package manager to include the non-free section of the Debian
- archive before you can install these firmware files.
+ Most firmware files are not included in the system because they do
+ not conform to the Debian Free Software Guidelines. You may need to
+ reconfigure the package manager to include the contrib and non-free
+ sections of the package archive before you can install these
+ firmware files.
--- linux-2.6.old/debian/changelog 2010-03-31 07:33:05.944954082 +0200
+++ linux-2.6/debian/changelog 2010-04-19 18:18:27.361612638 +0200
@@ -1,4 +1,4 @@
-linux-2.6 (2.6.32-11) UNRELEASED; urgency=low
+linux-2.6 (2.6.32-12) UNRELEASED; urgency=low
[ Ben Hutchings ]
* [sparc] Provide io{read,write}{16,32}be() (Closes: #574421)
@@ -30,7 +30,12 @@
[ Ian Campbell ]
* Include Xen hypervisor in reportbug related to list.
- -- maximilian attems m...@debian.org Wed, 17 Mar 2010 18:48:22 +0100
+ [ Christian Perrier ]
+ * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project. Closes: #578349
+ * [Debconf translation updates]
+
+ -- Christian Perrier bubu...@debian.org Mon, 19 Apr 2010 18:18:24 +0200
linux-2.6 (2.6.32-10) unstable; urgency=low
signature.asc
Description: Digital signature
Re: [LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Quoting Christian PERRIER (bubu...@debian.org): From what you write, it seems that we then need to add something to say more firmly that users *really* should let this action be perfomed or be prepared to have serious trouble at next reboot. Something like: The new Linux kernel version provides different drivers for some PATA (IDE) controllers. The names of some hard disk, CD-ROM, and tape devices may change. . It is now recommended to identify disk devices in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. . If you choose to not update the system configuration automatically, you must update device IDs yourself before the next system reboot or the system may become unbootable. As I got no further comment, this is what will now go in the bug report I'll send in a few seconds. In case someone want to comment, I suggest commenting in the bug report itself now. Please note that I intend to jump into a formal call for translations in 2 days, so comments need to come soon as, once the call is sent, changing the phrasing of what's being translated becomes much more complicated. -- signature.asc Description: Digital signature
Bug#578349: linux-2.6: [debconf_rewrite] Debconf templates and debian/control review
Package: linux-2.6
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Monday, April 19, 2010, I notified you of the beginning of a review process
concerning debconf templates for linux-2.6.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading linux-2.6 with these changes
right now.
The second phase of this process will begin on Thursday, April 22, 2010, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Thursday, May 13, 2010. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Friday, May 14, 2010, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
--- linux-2.6.old/debian/linux-base.templates 2010-03-31 07:33:05.952958142
+0200
+++ linux-2.6/debian/linux-base.templates 2010-04-19 07:12:17.707893653
+0200
@@ -1,20 +1,34 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
-_Description: Update disk device ids in system configuration?
- The new Linux kernel version provides different drivers for some
- PATA (IDE) controllers. The names of some hard disk, CD-ROM and
- tape devices may change.
+_Description: Update disk device IDs in system configuration?
+
+ The new Linux kernel version provides different drivers for some PATA
+ (IDE) controllers. The names of some hard disk, CD-ROM, and tape
+ devices may change.
.
- You are recommended to identify disk devices in configuration files
+ It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
- which will work with both old and new kernel versions. Your system
- configuration can be updated automatically in most cases.
+ which will work with both old and new kernel versions.
+ .
+ If you choose to not update the system configuration automatically,
+ you must update device IDs yourself before the next system reboot or
+ the system may become unbootable.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5,7
+_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
@@ -23,38 +37,41 @@
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-manual
-Type: note
-_Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
Template: linux-base/disk-id-manual-boot-loader
-Type: note
-_Description: Check the boot loader configuration before rebooting
- The boot loader configuration for this system was not recognised. These
+Type: error
+_Description: Boot loader configuration check needed
+ The boot loader configuration for this system
Re: [LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Quoting maximilian attems (m...@stro.at): + which will work with both old and new kernel versions. + . + The system configuration can be updated automatically in most cases. + Please choose whether you want this action to be performed. sorry to jump in late, but this added phrase might be a misguide. we already had a report of a non booting box by a user, who choose not to perform the proposed action. it came to surprise to him that he had to edit himself fstab boot loader and so on.. From what you write, it seems that we then need to add something to say more firmly that users *really* should let this action be perfomed or be prepared to have serious trouble at next reboot. Something like: The new Linux kernel version provides different drivers for some PATA (IDE) controllers. The names of some hard disk, CD-ROM, and tape devices may change. . It is now recommended to identify disk devices in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. . If you choose to not update the system configuration automatically, you must update device IDs yourself before the next system reboot or the system may become unbootable. signature.asc Description: Digital signature
Re: [LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Quoting Ben Hutchings (b...@decadent.org.uk):
On Mon, 2010-04-12 at 07:29 +0200, Christian PERRIER wrote:
This is the last call for comments for the review of debconf
templates for linux-2.6.
The reviewed templates will be sent on Wednesday, April 14, 2010 to the
package
maintainer as a bug report and a mail will be sent to this list with
[BTS] as a subject tag.
You haven't applied David's wording for
=ST-image-=V/postinst/missing-firmware-=V
Woops. this package's layout being quite unusual, some of my magic
scripts aren't fully operational on it...
--- linux-2.6.old/debian/linux-base.templates 2010-03-31 07:33:05.952958142
+0200
+++ linux-2.6/debian/linux-base.templates 2010-04-12 07:29:17.678189658
+0200
@@ -1,20 +1,23 @@
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
-_Description: Update disk device ids in system configuration?
+_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
- PATA (IDE) controllers. The names of some hard disk, CD-ROM and
+ PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
- You are recommended to identify disk devices in configuration files
+ It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
- which will work with both old and new kernel versions. Your system
- configuration can be updated automatically in most cases.
+ which will work with both old and new kernel versions.
+ .
+ The system configuration can be updated automatically in most cases.
+ Please choose whether you want this action to be performed.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5,7
+_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
@@ -23,38 +26,41 @@
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-manual
-Type: note
-_Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
Template: linux-base/disk-id-manual-boot-loader
-Type: note
-_Description: Check the boot loader configuration before rebooting
- The boot loader configuration for this system was not recognised. These
+Type: error
+_Description: Boot loader configuration check needed
+ The boot loader configuration for this system was not recognized. These
settings in the configuration may need to be updated:
.
- * The root device id passed as a kernel parameter
- * The boot device id used to install and update the boot loader
+ * The root device ID passed as a kernel parameter;
+ * The boot device ID used to install and update the boot loader.
.
- We recommend that you identify these devices by UUID or label, except that
- on MIPS systems this is not supported for the root device.
+ You should generally identify these devices by UUID or
+ label. However, on MIPS systems the root device must be identified by
+ name.
--- linux-2.6.old/debian/templates/temp.image.plain/templates 2010-03-31
07:33:05.088958975 +0200
+++ linux-2.6/debian/templates/temp.image.plain/templates 2010-04-12
21:41:20.276864590 +0200
@@ -87,7 +87,8 @@
.
${missing}
.
- Most firmware files are not included in the Debian system because
- no source code is available for them. You may need to reconfigure
- the package manager to include the non-free section of the Debian
- archive before you can install these firmware files.
+ Most firmware files are not included in the system because they do
+ not conform to the Debian Free Software Guidelines. You may need to
+ reconfigure the package manager to include the contrib and non-free
+ sections of the package archive before you can install these
+ firmware files.
signature.asc
Description: Digital signature
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
David didn't leave the linux-...@packages.qa.d.o CC'ed. Re-adding it so that kernel packages maintainers can comment (Ben at first). Quoting David Prévot (dav...@altern.org): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 31/03/2010 12:37, Christian PERRIER a écrit : Most firmware files are not included in the system because no source code is available for them. You may need to reconfigure the package manager to include the non-free section of the package archive before you can install these firmware files. It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Unless you are exclusively referencing the firmware-linux-nonfree package, which is in the non-free section, some firmware can also be available through the contrib section (bcm43xx-fwcutter used to download sources, extract and install firmware from these downloaded files. I don't know if some packages are still running this way). I really might be talking nonsense, but if not, what about (no doubt that it needs to be rephrased in proper English) : Most firmware files are not included in the system because they do not conform to the Debian Free Software Guidelines. You may need to reconfigure the package manager to include the contrib and non-free sections of the package archive before you can install these firmware files. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvBIv0ACgkQ18/WetbTC/oDTQCfStHyPv5ywdIaCjBOMm4X/VCU bOIAnA1krBbuCfWdenYAKLNmq6i79ecP =V2MH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-l10n-english-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hpr7u0$qm...@dough.gmane.org ** CRM114 Whitelisted by: WHITELIST ** -- signature.asc Description: Digital signature
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Quoting Ben Hutchings (b...@decadent.org.uk): It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Indeed, we do not have source code for any of the non-free firmware. In many cases it is under a BSDish licence and would thus become DFSG-free if the source code was released. Can you comment (maybe later) on David's proposal so that I can decide whether to include that paragraph in the reviewed templates. signature.asc Description: Digital signature
[LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
This is the last call for comments for the review of debconf
templates for linux-2.6.
The reviewed templates will be sent on Wednesday, April 14, 2010 to the package
maintainer as a bug report and a mail will be sent to this list with
[BTS] as a subject tag.
--
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
which will work with both old and new kernel versions.
.
The system configuration can be updated automatically in most cases.
Please choose whether you want this action to be performed.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
#flag:translate!:3,5,7
_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
.
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
#flag:translate!:3,5
_Description: Apply configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-manual
Type: error
#flag:translate!:3
_Description: Configuration files still contain deprecated device names
The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
Template: linux-base/disk-id-manual-boot-loader
Type: error
_Description: Boot loader configuration check needed
The boot loader configuration for this system was not recognized. These
settings in the configuration may need to be updated:
.
* The root device ID passed as a kernel parameter;
* The boot device ID used to install and update the boot loader.
.
You should generally identify these devices by UUID or
label. However, on MIPS systems the root device must be identified by
name.
Template: =ST-image-=V/postinst/depmod-error-initrd-=V
Type: boolean
Default: false
_Description: Abort installation after depmod error?
The 'depmod' command exited with the exit code ${exit_value}
(${SIGNAL}${CORE}).
.
Since this image uses initrd, the ${modules_base}/=V/modules.dep file
will not be deleted, even though it may be invalid.
.
You should abort the installation and fix the
errors in depmod, or regenerate the initrd image with a known good
modules.dep file. If you don't abort the installation, there is
a danger that the system will fail to boot.
Template: shared/kernel-image/really-run-bootloader
Type: boolean
Default: true
_Description: Run the default boot loader?
The default boot loader for this architecture is $loader, which is
present.
.
However, there is no explicit request to run that boot loader in
/etc/kernel-img.conf while GRUB seems to be installed with
a postinst hook set.
.
It thus seems that this system is using GRUB as
boot loader instead of $loader.
.
Please choose which should run: the default boot loader now, or the
GRUB update later.
Template: =ST-image-=V/postinst/bootloader-test-error-=V
Type: note
_Description: Error running the boot loader in test mode
An error occurred while running the ${loader} boot loader in test mode.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/postinst/bootloader-error-=V
Type: note
_Description: Error running the boot loader
An error occurred while running the ${loader} boot loader.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/prerm/removing-running-kernel-=V
Type: boolean
Default: true
_Description: Abort kernel removal?
You are running a kernel (version ${running}) and attempting to remove
the same version.
.
This can make the system unbootable as it will remove
/boot/vmlinuz-${running} and all modules under the directory
/lib/modules/${running}. This can only be fixed with a copy of the
kernel image and the corresponding modules.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.
Template: =ST-image-=V/prerm/would-invalidate-boot-loader-=V
Type: boolean
Default: true
_Description: Abort kernel removal?
This system uses a valid /etc/${loader}.conf file that mentions
${kimage}-=V. Removing =ST-image-=V will invalidate
that file.
.
You will need to edit /etc/${loader}.conf or re-target
symbolic links mentioned there (typically, /vmlinuz
[RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Please find, for review, the debconf templates for the linux-2.6 source package.
(I didn't review the package description)
This is a quite important review as some of these strings are likely
to appear during the system install. Some other will also appear
during kernel upgrades and, I guess, particularly for lenny-squeeze
upgrades.
I agreed with the Kernel Team for us to do a review of these changes.
Please note that, to cope with the specific layout of the debian/
directory in this package, I temporarily used a copy of
templates/temp.image.plain/templates, named
debian/temp.templates. That was meant for me to be able to use my
usual scripts..:-)
This review will last from Wednesday, March 31, 2010 to Saturday, April 10,
2010.
Please send reviews as unified diffs (diff -u) against the original
files. Comments about your proposed changes will be appreciated.
Your review should be sent as an answer to this mail.
When appropriate, I will send intermediate requests for review, with
[RFRn] (n=2) as a subject tag.
When we will reach a consensus, I send a Last Chance For
Comments mail with [LCFC] as a subject tag.
Finally, the reviewed templates will be sent to the package maintainer
as a bug report, and a mail will be sent to this list with [BTS] as
a subject tag.
Rationale:
--- linux-2.6.old/debian/linux-base.templates 2010-03-31 07:33:05.952958142
+0200
+++ linux-2.6/debian/linux-base.templates 2010-03-31 07:39:33.688998875
+0200
@@ -1,20 +1,23 @@
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
-_Description: Update disk device ids in system configuration?
+_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
- PATA (IDE) controllers. The names of some hard disk, CD-ROM and
+ PATA (IDE) controllers. The names of some hard disk, CD-ROM and
tape devices may change.
.
- You are recommended to identify disk devices in configuration files
+ It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
- which will work with both old and new kernel versions. Your system
- configuration can be updated automatically in most cases.
+ which will work with both old and new kernel versions.
+ .
+ The system configuration can be updated automatically in most cases.
+ Please choose whether you want this action to be performed.
I feel like ID is more appropriate than lowercas id as acronyms
are generally using uppercase. However, the current practice and
existing documentation may lead to keep id.
That said, I'm dropping a double space after full stop, which is
something we try to get rid of, during such review.
Turning You are recommended to It is now recommended. Passive form
being more usual in such case, I think. Also now as this was not
necessarily recommended in the past..:)
Split to another paragraph the statement that the system may be
automatically updated and confirm what's expected from the user.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5,7
+_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
@@ -23,14 +26,15 @@
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Mark variable-only strings as non translatable
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply these configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
Ditto
@@ -40,21 +44,23 @@
${id_map}
Template: linux-base/disk-id-manual
-Type: note
-_Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
I think that the error type is more likely to properly bring the
user's attention.
Turn the synopsis from a sentence to a title.
Device names are deprecated, right? So, just say itimho more directive.
Template: linux-base/disk-id-manual-boot-loader
-Type: note
-_Description: Check the boot loader configuration before rebooting
- The boot loader configuration for this system was not recognised. These
+Type: error
+_Description: Boot loader configuration check needed
+ The boot loader configuration for this system was not recognised. These
settings in the configuration may need to be updated:
.
- * The root device id passed as a kernel parameter
- * The boot
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
(thanks, Ben, for your comments. I was of course expecting them as it
is a little bit fun to see a Frenglish speaker reviewing texts for a
native speaker who is known as very clever with his own language..:-))
This is a quite important review as some of these strings are likely
to appear during the system install. Some other will also appear
during kernel upgrades and, I guess, particularly for lenny-squeeze
upgrades.
Actually, they shouldn't appear during install.
I went on this because of a recent report in D-I from a user who was
surprised to not see the template mentioning potentially mimssing
firmware. *this* one is likely to appear for some users, isn't it?
Anywa, even if it doesn't, I think that having that round of review
and of course the translation update round that will follow is still a
good improvement we can bring. After all, we're talking about a
somehow important package, right? ;-)
I feel like ID is more appropriate than lowercas id as acronyms
are generally using uppercase. However, the current practice and
existing documentation may lead to keep id.
'id' is short for 'identifier' and there is no reason to capitalise an
abbreviation of a single word. I believe 'ID' in capitals originally
stood for identity document, and while it is commonly used simply for
'identifier' it annoys my pedantic nature.
OK. Point taken. Reverting to id.
[...]
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply these configuration changes to disk device IDs?
This short description should match that of the previous template.
Ideally they would be the same template but AFAIK debconf has no
provision to make parts of a template conditional.
No, particularly when one wants them to be translatable.
I actually missed the identical synopsis for both templates. Fixed.
Template: linux-base/disk-id-manual
-Type: note
-_Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
I think that the error type is more likely to properly bring the
user's attention.
This is not necessarily an error.
Yep. That's debatable. My point, es explained, was getting attention,
which is better achieved with Type: error and, after all, in some
cases, that could turn into an error.
I leave you with the last word on this. Do you prefer me to revert to note?
- We recommend that you identify these devices by UUID or label, except that
- on MIPS systems this is not supported for the root device.
+ You should identify these devices by UUID or label, with the
+ noticeable exception of the root device for MIPS systems.
+
Another note turned into error and a synopsis turned as a title for
it
Drop double space
Add punctuation
Drop the use of first person. Rewrite the last sentence that looks
awkward to me (Germish? :-))
No, I wrote that. While it was slightly awkward, it was correct and
your change after the comma would make it ambiguous. MIPS users *must
not* use UUID or label for the root device id.
Ahh, ooops. So, not Germish. I was indeed convinced that except that
is too close to a false friend (for example for French speaker, as a
word for word translation of à part quewhich is bad French but
(too) often used). So, not awkward it was.
I changed it another way. This time mostly because I think that a
separate sentence has better chances to be catched by the target
audience (MIPS users):
You should identify these devices by UUID or label. This is however
not supported for the root device of MIPS systems.
New templates attached (Justin's proposal includedeven the Oxford
comma, which I leave you guys to debate about).
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
_Description: Update disk device ids in system configuration?
The new Linux kernel version provides different drivers for some
PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
which will work with both old and new kernel versions.
.
The system configuration can be updated automatically in most cases.
Please choose whether you want this action to be performed.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
#flag:translate!:3,5,7
_Description: Apply configuration changes to disk device ids?
These devices will be assigned UUIDs or labels:
.
${relabel}
.
Re: Loading firmware: untranslated dialog (bug #575456)
Quoting Ben Hutchings (b...@decadent.org.uk): The VCS branch for uploads to unstable is svn://svn.debian.org/svn/kernel/dists/sid/linux-2.6. Templates for linux-base are in debian/linux-base.templates. Templates for linux-image-* are in debian/templates/temp.image.plain/templates, but these are actually templates for templates as we need to substitute in the kernel version and so on. We'll apply those substitution to the translations too. I did check this out, but I didn't find any PO file in there. Is there some special mechanism in place to allow for localization of the kernel packages templates? signature.asc Description: Digital signature
Re: Loading firmware: untranslated dialog (bug #575456)
Quoting Ben Hutchings (b...@decadent.org.uk): I did check this out, but I didn't find any PO file in there. Is there some special mechanism in place to allow for localization of the kernel packages templates? There is no mechanism in place. However, I've now committed templates.pot etc. Thanks. I just had a look at these templates. Would you mind if we launch some review on debian-l10n-english? Not that I pretend that my knowledge of your language is better than yoours, Benbut more to guarantee some style consistency with other debconf templates (for instance, I spotted double spaces after full stopswhich we try to avoid). signature.asc Description: Digital signature
Loading firmware: untranslated dialog (bug #575456)
(see #575456) Frans closed the bug report (which is the right action) with the following comment: This dialog does not come from D-I, but from linux-2.6. I suspect that that was not 100% translated for the version currently in testing. Closing this report. However, this could mean it would be a good idea to add linux-2.6 to the list of packages in either level 2 or 3 as it is likely to show some internationalized material during some installs. CC'ing the Kernel Team (I hope I'm using the right mail address): if we go this way, where should I pick for kernel packages debconf translations (which VCS). signature.asc Description: Digital signature
Bug#546809: [Pkg-samba-maint] Bug#546809: listing contents of remote directory does not show all content and can cause kernel panic
Quoting Steve Langasek (vor...@debian.org): reassign 546809 linux-2.6 thanks On Tue, Sep 15, 2009 at 01:49:47PM -0700, Kevin Crain wrote: After mounting a remote directory, I 'cd' to a directory contained therein and do an 'ls'. This directory contains over 200 files but I can see only 131. If I do an 'ls some_file' on a specific file that is not listed it will list it. Browsing the remote directories using Konqueror shows all files. If I do an 'ls|less' on the directory with over 131 files the kernel panics and the system either locks up or reboots. Then you have a kernel bug. Reassigning. I agree this has nothing to do with samba, but isn't it weird that this is the first time we get such report? Is the kernel the stock lenny kernel on the client? signature.asc Description: Digital signature
Re: Coordinating efforts to get a new kernel in testing?
Quoting Luk Claes (l...@debian.org): Could this be prioritized by the involved teams (mostly kernel and release, I'd guess) or are there already some plans for this to happen? There are no plans to force anything in like some propose in such situations as there is no clear plan of the kernel team to get the remaining issues solved soon after it would be forced in. So, could we get some input from the kernel team on this topic, then? Are you guys prioritizing work to get a new kernel in testing or work to get yet another upstream release in unstable? (from the above sentence and the discussion we had during the D-I team meeting, you probably understand where is my own preference going) signature.asc Description: Digital signature
Coordinating efforts to get a new kernel in testing?
During the last meeting of the D-I 'team' (ahem) which logs can be read from http://wiki.debian.org/DebianInstaller/Meetings, the situation of the kernel packages wrt testing transition was raised. Apparently, having a new kernel in testing (whether this is 2.6.30 or whatever other funky new version appears soon is not really relevant) is quite hairy. Indeed hairy enough for this to not have happened since the release of lenny, 5 months ago. Among other things, that is a blocker for a release of D-I, which is otherwise nearly ready. From what was said during the D-I meeting (but more details can be bringed in by people who are more aware of this than me), a transition for D-I packages is similar to a library transition. http://release.debian.org/migration/testing.pl?package=linux-2.6 Could this be prioritized by the involved teams (mostly kernel and release, I'd guess) or are there already some plans for this to happen? (please respect Reply-To as -release is not meant to be a discussion list and the topic doesn't have much to do with D-I...except that we need this to happen for a release to happen) -- signature.asc Description: Digital signature
Re: Bug#523342: installation report Dell Optiplex 960: NIC driver not available
Quoting Charles Muller (acmul...@jj.em-net.ne.jp): Package: installation-reports Boot method: Netinstall Image version: Full URL to image you downloaded is best Date: 2009-04-09 Machine: Dell Optiplex 960 Processor: Quad 2.66 G Memory: 4 G Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[X] Stop here. Can't find NIC Intel 82567. Ubuntu has it, but apparently it's not in Squeeze To kernel people: is this something that's likely to be fixed in 2.6.28|2.6.29 ? signature.asc Description: Digital signature
Re: Bug#523342: installation report Dell Optiplex 960: NIC driver not available
Quoting Otavio Salvador (ota...@ossystems.com.br):
Yes, 2.6.27 already supports it in e1000e module, check:
ota...@neumann { ~/hacking/linux-2.6 }$ git describe
f4187b56e1f8a05dd110875d5094b21b51ebd79b
v2.6.27-rc4-296-gf4187b5
OK, so what would be the best way to tag this bug report as will be
fixed when we have an installer that includes this kernel?
signature.asc
Description: Digital signature
Re: linux-2.6 upload planned
Quoting dann frazier (da...@debian.org): hey, I wanted to give -release -boot a heads up that the kernel team is looking to do a linux-2.6 upload to sid tomorrow. As discussed on the d-i channel, delays in the d-i release have given us a short window to introduce a new build for inclusion in RC2. Changes pending for this update include: - a few local DoS security issues - the hppa kernel fix that was causing crashes during ruby builds (doesn't fix the FTBFS - that may be a userspace issue) - reintroduces a driver for the ia64 rtc (regression) - several other fixes of = important severity from Moritz's recent bug triage Does that include #508108 ? If there is a release, fixing that one would be worth it from what I read in it. signature.asc Description: Digital signature
Bug#508108: Reopening, bug not fixed in 2.6.26-12
Quoting Jurij Smakov (ju...@wooyd.org): Please enable them for the next upload (which will hopefully make it into lenny). If we want to release lenny some day, maybe not. D-I RC2 was delayed partly because of -12. Now that everything is in place for a release to happen (including the D-I RM back from holidays), I'm not sure that another delay is really welcome. Could we document that issue in the errata? signature.asc Description: Digital signature
Bug#509428: [Pkg-samba-maint] Bug#509428: libsmbclient: System freeze when accessing SAMBA/CIFS share on Network Appliances storage
severity 509428 important reassign 509428 smbfs thanks Quoting vogu00 (vog...@gmail.com): Package: libsmbclient Hmm, this has nothing to do with libsmbclient, rather smbfs In our network, there's a network storage (Network Appliances) that I mount on all the attached Linux clients via SAMBA or CIFS. Since 2 years, this works without any problems. I recently did some tests with Debian Lenny. In the beginning, everything went fine. Since an upgrade to Lenny (approx. 3 weeks ago), I have some very bad effects: Mounting the NetApp share is ok, but when changing to a directory below the mountpoint, the system quickly crashes or freezes. The directory in which one I change has some 250 directory entries. In the few cases, where the system doesn't crash and where I can do an ls, the result only shows some 145 of the 250 directories. As I told, the system normally freezes. It does this nearly every time when entering cd followed by TAB (for bash completion). In that case, nothing works any longer, not the mouse nor the keyboard. Remote ssh shells cannot be opened, the system can even not be pinged any longer; I have todo a reset (causing data loss for all opened applications). I do not use any special mount options, just mount.cifs //myserver/share /mnt/xxx or mount.smbfs ... I can easily reproduce the problem on - Debian Lenny (since I updated it +- 3 weeks ago; before that update, there was no problem) - Ubuntu 8.10 - Xubuntu 8.10 The problem does not appear on - Debian Etch - Ubuntu 8.04 I made my tests on 5 different PCs and also on some virtual machines. The results are the same everywhere. I am not sure if it really is a libsmbclient bug. It might be as well somewhere else in Samba. Bug #264943 in Launchpad, for Ubuntu 8.10, seems similar to this one. I'm not entirely sure of this, though. That needs investigation and re-reading that bug (which has a very long log and for which fixes are already in 3.2.6, IIRC). I prefer using the important severity here, to still allow the 3.2.5-2 packages to enter testing (we have enough good reasons for this). Please don't re-upgrade the bug severity too early. signature.asc Description: Digital signature
Bug#497530: Patch for the l10n upload of mkvmlinuz
Dear maintainer of mkvmlinuz, On Thursday, November 20, 2008 I sent you a notice announcing my intent to upload a NMU of your package to fix its pending l10n issues, after an initial notice sent on Saturday, November 15, 2008. We finally agreed that you would do the update yourself at the end of the l10n update round. That time has come. To help you out, here's the patch which I would have used for an NMU. Please feel free to use all of it...or only the l10n part of it. The corresponding changelog is: Source: mkvmlinuz Version: 34+nmu1 Distribution: unstable Urgency: low Maintainer: Christian Perrier [EMAIL PROTECTED] Date: Tue, 02 Dec 2008 07:48:22 +0100 Closes: 497530 505866 Changes: mkvmlinuz (34+nmu1) unstable; urgency=low . * Non-maintainer upload. * Fix pending l10n issues. Debconf translations: * Spanish. Closes: #497530 * Polish. Closes: #505866 -- diff -Nru mkvmlinuz-34+nmu1.old/debian/changelog mkvmlinuz-34+nmu1/debian/changelog --- mkvmlinuz-34+nmu1.old/debian/changelog 2008-11-15 19:24:25.047407538 +0100 +++ mkvmlinuz-34+nmu1/debian/changelog 2008-12-02 07:48:24.866706646 +0100 @@ -1,3 +1,12 @@ +mkvmlinuz (34+nmu1) unstable; urgency=low + + * Non-maintainer upload. + * Fix pending l10n issues. Debconf translations: +* Spanish. Closes: #497530 +* Polish. Closes: #505866 + + -- Christian Perrier [EMAIL PROTECTED] Tue, 02 Dec 2008 07:48:22 +0100 + mkvmlinuz (34) unstable; urgency=low * Add debconf translations: diff -Nru mkvmlinuz-34+nmu1.old/debian/po/es.po mkvmlinuz-34+nmu1/debian/po/es.po --- mkvmlinuz-34+nmu1.old/debian/po/es.po 1970-01-01 01:00:00.0 +0100 +++ mkvmlinuz-34+nmu1/debian/po/es.po 2008-11-15 19:28:54.439407000 +0100 @@ -0,0 +1,50 @@ +# mkvmlinuz translation to Spanish +# Copyright (C) 2008 +# This file is distributed under the same license as the lurker package. +# Changes: +# - Initial translation +# Francisco Javier Cuadrado [EMAIL PROTECTED] +# +# Traductores, si no conoce el formato PO, merece la pena leer la +# documentación de gettext, especialmente las secciones dedicadas a este +# formato, por ejemplo ejecutando: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Equipo de traducción al español, por favor lean antes de traducir +# los siguientes documentos: +# - El proyecto de traducción de Debian al español +# http://www.debian.org/intl/spanish/coordinacion +# especialmente las notas de traducción en +# http://www.debian.org/intl/spanish/notas +# - La guía de traducción de po's de debconf: +# /usr/share/doc/po-debconf/README-trans +# http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# +msgid +msgstr +Project-Id-Version: mkvmlinuz_34\n +Report-Msgid-Bugs-To: \n +POT-Creation-Date: 2006-10-31 08:09+0100\n +PO-Revision-Date: 2008-08-22 20:48+0100\n +Last-Translator: Francisco Javier Cuadrado [EMAIL PROTECTED]\n +Language-Team: [EMAIL PROTECTED]\n +MIME-Version: 1.0\n +Content-Type: text/plain; charset=UTF-8\n +Content-Transfer-Encoding: 8bit\n + +#. Type: select +#. Description +#: ../mkvmlinuz.templates:1001 +msgid Bootloader to use: +msgstr Cargador de arranque a usar: + +#. Type: select +#. Description +#: ../mkvmlinuz.templates:1001 +msgid +Your PowerPC sub-architecture supports more than one bootloader, please +select the one you want to use. +msgstr +Su subarquitectura de PowerPC es compatible con más de un cargador de +arranque, por favor seleccione el que quiere usar. diff -Nru mkvmlinuz-34+nmu1.old/debian/po/pl.po mkvmlinuz-34+nmu1/debian/po/pl.po --- mkvmlinuz-34+nmu1.old/debian/po/pl.po 1970-01-01 01:00:00.0 +0100 +++ mkvmlinuz-34+nmu1/debian/po/pl.po 2008-11-23 11:38:36.048832000 +0100 @@ -0,0 +1,34 @@ +# debconf templates for mkvmlinuz package +# Polish translation +# Copyright (C) +# Łukasz Paździora, 2008 +# +# This file is distributed under the same license as the mkvmlinuz package. +# +msgid +msgstr +Project-Id-Version: mkvmlinuz 34\n +Report-Msgid-Bugs-To: \n +POT-Creation-Date: 2006-10-31 08:09+0100\n +PO-Revision-Date: 2008-11-16 00:47+0200\n +Last-Translator: Łukasz Paździora [EMAIL PROTECTED]\n +Language-Team: Polish [EMAIL PROTECTED]\n +MIME-Version: 1.0\n +Content-Type: text/plain; charset=UTF-8\n +Content-Transfer-Encoding: 8bit\n + +#. Type: select +#. Description +#: ../mkvmlinuz.templates:1001 +msgid Bootloader to use: +msgstr Którego programu rozruchowego użyć: + +#. Type: select +#. Description +#: ../mkvmlinuz.templates:1001 +msgid +Your PowerPC sub-architecture supports more than one bootloader, please +select the one you want to use. +msgstr +Podstruktura Twojego PowerPC obsługuje więcej niż jeden program rozruchowy. +Proszę wybrać którego chcesz użyć. signature.asc Description: Digital signature
Bug#505866: Acknowledgement ([INTL:pl] Polish debconf template translation)
Quoting Łukasz Paździora ([EMAIL PROTECTED]): Messed up with encoding earlier. This one should be good. But a double quota was missing at the end of the file: msgid Your PowerPC sub-architecture supports more than one bootloader, please select the one you want to use. msgstr Podstruktura Twojego PowerPC obsługuje więcej niż jeden program rozruchowy. Proszę wybrać którego chcesz użyć. ^ here Corrected file attached -- pl.po Description: application/gettext signature.asc Description: Digital signature
Bug#497530: Announce of the upcoming NMU for the mkvmlinuz package
Dear maintainer of mkvmlinuz and Debian translators, Some days ago, I sent a notice to the maintainer of the mkvmlinuz 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 (with help of a powerpc user, probably). 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 ro ru sv vi 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 mkvmlinuz package so I can incorporate them in the build. The deadline for receiving updates and new translations is Wednesday, November 26, 2008. 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): Saturday, November 15, 2008 : send the first intent to NMU notice to the package maintainer. Thursday, November 20, 2008 : send this notice Wednesday, November 26, 2008 : (midnight) deadline for receiving translation updates Thursday, November 27, 2008 : build the package and upload it to DELAYED/2-day send the NMU patch to the BTS Saturday, November 29, 2008 : NMU uploaded to incoming Thanks for your efforts and time. -- -- # #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. # #, fuzzy msgid msgstr Project-Id-Version: PACKAGE VERSION\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-10-31 08:09+0100\n PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n Last-Translator: FULL NAME [EMAIL PROTECTED]\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: select #. Description #: ../mkvmlinuz.templates:1001 msgid Bootloader to use: msgstr #. Type: select #. Description #: ../mkvmlinuz.templates:1001 msgid Your PowerPC sub-architecture supports more than one bootloader, please select the one you want to use. msgstr signature.asc Description: Digital signature
Intent to NMU or help for an l10n upload of mkvmlinuz to fix pending po-debconf l10n bugs
Dear Debian maintainer, (oh no, not him again...) The mkvmlinuz Debian package, which you are the maintainer of, has pending bug report(s) which include translation updates or fixes for po-debconf, namely bug number 497530 (and maybe other similar bugs). The i18n team is now hunting the very last bits of missing localization and your package went on our radar. You may have uploaded recently but, unfortunately for you, you then got *another* l10n bug report. We really should prevent translators from translating..:-) So, sorry for this, but the radar beeped at your package and here am I with an NMU intent...:-) In case you can't update your package, I hereby propose, as part of a more general action of the Debian i18n Task Force to build and possibly upload a non-maintainer upload for mkvmlinuz in order to fix this as well as all pending translations for the debconf templates. Of course, as you seem pretty active on that package, an upload by you would also be OK...as long as it allows a round of translation updates. Such changes are always harmless, which explains why I safely consider building NMU's for such issues even though they're obviously non critical. The schedule for the NMU (in case it happens, that is if you agree with it or if I don't receive any answer in 10 days) is roughly the following: Saturday, November 15, 2008 : send this notice Wednesday, November 19, 2008 : post a NMU announcement to debian-i18n with you (maintainer) CC'ed Tuesday, November 25, 2008 : deadline for receiving translation updates Wednesday, November 26, 2008 : build the package and upload it to DELAYED/2-day send the NMU patch to the BTS Friday, November 28, 2008 : NMU reaches incoming If you intent to upload yourself, please discuss with me. I propose handling a translation update round and I can handle it myself for you. That will just require a few days. In case I upload an NMU, I will subscribe to the Package Tracking System for mkvmlinuz and follow its life for 60 days after my NMU in order to fix any issue potentially introduced by my upload. Let me know, as soon as possible, if you have any kind of objection to this process. If you'd rather do the fix yourself, I will of course leave the package alone. Same if you have reasons not to do the update now. -- signature.asc Description: Digital signature
Bug#495541: linux-image-2.6.26-1-686: Please reactivate CONFIG_ACPI_PROCFS_POWER
(the bug was already reported to powertop) Quoting maximilian attems ([EMAIL PROTECTED]): Being the source of the change, the consequences should have been tracked by the kernel team and the change made at the moment all userspace utilities have been updated. Which is what I call a transition. no the kernel is not a lib if an app doesn't work with default kernel it is plain buggy. I think this is mostly rethorical. Changing settings in the kernel is pretty much similar to changing the version of a library. So, it should be handled mostly the same way, IMHO: identify the affected packages, talk about it in -devel, organise a transition with the affected maintainers, track this down in the BTS and do the change when everything is ready. That undoubtfully consumes resources and I know these are scarce. In such case, the only solution left is to minimize such invasive changes. I sincerely hope that this story will lead the kernel team to consider such approach for upcoming similar changes you guys might want to do. deprecated ACPI_PROCFS_POWER will be set for lenny as it is show now that too much userspace is still too buggy to interpret the sys files. Thanks you very much for that decision. I think this is the wise choice, indeed, and I appreciate that the kernel team is taking this seriously. Really, it's much appreciated. signature.asc Description: Digital signature
Bug#495541: linux-image-2.6.26-1-686: Please reactivate CONFIG_ACPI_PROCFS_POWER
Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: important Dear kernel team, In #463253, it was reported that deactivating CONFIG_ACPI_PROCFS was too early as many userland utilities are still relying on /proc/acpi. So, the support for it was reinstated by Maks in 2.6.24-3. However, CONFIG_ACPI_PROCFS_POWER is left undefined and, therefore, some informations are not available (such as powertop failing to report the power consumption). Could you reactivate this option in an upcomiong uplad? Many thanks in advance... -- Package-specific info: -- System Information: Debian Release: lenny/sid Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.23 Debian configuration management sy ii initramfs-tools [linux-initra 0.92f tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.13-4 Yet Another mkInitRD Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-46GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495541: linux-image-2.6.26-1-686: Please reactivate CONFIG_ACPI_PROCFS_POWER
Quoting maximilian attems ([EMAIL PROTECTED]): So, the support for it was reinstated by Maks in 2.6.24-3. yes it was to give userspace some time to react. we allways stated that we *don't* guarantee to have it set for lenny. What I regret is that there should have been more communication with developers. Being the source of the change, the consequences should have been tracked by the kernel team and the change made at the moment all userspace utilities have been updated. Which is what I call a transition. I'm well aware of the lack of resources of the kernel team and I know that such transitions are hard to manage. However, in such cases, I would suggest you to be more conservative than you might have been, which is mostly the point of my bug report. However, CONFIG_ACPI_PROCFS_POWER is left undefined and, therefore, some informations are not available (such as powertop failing to report the power consumption). Could you reactivate this option in an upcomiong uplad? why? please upgrade your powertop installation. Well: [EMAIL PROTECTED]:/etc/acpi/events dpkg -s powertop Package: powertop .../... Version: 1.10-1 Is there something I'm missing here ? my powertop is still reporting that no ACPI power usage estimate available See also #491396 for acpi-support: that one lead me to think that there are still utilities that are broken by dropping /proc/acpi support and it would better be reinstated. (indeed all this plus following Sulamita Garcia's talk at DC8 and the discussions we had later brings me to the idea of a Power Management team, dealing with these issues and who could be a good reference point in such situations, but that's mostly another story) signature.asc Description: Digital signature
Re: project smith review linux-2.6 templates
Quoting maximilian attems ([EMAIL PROTECTED]): thank you very much committed to linux-2.6, rewritten templates should appear for 2.6.25 linux-2.6 upload. Good, thanks for taking care to have this interaction. Bastian mentioned me briefly on IRC that i18n is not really straghtforwarf but I would appreciate if you guys could consider it at some moment. signature.asc Description: Digital signature
Re: project smith review linux-2.6 templates
Quoting Justin B Rye ([EMAIL PROTECTED]):
My comments, slightly delayed by a weekend AFK.
Thanks Justin.
I assembled all your comments in my proposed templates, attached (with
diff wrt the original templates).
Template: =ST-image-=V/preinst/initrd-=V
Type: text
#flag:translate!:4
_Description: Initial RAMdisk image generation impossible
You are attempting to install an initrd kernel image (version
=V) on a machine currently running kernel version
${hostversion}.
.
No suitable tool for generating initrd images was found in
${ramdisk} and therefore no initrd image can be generated.
This will break the installation, unless such tools are also being installed
right now. Suitable tools:
.
${initrddep}
Template: =ST-image-=V/preinst/bootloader-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V).
This will not work unless the boot loader is configured to use an
initrd.
.
An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/lilo-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V).
This will not work unless the boot loader is configured to use an
initrd.
.
In order to configure LILO, you need to add
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/lilo.conf.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/elilo-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V).
This will not work unless the boot loader is configured to use an
initrd.
.
In order to configure LILO, you need to add
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/elilo.conf.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/lilo-has-ramdisk
Type: text
#flag:translate!:3
_Description: Removal of 'ramdisk' in /etc/lilo.conf
The following line in /etc/lilo.conf should be removed or commented out,
since the system uses initrd (or initramfs):
.
${LINE}
Template: =ST-image-=V/preinst/abort-install-=V
Type: note
_Description: Aborting install of unsupported initrd kernel image
You are attempting to install an initrd kernel image (version =V).
This will not work unless the boot loader is configured to use an
initrd.
.
An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting.
.
As the question that's relevant for this situation
was not shown, =ST-image-=V installation has been aborted.
Template: =ST-image-=V/preinst/failed-to-move-modules-=V
Type: note
_Description: Modules removal failure
You are attempting to install a kernel image (version =V).
However, the directory ${modules_base}/=V/kernel still exists.
.
An attempt was made to move the directory. However, that
action failed and ${modules_base}/=V could not be moved to
${modules_base}/${dest}.
.
You should move $modules_base/$version manually
and try re-installing this image.
Template: =ST-image-=V/preinst/overwriting-modules-=V
Type: boolean
Default: true
_Description: Abort installation since the kernel-image is already installed?
You are attempting to install a kernel image (version =V).
However, the directory ${modules_base}/=V/kernel still exists.
.
If this directory belongs to a previous ${package} package, and if
you have deselected some modules, or installed standalone modules
packages, this could have unexpected consequences.
.
If ${modules_base}/=V/kernel belongs to an old install of
${package}, you can now abort the
installation of this kernel image (nothing has been changed yet).
.
It is recommended to abort the installation unless you are
sure of what you are doing.
.
If you abort the installation, you should then move
${modules_base}/=V/kernel (for instance as
${modules_base}/=V.kernel.old) and then try
re-installing this image.
Template: =ST-image-=V/preinst/abort-overwrite-=V
Type: note
_Description: Aborting installation
Re: project smith review linux-2.6 templates
Quoting maximilian attems ([EMAIL PROTECTED]):
hello
i'm not entirely sure that every of those template make sense.
we already nuked some of them.
anyway lintian throws quite some errors and they seem justified.
latest version can be found in svn repo
svn co
svn://svn.debian.org/kernel/dists/trunk/linux-2.6/debian/templates/temp.image.plain
thanks for comments and rewording
Here's a complete rewrite. It is very hard to really comment on any
individual change I propose as I nearly completely rewrote some of the
templates.
Some key points:
-drop the awful use of 1st person. All available documentations
suggest this is a very amateur way to address users and I only know
about Manoj who supports this. The computer does not speak to users,
except when it is called HAL9000.
-split many paragraphs in more logical bits
-remove jargon as much as possible
-consistency: bootloader vs. boot loader
-mark templates as translatable (I hope that things are ready for
l10n...not sure of that)
-remove some very clumsy syntax (such a parenthesis beginning sentences)
I really hope that I didn't introduce misunderstandings
Template: =ST-image-=V/preinst/initrd-=V
Type: text
#flag:translate!:4
_Description: Initial RAMdisk image generation impossible
You are attempting to install an initrd kernel image (version
=V) on a machine currently running kernel version
${hostversion}.
.
No suitable tool for generating initrd images was found in
${ramdisk} and therefore no initrd image can be generated.
This will break the installation, unless such tools are also being installed
right now. Suitable tools:
.
${initrddep}
Template: =ST-image-=V/preinst/bootloader-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V)
This will not work unless the boot loader is configured to use an
initrd.
.
An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/lilo-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V)
This will not work unless the boot loader is configured to use an
initrd.
.
In order to configure LILO, you need to add
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/lilo.conf.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/elilo-initrd-=V
Type: boolean
Default: true
#flag:translate!:6
_Description: Abort initrd kernel image installation?
You are attempting to install an initrd kernel image (version =V)
This will not work unless the boot loader is configured to use an
initrd.
.
In order to configure LILO, you need to add
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/elilo.conf.
.
The boot loader must be configured to use such images and the system will not
boot until this is done.
.
This message will appear for any new kernel installation unless the
following is added to /etc/kernel-img.conf:
.
do_initrd = Yes
Template: =ST-image-=V/preinst/lilo-has-ramdisk
Type: text
#flag:translate!:3
_Description: Removal of 'ramdisk' in /etc/lilo.conf
The following line in /etc/lilo.conf should be removed or commented out,
since the system uses initrd/initramfs:
.
${LINE}
Template: =ST-image-=V/preinst/abort-install-=V
Type: note
_Description: Aborting install since loading an initrd kernel image
You are attempting to install an initrd kernel image (version =V)
This will not work unless the boot loader is configured to use an
initrd.
.
An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting.
.
As the question that's relevant for this situation
was not shown, =ST-image-=V installation is aborted.
Template: =ST-image-=V/preinst/failed-to-move-modules-=V
Type: note
_Description: Modules removal failure
You are attempting to install a kernel image (version =V).
However, the directory ${modules_base}/=V/kernel still exists.
.
An attempt was made to move the directory. However, that
action failed and ${modules_base}/=V could not be moved to
${modules_base}/${dest}.
.
You should move $modules_base/$version manually
and try re-installing this image.
Template: =ST-image-=V/preinst/overwriting-modules-=V
Type: boolean
Default:
Bug#415493: Announce of an upcoming upload for the mkvmlinuz package
Dear maintainer of mkvmlinuz and Debian translators, On Friday, April 11, 2008 I sent a notice to the maintainer of the mkvmlinuz Debian package, mentioning the status of at least one old po-debconf translation update in the BTS (bug #415493). 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 will upload the package himself but agreed for a l10n update round.. The full planned schedule is available at the end of this mail. The package is currently translated to: cs de fr it ja nl pt pt_BR ro ru sv vi 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 mkvmlinuz package so I can incorporate them in the build. The deadline for receiving updates and new translations is Tuesday, April 22, 2008. 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): Friday, April 11, 2008 : send the first intent to NMU notice to the package maintainer. Saturday, April 12, 2008 : send this notice Tuesday, April 22, 2008 : deadline for receiving translation updates Wednesday, April 23, 2008 or later : build by maintainer Thanks for your efforts and time. -- -- # #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. # #, fuzzy msgid msgstr Project-Id-Version: PACKAGE VERSION\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-10-31 08:09+0100\n PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n Last-Translator: FULL NAME [EMAIL PROTECTED]\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: select #. Description #: ../mkvmlinuz.templates:1001 msgid Bootloader to use: msgstr #. Type: select #. Description #: ../mkvmlinuz.templates:1001 msgid Your PowerPC sub-architecture supports more than one bootloader, please select the one you want to use. msgstr signature.asc Description: Digital signature
Intent to NMU mkvmlinuz to fix pending po-debconf l10n bugs
Dear Debian maintainer, The mkvmlinuz Debian package, which you are the maintainer of, has pending bug report(s) which include translation updates or fixes for po-debconf, namely bug number 415493 (and maybe other similar bugs). Even if we're still far from the release of the next Debian version, letting such bugs sleep in the BTS is simply lowering the chances that your package interaction with its users may be done in something else than the English language. It is also not encouraging for translators. I have the intention, as part of a more general action of the Debian i18n Task Force to build and possibly upload a non-maintainer upload for mkvmlinuz in order to fix this as well as all pending translations for the debconf templates. Of course, an upload made by you would even be better...:-) Such changes are always harmless, which explains why I safely consider building NMU's for such issues even though they're obviously non critical. The schedule for the NMU (in case it happens, that is if you agree with it or if I don't receive any answer in 14 days) is roughly the following: Friday, April 11, 2008 : send this notice Friday, April 25, 2008 : post a NMU announcement to debian-i18n with you (maintainer) CC'ed Monday, May 05, 2008 : deadline for receiving translation updates Tuesday, May 06, 2008 : build the package and upload it to DELAYED/2-day send the NMU patch to the BTS Thursday, May 08, 2008 : NMU reaches incoming If you intent to upload yourself, please notify me so that I interrupt the process on my side. In case I upload an NMU, I will subscribe to the Package Tracking System for mkvmlinuz and follow its life for 60 days after my NMU in order to fix any issue potentially introduced by my upload. Let me know, as soon as possible, if you have any kind of objection to this process. If you'd rather do the fix yourself, I will of course leave the package alone. Same if you have reasons not to do the update now. -- signature.asc Description: Digital signature
Re: Intent to NMU mkvmlinuz to fix pending po-debconf l10n bugs
Quoting Aurélien GÉRÔME ([EMAIL PROTECTED]): On Fri, Apr 11, 2008 at 11:00:27PM +0200, Christian Perrier wrote: Of course, an upload made by you would even be better...:-) Will do. If you agree, may I jump to the second stage of the nmu process which inludes a call for translations? That will allow a few more translators to send new or completed translations. It lasts for 10 days and, then, I'll send you a summary patch just as if I would be NMU'ing the package. Less work for you, more localization done...:-) signature.asc Description: Digital signature
Bug#461839: ping
Quoting Frederik Schueler ([EMAIL PROTECTED]): Hi Christian, how is it, do you have something already? Stange. I ran my rewrite-done script on Feb 13th.but, indeed, nothing popped up in the BTS. As I had outbound mail problems in the last weeks, I guess that explains. Re-sending it now. signature.asc Description: Digital signature
Bug#461839: redhat-cluster: General update after the debconf review process
be deployed to build high-availability services without the single point
+ of failure of a file server.
.
- This package contains userspace tools for creating and managing global
- file systems. GFS2 itself is a set of kernel modules.
+ This package provides userspace tools for creating and managing global
+ file systems.
.
- GFS2 *MUST NOT* be used in production enviroment yet.
+ The GFS2 kernel modules themselves are highly experimental and *MUST NOT*
+ be used in a production environment yet.
Package: gnbd-client
Section: admin
Architecture: any
Depends: ${shlibs:Depends}
Recommends: fence-gnbd (= ${binary:Version}), redhat-cluster-modules
-Description: global network block device - client tools
- GNBD allows to use block devices over the network. It is a modified
- version of the linux network block device for the use within a cluster
+Description: Red Hat cluster suite - global network block device client tools
+ This package is part of the Red Hat Cluster Suite, a complete
+ high-availability solution.
+ .
+ GNBD allows block devices to be used over the network. It is a modified
+ version of the Linux network block device for use within a cluster
environment.
.
- This package contains userspace tools for running GNBD clients.
+ This package provides userspace tools for running GNBD clients.
Package: gnbd-server
Section: admin
Architecture: any
Depends: ${shlibs:Depends}
Recommends: fence-gnbd (= ${binary:Version})
-Description: global network block device - server tools
- GNBD allows to use block devices over the network. It is a modified
- version of the linux network block device for the use within a cluster
+Description: Red Hat cluster suite - global network block device server tools
+ This package is part of the Red Hat Cluster Suite, a complete
+ high-availability solution.
+ .
+ GNBD allows block devices to be used over the network. It is a modified
+ version of the Linux network block device for use within a cluster
environment.
.
- This package contains userspace tools for running GNBD servers.
+ This package provides userspace tools for running GNBD servers.
Package: rgmanager
Architecture: any
Depends: ${shlibs:Depends}, cman (= ${binary:Version}), iproute,
iputils-arping, iputils-ping, nfs-kernel-server, nfs-common
Conflicts: nfs-user-server
-Description: clustered resource group manager
+Description: Red Hat cluster suite - clustered resource group manager
+ This package is part of the Red Hat Cluster Suite, a complete
+ high-availability solution.
+ .
Resource Group Manager provides high availability of critical server
applications in the event of planned or unplanned system downtime.
@@ -142,6 +182,9 @@
Architecture: all
Depends: bzip2
Description: Red Hat cluster suite - kernel modules source
- This package contains the source necessary for compiling the Red Hat
+ This package is part of the Red Hat Cluster Suite, a complete
+ high-availability solution.
+ .
+ This package provides the source necessary for compiling the Red Hat
cluster suite out-of-tree kernel modules gfs and gnbd against the
- linux tree.
+ Linux kernel source tree.
--- redhat-cluster.old/debian/changelog 2007-12-29 08:26:58.93775 +0100
+++ redhat-cluster/debian/changelog 2008-02-13 18:14:08.218678787 +0100
@@ -1,3 +1,25 @@
+redhat-cluster (2.20071214-3) UNRELEASED; urgency=low
+
+ * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project.
+Closes: #461839, #462802
+ * [Debconf translation updates]
+ * German. Closes: #462787
+ * German. Closes: #462801
+ * Norwegian Bokmål. Closes: #462812
+ * Vietnamese. Closes: #462913
+ * Galician. Closes: #462999
+ * Portuguese. Closes: #463012
+ * Finnish. Closes: #463946
+ * Czech. Closes: #464039
+ * Dutch. Closes: #464536
+ * Russian. Closes: #464758
+ * Japanese. Closes: #464870
+ * Italian. Closes: #465070
+ * French. Closes: #465553
+
+ -- Christian Perrier [EMAIL PROTECTED] Wed, 13 Feb 2008 18:14:08 +0100
+
redhat-cluster (2.20071214-2) unstable; urgency=low
* Add muissing build-dependency on libslang2-dev.
signature.asc
Description: Digital signature
Re: D-I Etch+1/2 kernel selection (was: Beta1 missing decisions and possible timeline)
Quoting Frans Pop ([EMAIL PROTECTED]): Sorry for the long explanation below, but I really want people to understand what is happening and why so we are agreed on this implementation and don't have nasty surprises after the point release. Your mail (which I read carefully) requires ACK from several people. You maybe want to target these people specifically with specific questions, in order to be sure to get the quick answers you need. Apart from that minor suggestion, kudos for that work. I'm pretty much ignorant with the involved issues and therefore won't care commenting in the details but, as often, I'm impressed..:-) signature.asc Description: Digital signature
Bug#462802: redhat-cluster: Superfluous white spaces in Debconf template
Quoting Helge Kreutzmann ([EMAIL PROTECTED]): Package: redhat-cluster Severity: minor Tags: patch While translating your Debconf template to German I noticed the following superfluous white spaces: Damn. Trailing white spaces after the rewrite. I corrected this in the rewritten templates and will also unfuzzy incoming translations. In short: maintainers, just do nothin and wait for the final patch in about 2 weeks. signature.asc Description: Digital signature
[LCFC] templates://redhat-cluster/{cman.templates}
This is the last call for comments for the review of debconf
templates for redhat-cluster.
The reviewed templates will be sent on Sunday, January 20, 2008 to the package
maintainer as a bug report and a mail will be sent to this list with
[BTS] as a subject tag.
--
Template: cman/upgrade-warning
Type: boolean
Default: false
_Description: Abort the potentially disruptive upgrade of Red Hat Cluster Suite?
The new version 2.0 of the Red Hat Cluster Suite is not compatible with
the currently installed one. Upgrading these packages without stopping
the complete cluster can cause file system corruption on shared storage
devices.
.
For instructions on how to safely upgrade the Red Hat Cluster Suite to
version 2.0, please refer to 'http://wiki.debian.org/UpgradeRHCSV1toV2'.
sSource: redhat-cluster
Section: admin
Priority: optional
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Uploaders: Bastian Blank [EMAIL PROTECTED], Frederik Schüler [EMAIL
PROTECTED]
Standards-Version: 3.7.3.0
Build-Depends: dpatch, debhelper (= 4.2.28), libxml2-dev, libncurses5-dev,
libopenais-dev (= 0.82-2), libvolume-id-dev (= 0.105-4), linux-libc-dev (=
2.6.22-6), libvirt-dev (= 0.3.0) [amd64 i386], libnss3-dev [amd64 i386],
libnspr4-dev [amd64 i386], bzip2, libslang2-dev
Build-Conflicts: libccs-dev, libcman-dev (= 2.0), libdlm-dev (= 2.0),
libcman2, libdlm2
Package: redhat-cluster-suite
Section: admin
Priority: optional
Architecture: all
Depends: cman, gfs-tools, gfs2-tools, rgmanager, clvm
Description: Red Hat cluster suite - meta package
RHCS is a cluster management infrastructure, for building
high-availability multi-node clusters with service and IP failover on
top of shared Fibre Channel/iSCSI storage devices.
.
The only scope for this package is to install the full Red Hat Cluster Suite
in one shot. It is safe to remove it.
Package: cman
Architecture: any
Section: admin
Pre-Depends: debconf | debconf-2.0
Depends: ${shlibs:Depends}, python, openais (= 0.82-2)
Conflicts: magma, libmagma1, libmagma-dev, ccs, fence, libiddev-dev,
fence-gnbd, gulm, libgulm1, libgulm-dev, magma-plugins
Replaces: ccs, fence, fence-gnbd
Description: Red Hat cluster suite - cluster manager
This package is part of the Red Hat Cluster Suite, a complete
high-availability solution.
.
CMAN is a symmetric general-purpose cluster manager. It provides a
service manager that handles service groups, plus a connection
manager that handles cluster membership management, messaging among
the cluster nodes, event notification, quorum and state transitions.
.
This package provides only userspace tools for controlling the
cluster manager itself.
Package: libcman2
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
Description: Red Hat cluster suite - cluster manager libraries
This package is part of the Red Hat Cluster Suite, a complete
high-availability solution.
.
CMAN is a symmetric general-purpose cluster manager. It provides a
service manager that handles service groups, plus a connection
manager that handles cluster membership management, messaging among
the cluster nodes, event notification, quorum and state transitions.
.
This package provides the client libraries.
Package: libcman-dev
Section: libdevel
Architecture: any
Depends: libcman2 (= ${binary:Version})
Description: Red Hat cluster suite - cluster manager development files
This package is part of the Red Hat Cluster Suite, a complete
high-availability solution.
.
CMAN is a symmetric general-purpose cluster manager. It provides a
service manager that handles service groups, plus a connection
manager that handles cluster membership management, messaging among
the cluster nodes, event notification, quorum and state transitions.
.
This package provides the files needed for developing applications.
Package: libdlm2
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
Description: Red Hat cluster suite - distributed lock manager library
This package is part of the Red Hat Cluster Suite, a complete
high-availability solution.
.
DLM is a symmetric general-purpose distributed lock manager. It is
used for example by GFS and the distributed volume manager.
.
This package provides a client library for applications using the
lock manager. The lock manager itself is a kernel module.
Package: libdlm-dev
Section: libdevel
Architecture: any
Depends: libdlm2 (= ${binary:Version})
Description: Red Hat cluster suite - distributed lock manager development files
This package is part of the Red Hat Cluster Suite, a complete
high-availability solution.
.
DLM is a symmetric general-purpose distributed lock manager. It is
used for example by GFS and the distributed volume manager.
.
This package provides the files needed for developing applications
that use the lock manager.
Package: gfs-tools
Architecture: any
Depends: ${shlibs:Depends}, psmisc, gfs2-tools
Recommends: redhat-cluster-modules
Section: admin
Description: Red Hat
Re: [RFR] templates://redhat-cluster/{cman.templates}
Quoting Justin B Rye ([EMAIL PROTECTED]): linux tree is incorrect, imho. That's the Linux kernel source tree, I think RHCS isn't Section: devel, so it would be good if it could avoid this jargon - only dogs and programmers do things against trees. In case you don't read blogs, that one made my day. Please just imagine myself alone hacking at 07:00am in my daily train to work and suddenly laughing out loud and looking silly to other train apssengers, *because of you*..:-) Unfortunately I'm not confident I can translate compiling an out-of-tree module against a source tree into English... We should some day invent an [EMAIL PROTECTED] locale... Otherwise, as usual, all suggestions adopted (unless I forgot some: I usually apply changes manually). signature.asc Description: Digital signature
Please consider interacting with translators when introducing/modifying new debconf templates
Hello, I just noticed new or modified debconf templates appearing for this package. I would like to suggest you to consider calling for debconf templates review AND translation updates when you introduce new debconf templates or modify the existing templates in a package or, if you prefer, to send a call for translations after uploading the first version that introduces new templates or templates changes. This will be picked up by the debian-i18n contributors for your package *this time*, but please read the following for future reference. 1) Get your debconf templates reviewed -- The Debian i18n contributors have developed a set of suggestions for the writing style of debconf templates, to give them an overall consistency all around Debian. These writing style suggestions are explained in the Developers Reference. Lintian also warns about common writing style concerns. You should anyway consider asking in [EMAIL PROTECTED] for a review of your debconf templates. This should be done by sending the original templates file(s), which are generally named debian/*templates to [EMAIL PROTECTED] It is suggested that you use a Subject field that the debian-l10n-english participants have normalized, namely: Subject: [TAF] templates://package/templates file(s) name(s) Replace package by you package name and templates file(s) name(s) by the name of your templates file. Someone will pick up the review to do, handle it, and finally send you a bug report with the suggested templates. If you want, you can ask for being CC'ed to the various discussions when the templates are reviewed. 2) Install po-debconf - If you test-build your package on your system, you shoud already have it. Otherwise, consider apt-get installing it. it will bring the needed utility. 3) Call for new translations As soon as the templates have been reviewed, you can ask Debian translators for new translations: Just go to your package's build tree and use: $ podebconf-report-po --call This will propose you a generic mail which is to be sent to [EMAIL PROTECTED] and call for new translations. This utility will mention existing translations to avoid duplicate work. It will also attach the needed material to this mail. Please also think about giving a deadline to translators. We like deadlines..:-) 4) Always call for translation updates before uploading --- (of course only when you change the debconf templates!) If your package already includes debconf translations (ie *.po files in debian/po), please consider calling for translation updates if you happen to change something in the templates...or just in case when you release a new version. This is done with the following command: $ podebconf-report-po This will build private mails to translators (ie people listed in Last-Translator in the PO files) for translations that are incomplete. These mails will included the needed PO file for each translator. -- -- signature.asc Description: Digital signature
Bug#298972: Announce of an upcoming l10n update for the mkvmlinuz package
I'm sending the message to both of you, as I'm unsure about who was finishing the l10n pieces. Attached you will find the Brazilian Portuguese translation for mkvmlinuz package, gzipped, UTF-8 encoded, tested with msgfmt (2t) and podebconf-display-po. As Sven hasn't built and uploaded mkvmlinuz yet, I've committed that new translation in the SVN. signature.asc Description: Digital signature
