Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3690 - namcap should not run checks on comments
Attached to Project:
Arch Linux
Opened by Alexander Baldeck (kth5) - Monday, 02 January 2006, 16:19 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 25 March 2006, 23:10 GMT
Opened by Alexander Baldeck (kth5) - Monday, 02 January 2006, 16:19 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 25 March 2006, 23:10 GMT
|
Detailsnamcap runs checks against what is commented in a PKGBUILD as well, resulting in confusing messages like this one:
"PKGBUILD (e2fsprogs) W: Reference to i686 should be changed to $CARCH" when the maintainer line contains something like this: "# i686 Maintainer: judd <jvinet@zeroflux.org>" i suggest to not have namcap run any checks on comments at all except for the maintainer lines maybe. which reminds me that the $CARCH in front of the actual keyword "Maintainer" makes it possible to give credit to the original authors in a port w/o the compromise to accept this one warning all the time. example e2fsprogs PKGBUILD: http://cvs.archlinuxppc.org/viewcvs/base/e2fsprogs/PKGBUILD?rev=1.4&content-type=text/vnd.viewcvs-markup |
This task depends upon
Closed by Jason Chu (jason)
Wednesday, 02 August 2006, 06:16 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in the last release.
Wednesday, 02 August 2006, 06:16 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in the last release.