From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: There is no man for rsync
Date: Tue, 2 Jun 2020 13:36:43 -0600 [thread overview]
Message-ID: <fb4cc5de-25ae-4c12-920b-88f753160cb2@SystematicSw.ab.ca> (raw)
In-Reply-To: <dd1cacb7-20b4-6ad1-a843-ba3012b6b5da@gmail.com>
On 2020-06-01 03:13, Vlado via Cygwin wrote:
> Hello, rsync maintainer!
>
> Package rsync 3.1.3+20200429+gitf7746d0-1 is offered by setup as best choice,
> but this package has no manual pages inside.
> Consider to rebuild rsync 3.1.3 package, please. (nothing urgent, 3.1.2-1 works
> fine for me)
Looks like a packaging problem as the man dirs are created but not populated:
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Frsync%2Frsync-3.1.3%2B20200429%2Bgitf7746d0-1&grep=rsync
2020-05-05 12:11 0 usr/share/man/
2020-05-05 12:11 0 usr/share/man/man1/
2020-05-05 12:11 0 usr/share/man/man5/
but the previous releases include the man pages:
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Frsync%2Frsync-3.1.2-1&grep=rsync
2016-01-29 06:33 57288 usr/share/man/man1/rsync.1.gz
2016-01-29 06:33 16128 usr/share/man/man5/rsyncd.conf.5.gz
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Frsync%2Frsync-3.1.1-1&grep=rsync
2015-02-13 17:13 57154 usr/share/man/man1/rsync.1.gz
2015-02-13 17:13 16029 usr/share/man/man5/rsyncd.conf.5.gz
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-06-02 19:36 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 [this message]
2020-06-17 19:09 ` Wayne Davison
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=fb4cc5de-25ae-4c12-920b-88f753160cb2@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).