Lintian Reports

W possible-debconf-note-abuse

All reports of possible-debconf-note-abuse for the archive. The extended description of this tag is:

Debconf notes should be used only for important notes that the user really should see, since debconf will go to great pains to make sure the user sees it.

Displaying a note with a low priority is conflicting with this statement, since using a low or medium priority shows that the note is not important.

The right fix is NOT to increase the priority of the note, but to move it somewhere else in the inline documentation, for example in a README.Debian file for notes about package usability or NEWS.Debian for changes in the package behavior, or to simply drop it if it is not needed (e.g. "welcome" notes). Changing the templates type to "error" can also be appropriate, such as for input validation errors.

Refer to Debian Policy Manual section 3.9.1 (Prompting in maintainer scripts) for details.

Severity: normal, Certainty: possible

Check: debconf, Type: binary, udeb, source

Evolution of the possible-debconf-note-abuse Lintian tag over the past 366 days:

The beforementioned graph for the possible-debconf-note-abuse tag

Emitted (non-overridden): 8, overridden: 3, total: 11

The package names link to the relevant maintainer page and the corresponding report for the source package. The links go to the full maintainer report page, which includes info and experimental tags and overridden tags, rather than the default page that shows only errors and warnings.

cdrom-detect 1.73 (udeb)

checksecurity 2.0.16+nmu1 (binary)

iso-scan 1.61 (udeb)

lilo-installer 1.54 (udeb)

prey 0.6.2-1.1 (binary)

resolvconf 1.79 (binary) overridden

snort 2.9.7.0-5 (binary)

snort 2.9.7.0-5+b1 (binary)

tiger 1:3.2.3-14.3 (binary) overridden