Description of problem: The man page rsyncd.conf(5) is referenced in rsync(1) serveral times. It is particularly necessary because of its "log format" section for using rsync with --out-format. Version-Release number of selected component (if applicable): 3.1.2-3.fc25 How reproducible: always Steps to Reproduce: 1. run "man rsync" 2. read about "--out-format" 3. try "man rsyncd.conf" Actual results: rsyncd.conf man page not found Expected results: rsyncd.conf man page Additional info: I admit that it's simple and quick to just install rsync-daemon, since it's small and noarch. But one may not always have an internet connection or be able to install packages, and rsync-daemon is merely a convenience package, as you can run rsync as daemon just fine without it.
Perhaps we could just add the detailed description of --out-format from rsyncd.conf man page to the rsync man page? I will consult this with the upstream.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still in rsync-3.1.2-7.fc27.x86_64
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
not changed in rsync-3.1.3-4.fc29.x86_64
+1 to original request. rsyncd.conf should be documented fully in the rsync package, because it can be used manually as described in `man rsync`, "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION". I actually I think it would be better if there was not any separate rsync-daemon package. Note that systemd services are *not* enabled by default in Fedora. If the specific service is not listed in a systemd preset file, then it will only be enabled if the user takes some action to do so.
*** Bug 1699511 has been marked as a duplicate of this bug. ***
Sorry, this bug kind of fell into my backlog and I forgot about it. I agree and I will fix it now.
(In reply to Alan Jenkins from comment #6) > +1 to original request. rsyncd.conf should be documented fully in the rsync > package, because it can be used manually as described in `man rsync`, "USING > RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION". > > I actually I think it would be better if there was not any separate > rsync-daemon package. Note that systemd services are *not* enabled by > default in Fedora. If the specific service is not listed in a systemd > preset file, then it will only be enabled if the user takes some action to > do so. Hi Alan, the rsync-daemon was split from the main package because to run it as a daemon, it needed systemd(specifically systemd-units but that is part of systemd for a long time now). But because systemd is not in the minimal installation, only systemd-libs AFAIK, the split helped reduce dependencies when installing rsync. Also, when running rsync in a container for example, usually I think you might not want it to install systemd. So the split makes sense to me.
rsync-3.1.3-7.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4cf347baed
rsync-3.1.3-8.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-afd63cb5d4
rsync-3.1.3-8.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-afd63cb5d4
rsync-3.1.3-7.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4cf347baed
Oh, that sounds reasonable. Thanks for the fix :-).
rsync-3.1.3-7.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
rsync-3.1.3-8.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.