public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: man-db-2.11.2-1
Date: Sun, 15 Jan 2023 17:08:23 +0100	[thread overview]
Message-ID: <87ilh76ars.fsf@Rainer.invalid> (raw)
In-Reply-To: <f5by1q327uh.fsf@ecclerig.inf.ed.ac.uk> (Henry S. Thompson via Cygwin's message of "Sun, 15 Jan 2023 14:25:10 +0000")

Henry S. Thompson via Cygwin writes:
> A quick scan of this reveals 86 warnings:
>
>   54 whatis parse for ... failed
>   29 bad symlink or ROFF `.so' request
>    3 is a dangling symlink
>
> Are any of these of any interest to ordinary users, as opposed to
> package maintainers?

THese are warning, not errors.  There are tons of errors and
questionable ROFF constructs in the sources of various man pages, for
better or worse.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

      reply	other threads:[~2023-01-15 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 20:32 Achim Gratz
2023-01-15 14:25 ` Henry S. Thompson
2023-01-15 16:08   ` Achim Gratz [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=87ilh76ars.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).