NetBSD Problem Report #51709

From dholland@netbsd.org  Sun Dec 11 20:11:51 2016
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 8B9937A33A
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 11 Dec 2016 20:11:51 +0000 (UTC)
Message-Id: <20161211201151.43D1F8557B@mail.netbsd.org>
Date: Sun, 11 Dec 2016 20:11:51 +0000 (UTC)
From: dholland@NetBSD.org
Reply-To: dholland@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: pkglint should detect | in COMMENT
X-Send-Pr-Version: 3.95

>Number:         51709
>Category:       pkg
>Synopsis:       pkglint should detect | in COMMENT
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    rillig
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Dec 11 20:15:00 +0000 2016
>Closed-Date:    Sun Nov 25 23:21:48 +0000 2018
>Last-Modified:  Sun Nov 25 23:21:48 +0000 2018
>Originator:     David A. Holland
>Release:        pkglint 5.4.11
>Organization:
>Environment:
n/a
>Description:

As seen in PR 51696, vertical bar characters in COMMENT cause
problems; it would be nice if pkglint could warn about this.

(also, as also seen in PR 51696, the presence of a # on that line is
probably an error rather than a comment and it might be worth trying
to diagnose that too; but that could be problematic)

>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: pkg-manager->rillig
Responsible-Changed-By: wiz@NetBSD.org
Responsible-Changed-When: Sun, 11 Dec 2016 23:34:41 +0000
Responsible-Changed-Why:
Over to maintainer.


State-Changed-From-To: open->feedback
State-Changed-By: rillig@NetBSD.org
State-Changed-When: Tue, 13 Dec 2016 01:12:15 +0000
State-Changed-Why:

The warning for # has been added in pkglint 5.4.13.
The warning for | has not been implemented, as I think
it would be more appropriate to fix the index generation
program so that it can handle all printable ASCII
characters.

But if you really insist, I can provide the warning
within pkglint.


Responsible-Changed-From-To: rillig->dholland
Responsible-Changed-By: rillig@NetBSD.org
Responsible-Changed-When: Tue, 13 Dec 2016 01:12:42 +0000
Responsible-Changed-Why:


Responsible-Changed-From-To: dholland->rillig
Responsible-Changed-By: dholland@NetBSD.org
Responsible-Changed-When: Sun, 25 Nov 2018 23:21:48 +0000
Responsible-Changed-Why:
not sure why you set this to me


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 25 Nov 2018 23:21:48 +0000
State-Changed-Why:
fixed enough
(arguably pkglint ought to warn about | until the index generator is fixed,
but whatever)


>Unformatted:

Home	PR Database Search