From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: broken links on few man pages : xmon, mysql, bind-utils
Date: Sat, 16 Aug 2014 17:06:00 -0000 [thread overview]
Message-ID: <53EF8FA6.2000206@gmail.com> (raw)
Hi,
just as by product of looking why mc had a unusable man page,
and why u2d was making me crazy...
these are the other broken pages on my system, that look as
upstream bugs.
$ grep ROFF mandb.log
mandb: warning: /usr/share/man/man1/bind9-config.1.gz: bad symlink or
ROFF `.so' request
mandb: warning: /usr/share/man/man1/mysqltest_embedded.1.gz: bad symlink
or ROFF `.so' request
mandb: warning: /usr/share/man/man1/mysql_client_test_embedded.1.gz: bad
symlink or ROFF `.so' request
mandb: warning: /usr/share/man/man1/u2d.1.gz: bad symlink or ROFF `.so'
request
mandb: warning: /usr/share/man/man1/xmond.1.gz: bad symlink or ROFF
`.so' request
$ cygcheck -f /usr/share/man/man1/bind9-config.1.gz
bind-utils-9.9.5-3
$ gzip -cd /usr/share/man/man1/bind9-config.1.gz
.so isc-config.sh.1
but there is no isc-config.sh.1 page in any cygwin package
$ cygcheck -f /usr/share/man/man1/mysqltest_embedded.1.gz
mysql-5.5.35-1
$ gzip -cd /usr/share/man/man1/mysqltest_embedded.1.gz
.so man-gpl-tmp2/mysqltest.1
$ gzip -cd /usr/share/man/man1/mysqltest_embedded.1.gz
.so man-gpl-tmp2/mysqltest.1
but the file is located on /usr/share/man/man1/mysqltest.1.gz
$ cygcheck -f /usr/share/man/man1/xmond.1.gz
xmon-1.5.6-3
$ gzip -cd /usr/share/man/man1/xmond.1.gz
.so man1/xmonui.1x
so there is an extra "x" as the page is
/usr/share/man/man1/xmonui.1.gz
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2014-08-16 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EF8FA6.2000206@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).