FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-31-2010, 05:57 AM
Christian PERRIER
 
Default 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 it....imho 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 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 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? :-))

--



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 these 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 recognised. 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 identify these devices by UUID or label, with the
noticeable exception of the root device for MIPS systems.

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 and /vmlinuz.old)
to not refer to ${kimage}-=V. Then, you will have to re-run ${loader}.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.

Template: =ST-image-=V/postinst/missing-firmware-=V
Type: note
_Description: Required firmware files may be missing
This system is currently running Linux ${runningversion} and you are
installing Linux ${version}. In the new version some of the drivers
used on this system may require additional firmware files:
.
${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.
--- 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.

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}

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}
@@ -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}

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 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 identify these devices by UUID or label, with the
+ noticeable exception of the root device for MIPS systems.
+
 
Old 03-31-2010, 02:54 PM
Ben Hutchings
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

On Wed, 2010-03-31 at 07:57 +0200, Christian PERRIER wrote:
> 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.

Actually, they shouldn't appear during install.

[...]
> 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".

'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.

[...]
> 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.

> 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.

This is not necessarily an error.

> Turn the synopsis from a sentence to a "title".
>
> Device names are deprecated, right? So, just say it....imho 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 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 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.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 03-31-2010, 04:37 PM
Christian PERRIER
 
Default 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 que"....which 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 included....even 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}
.
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 recognised. 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 identify these devices by UUID or label. This is however
not supported for the root device of MIPS systems.
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: error
_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: error
_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?
This system is 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
#flag:comment:2
#Translators, DO NOT translate things like "=ST-image-=V"
_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 and /vmlinuz.old)
to not refer to ${kimage}-=V. Then, you will have to re-run ${loader}.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.

Template: =ST-image-=V/postinst/missing-firmware-=V
Type: error
#flag:translate!:3
_Description: Required firmware files may be missing
This system is currently running Linux ${runningversion} and you are
installing Linux ${version}. In the new version some of the drivers
used on this system may require additional firmware files:
.
${missing}
.
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.
 
Old 04-01-2010, 12:00 AM
Ben Hutchings
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

On Wed, 2010-03-31 at 18:37 +0200, Christian PERRIER wrote:
> (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?

This is supposed to catch cases where the current installation depends
on firmware blobs embedded in drivers, which have subsequently been
remove. Since the release of lenny we have only removed blobs at the
same time as switching to new upstream versions, so the check is made
conditional on the new kernel package's upstream version being later
than the running kernel. This is not normally true during installation
of a stable release, although it can be true for installation of
testing/unstable.

Debian-installer has its own check and prompts for missing firmware and
that is what users should normally see during installation.

Finally, I think we can remove this check altogether after squeeze as
there are no more non-free blobs to remove.

> 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? ;-)

Sure.

> > > 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".

I was explaining my reasoning, but I accept that ID is more common and
may be more understandable. So, no need to revert.

[...]
> 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.
[...]

One more try:

"You should generally identify these devices by UUID or label. However,
on MIPS systems the root device must be identified by name."

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 04-11-2010, 02:20 PM
Christian PERRIER
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

David didn't leave the linux-2.6@packages.qa.d.o CC'ed.

Re-adding it so that kernel packages maintainers can comment (Ben at
first).



Quoting David Prévot (davidp@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-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/hpr7u0$qmb$1@dough.gmane.org
>
>
>
> ** CRM114 Whitelisted by: WHITELIST **
>

--
 
Old 04-11-2010, 02:44 PM
Ben Hutchings
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

On Sun, 2010-04-11 at 16:20 +0200, Christian PERRIER wrote:
> David didn't leave the linux-2.6@packages.qa.d.o CC'ed.
>
> Re-adding it so that kernel packages maintainers can comment (Ben at
> first).
>
>
>
> Quoting David Prévot (davidp@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.

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.

> > 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).
[...]

They might be; I hadn't thought tof that.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 04-11-2010, 02:54 PM
Christian PERRIER
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

Quoting Ben Hutchings (ben@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.
 
Old 04-11-2010, 09:11 PM
Ben Hutchings
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

On Sun, 2010-04-11 at 16:54 +0200, Christian PERRIER wrote:
> Quoting Ben Hutchings (ben@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.

I am happy with David's version, if you do not think it will be too much
trouble for translators who have already started.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 04-12-2010, 05:29 AM
Christian PERRIER
 
Default 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 and /vmlinuz.old)
to not refer to ${kimage}-=V. Then, you will have to re-run ${loader}.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.

Template: =ST-image-=V/postinst/missing-firmware-=V
Type: note
_Description: Required firmware files may be missing
This system is currently running Linux ${runningversion} and you are
installing Linux ${version}. In the new version some of the drivers
used on this system may require additional firmware files:
.
${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.
 
Old 04-12-2010, 10:38 AM
Ben Hutchings
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}

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

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 

Thread Tools




All times are GMT. The time now is 04:28 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org