From: Wayne Davison <wayne@opencoder.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: There is no man for rsync
Date: Wed, 17 Jun 2020 12:09:58 -0700 [thread overview]
Message-ID: <CAHSx_SvGFQovN6eJYOv1bQc8ME169UZNvzf60XP0KmnipVFeMg@mail.gmail.com> (raw)
In-Reply-To: <fb4cc5de-25ae-4c12-920b-88f753160cb2@SystematicSw.ab.ca>
On Tue, Jun 2, 2020 at 12:36 PM Brian Inglis wrote:
> Looks like a packaging problem as the man dirs are created but not populated:
What undoubtedly happened was that the git checkout used for the
release does not include pre-generated man pages, and the build
required the yodl document processor to create them. At the time the
configure & make would have just mentioned that it wasn't able to
build the manpages, but the build would not have failed, making that
issue easy to miss. (And the "./prepare-source fetchgen" command would
not have worked since samba.org switched over to requiring ssl for the
rsync daemon copy commands and the script wasn't fixed to handle that
yet.)
In the upcoming 3.2.0 release the man page source files have changed
from .yo files to .md files, their build process only requires python3
and python3-commonmark (which Cygwin has), and the configure & make
rules now fail if there are no man pages and no way to build them.
This should hopefully mean that the issue won't recur should another
git release be needed in the future.
On the subject of the pending 3.2.0 release, it would be nice to get
the xxHash library turned into normal & dev packages so that the
Cygwin rsync can ship with xxhash checksum support. I've installed
xxHash manually for testing and it's working fine (and I just got the
project to fix a Cygwin install issue in the Makefile). For anyone
wanting to test it manually, you can grab the latest git or zip file
from github (https://github.com/Cyan4973/xxHash) and run "PREFIX=/usr
make install". If nobody else gets around to it I'll see what I can do
once I get done with the rsync release process.
..wayne..
prev parent reply other threads:[~2020-06-17 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:13 Vlado
2020-06-02 19:36 ` Brian Inglis
2020-06-17 19:09 ` Wayne Davison [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=CAHSx_SvGFQovN6eJYOv1bQc8ME169UZNvzf60XP0KmnipVFeMg@mail.gmail.com \
--to=wayne@opencoder.net \
--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).