summaryrefslogtreecommitdiffstats
path: root/tags/p/possible-debconf-note-abuse.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/p/possible-debconf-note-abuse.tag')
-rw-r--r--tags/p/possible-debconf-note-abuse.tag18
1 files changed, 18 insertions, 0 deletions
diff --git a/tags/p/possible-debconf-note-abuse.tag b/tags/p/possible-debconf-note-abuse.tag
new file mode 100644
index 0000000..4064d49
--- /dev/null
+++ b/tags/p/possible-debconf-note-abuse.tag
@@ -0,0 +1,18 @@
+Tag: possible-debconf-note-abuse
+Severity: warning
+Check: debian/debconf
+Explanation: 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.
+See-Also: debian-policy 3.9.1