From: Ingo Schwarze <schwarze@usta.de>
To: Abigail G <dev@kb6.ee>
Cc: discuss@mandoc.bsd.lv
Subject: Re: man.cgi doesn't find symlinked manpages
Date: Sat, 9 Apr 2022 20:18:32 +0200 [thread overview]
Message-ID: <YlHN+A1xwqIw07p8@asta-kit.de> (raw)
In-Reply-To: <a00315e04c6ed19c7aa96f1f4ee408a5ee8fd72a.camel@kb6.ee>
Helli Abigail,
Abigail G wrote on Sat, Apr 09, 2022 at 11:59:03AM -0400:
> Looks like there was an issue with the fix for our binary package
> repository to manpage database/file-tree program that caused symlinks
> not to be written. With that fixed, looking up symlinked manpages works
> fine.
Heh, no wonder i scratched my head trying to figure out what the problem
might be.
I'm glad to learn nothing is broken in man.cgi(8) in this respect.
> Thanks for the troubleshooting tips!
You are very welcome!
Do stay in contact and don't hesitate to tell us about your
experience with mandoc and man.cgi on your servers. I guess sooner
or later, you will run into something that can be improved on the
mandoc side, whatever it may then turn out to be.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2022-04-09 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 17:25 Abigail G
2022-04-08 15:49 ` Ingo Schwarze
2022-04-09 15:59 ` Abigail G
2022-04-09 18:18 ` Ingo Schwarze [this message]
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=YlHN+A1xwqIw07p8@asta-kit.de \
--to=schwarze@usta.de \
--cc=dev@kb6.ee \
--cc=discuss@mandoc.bsd.lv \
/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 NNTP newsgroup(s).