Red Hat Bugzilla – Bug 589432
[RFE] rpmlint could warn about the syntax problems in man-pages
Last modified: 2010-06-04 14:46:33 EDT
Description of problem: From f14 there is new version of groff (1.20) and new version of man pages reader man-db package which is able to produce the list of bugs in syntax for given man-page. e.g. $ man --warnings /usr/share/man/man1/gm.1.gz >/dev/null <standard input>:1301: warning: macro `unsigned'' not defined <standard input>:5345: warning: macro `-resize' not defined <standard input>:5347: warning: macro `+profile' not defined This could be automatically tested in rpmlint.
Can this be tested in a backwards compatible manner, for example directly with groff? man --warnings cannot be used with man 1.6f.
To clarify, backwards compatible manner doesn't necessarily have to mean that the tests would produce warnings with some earlier versions of man/groff (they could just fail silently), but it'd be nice to not have to introduce a config parameter to turn this feature on/off.
There seems to be a way how to use groff directly (nroff in groff 1.18 can't be used).
Sounds good, could you post the info how to do it directly with groff here when you find it out?
eg. if you want to check man page: /usr/share/man/man1/bash.1.gz you can use command /usr/bin/gunzip -c '/usr/share/man/man1/bash.1.gz' | /usr/bin/gtbl | groff -mtty-char -Tutf8 -P-c -mandoc -mandoc -wmac >/dev/null output the same level of warnings as man --warnings bash
Done upstream, will most likely be in the next release: http://rpmlint.zarb.org/cgi-bin/trac.cgi/changeset/1780
rpmlint-0.97-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/rpmlint-0.97-1.fc13
rpmlint-0.97-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/rpmlint-0.97-1.fc12
rpmlint-0.97-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
rpmlint-0.97-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.