Package: memtest86+
Version: 4.00-2
Severity: serious
User: [email protected]
Usertags: read-in-maintainer-script
This maintainer script appears to use read to get information from the
user. Prompting in maintainer scripts must be done by communicating through a
program such as debconf which conforms to the Debian Configuration management
specification, version 2 or higher.
Refer to Debian Policy Manual section 3.9.1 (Prompting in maintainer scripts)
for details.
,----[ 3.9.1 Prompting in maintainer scripts ]
| Package maintainer scripts may prompt the user if necessary. Prompting must be
| done by communicating through a program, such as debconf, which conforms to
the
| Debian Configuration Management Specification, version 2 or higher.
|
| Packages which are essential, or which are dependencies of essential packages,
| may fall back on another prompting method if no such interface is available
when
| they are executed.
|
| The Debian Configuration Management Specification is included in the
| debconf_specification files in the debian-policy package.
`----
manoj
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
memtest86+ depends on no packages.
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub2 1.97-1 GRand Unified Bootloader, version
pn hwtools <none> (no description available)
pn kernel-patch-badram <none> (no description available)
ii memtest86 3.5-2 thorough real-mode memory tester
pn memtester <none> (no description available)
ii mtools 4.0.10-1 Tools for manipulating MSDOS files
-- no debconf information
-- debsums errors found:
debsums: missing file /boot/memtest86+.bin (from memtest86+ package)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
