Re: pkg/29328: lintpkgsrc/pkg_info doesn't tell me which packages are missing +COMMENT

[Timothy Lee Roden <diro%nixsys.bz@localhost>]

The following reply was made to PR pkg/29328; it has been noted by GNATS.

From: Timothy Lee Roden <diro%nixsys.bz@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: rquinn%sec.sprint.net@localhost, pkg-manager%netbsd.org@localhost
Subject: Re: pkg/29328: lintpkgsrc/pkg_info doesn't tell me which packages are 
missing +COMMENT
Date: Tue, 22 Feb 2005 10:24:02 -0500

 I'm seeing a similar problem on NetBSD/alpha 1.6.2 with current-pkgsrc. This 
has been going on for a bit and I've not been able to determine the cause. It 
seems when certain pkgs are installed, +COMMENT is not entered into the pkg 
database. Also, on the daily security output, one may find:
 
 < ruby18-rdtool-0.6.14 p5-XML-LibXML-1.57nb2 Perl interface to the libxml2
 +library 
 ---
 > ruby18-rdtool-0.6.14 p5-perl-ldap-0.30nb2 Perl class to access LDAP servers
 1193c1192
 
 Wherein (something similar):
 
 % pkg_info -I ruby16
 pkg_info: show_file: can't open '+COMMENT' for reading
 ruby16-1.6.8nb1     
 
 This behavior seems to have almost gone away. I once had almost 50 pkgs with 
unregistered COMMENTS, but now have it down to only one pkg with a missing 
entry.
 
 If you update to pkgsrc-current, you may find this behavior to go away. 
However, this doesn't address the PR, which suggests lintpkgsrc/pkg_info should 
report which pkgs are missing a COMMENT. The request seems (to me at least) to 
be out of the jurisdiction of lintpkgsrc and as for pkg_info...the request 
seems useful to have, but shouldn't happen in the first place, as COMMENT 
should be written to the pkg database.
 
 !tr