literally '?' in debconf template

September 28th, 2008 - 04:30 pm ET by markus schnalke | Report spam

Hello mentors,

lintian reports this warning:
using-question-in-extended-description-in-templates
(see [1])

But there is no question where lintian sees one. Instead it's a
literally question mark. The text is:
"You can use wildcard expressions like '*' or '?'."

How can I solve the situation?
Is there a way to escape the questions mark?
Do I have to override the warning?


meillo


References:
[1] http://lintian.debian.org/tags/usin...lates.html





To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 4 repliesReplies Make a reply

Replies

#1 markus schnalke
September 28th, 2008 - 06:10 pm ET | Report spam

[2008-09-28 22:16] Stephen Gran
This one time, at band camp, George Danchev said:
> On Sunday 28 September 2008 22:08:28 markus schnalke wrote:
>
> > lintian reports this warning:
> > using-question-in-extended-description-in-templates
> > (see [1])
> >
> > But there is no question where lintian sees one. Instead it's a
> > literally question mark. The text is:
> > "You can use wildcard expressions like '*' or '?'."
> >
> > How can I solve the situation?
> > Is there a way to escape the questions mark?
> > Do I have to override the warning?
>
> Well, lintian did his job right to warn you about a possible problem, but it
> can't sense the context (at least as of yet;-), thus you can safely override
> his decision.



I did so. (For the moment.)



Or you could file a wishlist bug with a patch something like:
a/checks/debconf
+++ b/checks/debconf
@@ -312,7 +312,7 @@ foreach my $template (@templates) {
tag "malformed-question-in-templates", $template->{template};
}
}
- if (defined ($extended) && $extended =~ /\?/) {
+ if (defined ($extended) && $extended =~ /\?(\s+|$)/) {
tag "using-question-in-extended-description-in-templates", $template->{template};
}
if ($type eq 'note') {

To help eliminate false positives in tests.



Good suggestion ... and the patch (which seems to be good) already
included ;-)

I'll file the bug tomorrow (if nobody else did it till then)
... now I've really to go to bedit's much too late ;-)


meillo





To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics