Quoting Ben Hutchings (ben@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.
Attachment:
signature.asc
Description: Digital signature