Please find, for review, the debconf templates of microcode.ctl. This review will last from Sunday, June 03, 2007 to Wednesday, June 13, 2007. 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: @@ -1,14 +1,14 @@ Template: microcode.ctl/check-new Type: boolean Default: true -_Description: Do you want to check online for new Intel CPU microcodes? - microcode.ctl package needs the Intel microcodes to be usefull. +_Description: Download Intel CPU microcodes now? + The microcode.ctl package needs the Intel microcodes for its operation. . - Debian considers these microcode non-free (microcodes are program, but - without sources), so they cannot distributed within this package. + These microcodes are non-free software and cannot distributed + within the package. They can be downloaded from the Internet (the + expected download size is about 300-400Kb). . - The expected internet traffic is about 300-400Kb. - Alternatively, you can check /usr/share/doc/microcode.ctl/README.Debian - and download manually the microcodes or you can also run manually - /usr/sbin/update-intel-microcode . - + If you do not choose to download the microcodes now, please read + /usr/share/doc/microcode.ctl/README.Debian and download the needed + files manually or by running the '/usr/sbin/update-intel-microcode' + command. This is indeed a general rewrite..:-) I tried to avoid the mention of "Debian" and be mor efactual as well as use a writing style that's consistent with other packages. Instead of "online", I mention "from the Internet". --- /home/bubulle/travail/debian/rewrite/INTENT/microcode.ctl/microcode.ctl.old/debian/control 2007-05-25 08:09:45.640189246 +0200 +++ /home/bubulle/travail/debian/rewrite/INTENT/microcode.ctl/microcode.ctl/debian/control 2007-06-03 10:10:19.132310418 +0200 @@ -11,18 +11,16 @@ Suggests: wget, bzip2 Replaces: microcode-ctl Description: Intel IA32/IA64 CPU Microcode Utility - The microcode_ctl utility is a companion to the IA32 microcode driver - written by Tigran Aivazian <tigran@veritas.com>. The utility has two - uses: + The microcode_ctl utility is a companion to the IA32 microcode + driver. The utility has two uses: Do not mention upstream author in the package's description. That could change in the future and is already in debian/copyright. . - a) it decodes and sends new microcode to the kernel driver to be - uploaded to Intel IA32 family processors. (Pentium Pro, PII, - Celeron, PIII, Xeon, Pentium 4, etc.) and the Intel x86_64 - family processors - b) it signals the kernel driver to release any buffers it may hold + - decodes and sends new microcode to the kernel driver for Intel IA32 + family (Pentium Pro, PII, Celeron, PIII, Xeon, Pentium 4, etc.) and + Intel x86_64 family processors; + - signals the kernel driver to release any buffers it may hold. Recommended way to present itemized lists . The microcode update is volatile and needs to be uploaded on each - system boot i.e. it doesn't re-flash your CPU permanently, reboot and - it reverts back to the old microcode. The ideal place to load - microcode is in BIOS, but most vendors never update it! - + system boot, i.e. it doesn't re-flash the CPU permanently, reboot and + it reverts back to the old microcode. Ideally, the microcode should be + updated by the computer's BIOS, but most vendors do not implement that + behavior. I'm not sure that this is easy to understand, indeed. I even wonder whether this paragraph adds value. --
Template: microcode.ctl/check-new Type: boolean Default: true _Description: Download Intel CPU microcodes now? The microcode.ctl package needs the Intel microcodes for its operation. . These microcodes are non-free software and cannot distributed within the package. They can be downloaded from the Internet (the expected download size is about 300-400Kb). . If you do not choose to download the microcodes now, please read /usr/share/doc/microcode.ctl/README.Debian and download the needed files manually or by running the '/usr/sbin/update-intel-microcode' command.
--- ../microcode.ctl.old/debian/templates 2007-05-25 08:09:45.644189280 +0200 +++ debian/templates 2007-06-03 10:09:25.635055234 +0200 @@ -1,14 +1,14 @@ Template: microcode.ctl/check-new Type: boolean Default: true -_Description: Do you want to check online for new Intel CPU microcodes? - microcode.ctl package needs the Intel microcodes to be usefull. +_Description: Download Intel CPU microcodes now? + The microcode.ctl package needs the Intel microcodes for its operation. . - Debian considers these microcode non-free (microcodes are program, but - without sources), so they cannot distributed within this package. + These microcodes are non-free software and cannot distributed + within the package. They can be downloaded from the Internet (the + expected download size is about 300-400Kb). . - The expected internet traffic is about 300-400Kb. - Alternatively, you can check /usr/share/doc/microcode.ctl/README.Debian - and download manually the microcodes or you can also run manually - /usr/sbin/update-intel-microcode . - + If you do not choose to download the microcodes now, please read + /usr/share/doc/microcode.ctl/README.Debian and download the needed + files manually or by running the '/usr/sbin/update-intel-microcode' + command. --- ../microcode.ctl.old/debian/control 2007-05-25 08:09:45.640189246 +0200 +++ debian/control 2007-06-03 10:10:19.132310418 +0200 @@ -11,18 +11,16 @@ Suggests: wget, bzip2 Replaces: microcode-ctl Description: Intel IA32/IA64 CPU Microcode Utility - The microcode_ctl utility is a companion to the IA32 microcode driver - written by Tigran Aivazian <tigran@veritas.com>. The utility has two - uses: + The microcode_ctl utility is a companion to the IA32 microcode + driver. The utility has two uses: . - a) it decodes and sends new microcode to the kernel driver to be - uploaded to Intel IA32 family processors. (Pentium Pro, PII, - Celeron, PIII, Xeon, Pentium 4, etc.) and the Intel x86_64 - family processors - b) it signals the kernel driver to release any buffers it may hold + - decodes and sends new microcode to the kernel driver for Intel IA32 + family (Pentium Pro, PII, Celeron, PIII, Xeon, Pentium 4, etc.) and + Intel x86_64 family processors; + - signals the kernel driver to release any buffers it may hold. . The microcode update is volatile and needs to be uploaded on each - system boot i.e. it doesn't re-flash your CPU permanently, reboot and - it reverts back to the old microcode. The ideal place to load - microcode is in BIOS, but most vendors never update it! - + system boot, i.e. it doesn't re-flash the CPU permanently, reboot and + it reverts back to the old microcode. Ideally, the microcode should be + updated by the computer's BIOS, but most vendors do not implement that + behavior.
Source: microcode.ctl
Section: contrib/utils
Priority: optional
Maintainer: Giacomo Catenazzi <cate@debian.org>
Build-Depends: debhelper (>= 5), po-debconf
Standards-Version: 3.7.2.2
Package: microcode.ctl
Architecture: i386 amd64
Depends: module-init-tools | modutils, udev | makedev (>> 2.3.1-52), po-debconf, ${shlibs:Depends}, ${misc:Depends}
Suggests: wget, bzip2
Replaces: microcode-ctl
Description: Intel IA32/IA64 CPU Microcode Utility
The microcode_ctl utility is a companion to the IA32 microcode
driver. The utility has two uses:
.
- decodes and sends new microcode to the kernel driver for Intel IA32
family (Pentium Pro, PII, Celeron, PIII, Xeon, Pentium 4, etc.) and
Intel x86_64 family processors;
- signals the kernel driver to release any buffers it may hold.
.
The microcode update is volatile and needs to be uploaded on each
system boot, i.e. it doesn't re-flash the CPU permanently, reboot and
it reverts back to the old microcode. Ideally, the microcode should be
updated by the computer's BIOS, but most vendors do not implement that
behavior.
Attachment:
signature.asc
Description: Digital signature