Description of problem: "man man" and "man apropos" show incorrectly formatted pages, full of what look like unexpanded keywords (words surrounded by percent symbols). Version-Release number of selected component (if applicable): man-pages-3.69-5.fc21.noarch man-db-2.6.7.1-16.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. man man 2. 3. Actual results: %thman%(1) Manual pager utils %thman%(1) NAME %man% - an interface to the on-line reference manuals ... Expected results: MAN(1) Manual pager utils MAN(1) NAME man - an interface to the on-line reference manuals ... Additional info: The man page for apropos is similarly formatted. LANG=en_US.UTF-8 TERM=xterm Viewed via PuTTY 0.65 (with UTF-8 set) (By the way, shouldn't the title say "Manual page utils" instead of "Manual pager utils"? I noticed that on F22 as well.)
Looks similar to #1231568, only this time for F21. The title is intentionally "Manual pager utils", and has been that way ever since before I took on upstream maintenance; it's an agent noun construction, i.e. "manual pager" -> "thing that shows manual pages".
(In reply to Colin Watson from comment #1) > Looks similar to #1231568, only this time for F21. Yes, exactly the same problem. Unfortunately I'm unable to find the cause. Rebuilding the package always fixes it, even when I try to emulate the same conditions as with the faulty build.
http://git.savannah.gnu.org/cgit/man-db.git/commit/?id=32ee575a45d3a7e221a7b29c457049b659315152
man-db-2.6.7.1-18.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16443
man-db-2.7.1-9.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16445
man-db-2.7.1-10.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16446
(In reply to Nikola Forró from comment #2) > Unfortunately I'm unable to find the cause. Building in Koji with high number of parallel make jobs sometimes caused this. (In reply to Colin Watson from comment #3) > http://git.savannah.gnu.org/cgit/man-db.git/commit/ > ?id=32ee575a45d3a7e221a7b29c457049b659315152 Thanks Colin. f21: http://pkgs.fedoraproject.org/cgit/man-db.git/commit/?h=f21&id=3a284cdb53f09350bd0ecd40cb6ec36dbc9e352a f22: http://pkgs.fedoraproject.org/cgit/man-db.git/commit/?h=f22&id=bd6192c5def4b28dec644319f68fab53fb717cc9 f23: http://pkgs.fedoraproject.org/cgit/man-db.git/commit/?h=f23&id=caa5c4542c993c8abaf95f0a9cbf74980c03737c master: http://pkgs.fedoraproject.org/cgit/man-db.git/commit/?id=0d6c9fa70b1bdaf62a3786ee117711d3fac06f6a
man-db-2.7.1-10.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update man-db' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16446
man-db-2.6.7.1-18.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update man-db' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16443
man-db-2.7.1-9.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update man-db' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16445
man-db-2.7.1-10.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
man-db-2.7.1-9.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
man-db-2.6.7.1-18.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.