Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1600386 (FedoraManpagescan)
Created attachment 1458273 [details]
Error/warning explanation.
So, just to note here: Filing this will not cause any developers to do anything. :) I do see you have this listed as a tracking bug, do you intend then to run the script over the fedora packages collection and file bugs? If so, do see: https://fedoraproject.org/wiki/Mass_package_changes Let me know if I can help any further... (In reply to Kevin Fenzi from comment #3) > So, just to note here: Filing this will not cause any developers to do > anything. :) > > I do see you have this listed as a tracking bug, do you intend then to run > the script over the fedora packages collection and file bugs? If so, do see: > https://fedoraproject.org/wiki/Mass_package_changes > > Let me know if I can help any further... Hi Kevin, Yes, this is a tracking bug and I'm going to inform people via devel-announce list about future reports to be done here. The requirement of qa-tools makes it unusable for any external contributor. Also the license of the script is not specified. Providing the script as an attachment in bugzilla is not very user-friendly. Maybe consider at least making a repo with it somewhere that one can git-clone easily. Hi Maryna, Either I'm doing something very wrong, or you've forgotten to provide the attachments… (In reply to Maryna Nalbandian from comment #0) > Here is the simple process of man page check: > > 1. Run the script (you can find it in attachments): > $ ./man-page-day.sh ${component} > > 2. For more information, please check README.md. You also mentioned these files in your message to devel-announce, but the only attachment I could see was fedora_BZ: > Please take a look at the bug tracker[1] and also please have a look at > the attached! There are 2 files: > > man-page-day.sh > README.md I googled the script's name, but that got me to an expired RH URL: http://download.eng.brq.redhat.com/archive/RHELManPageCheck/man-page-day.sh Anyway, I checked fedora_BZ for any of the packages I maintain and I saw all of the gdouros-* fonts. For as long as I've been the POC for these packages, the fonts have always been provided as TrueType Fonts, without any source. Why would they need man pages? I now looked at three bugs for packages which I own. They were all bogus. Looking at other bugs, they *all* get closed as NOTABUG. It seems that the script grossly misdetects issues. This is wasting developer time. Please stop filing mass bugs like that. You need to work on the script to have a higher sound/noise ratio *and* improve the legibility of the output first. |
Description of problem: In order to improve usability of packages in Fedora, project Man Page Scan was created and its task is to provide consistency of man pages (and documentation in general). The results are now available for package maintainers to fix documentation issues. Here is the simple process of man page check: 1. Run the script (you can find it in attachments): $ ./man-page-day.sh ${component} 2. For more information, please check README.md.