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.
For more information please consult:
- Prompting in maintainer scripts (Section 3.9.1) in the Debian Policy Manual
The tag is present in Lintian version
That is the most recent version we know about.
We use semantic versions.
The patch number is a commit step indicator relative to the
release tag in our Git
You can find the detection logic for this version at commit 3410a22. For merge requests, please use the latest version in the Lintian check debian/debconf.