As of rsync 2.6.7 the meaning of the option --devices changed in that it doesn't include preserving "special" files any more. As a consequence it get following error messages in my rsync mirror log file: ----------------------------snip----------------------------- Started update at Wed Jan 17 03:10:01 CET 2007 rsync: on remote machine: --no-specials: unknown option rsync error: requested action not supported (code 4) at clientserver.c(520) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(604) [receiver=2.6.9] End: Wed Jan 17 03:10:49 CET 2007 ----------------------------snap----------------------------- Adding the option "--specials" to the OPTS-Variable in "/etc/rsync/gentoo-mirror.conf" fixed the problem. I also attached the changed gentoo-mirror.conf-file. Reproducible: Always Steps to Reproduce: 1. Executing /opt/gentoo-rsync/rsync-gentoo-portage.sh Actual Results: No syncing of the gentoo portage tree any more. Error message see description Expected Results: Syncing of the gentoo portage tree
Created attachment 135947 [details] New conf file fixing the problem Just added --special to the list of options passed to rsync (OPTS-variable)
Created attachment 135949 [details, diff] The same as a patch file
*** Bug 146274 has been marked as a duplicate of this bug. ***
Assigning to new maintainers.
Hello RGK. Do you still proxy maintain this package? Do you think this is fixable or whether it is a candidate for being cleaned from the Portage tree? Thank you very much in advance.
ping maintainer.. also got this warning, it would be great if we can fix all bugs and stabilize new version, many thanks RepoMan scours the neighborhood... >>> Creating Manifest for /home/gentoo/gentoo-x86/app-admin/gentoo-rsync-mirror repo.eapi.deprecated 1 app-admin/gentoo-rsync-mirror/gentoo-rsync-mirror-1.0-r4.ebuild: 0
commit d59a2174f4da6b9d900c88cf714b418bb6afff92 Author: Amy Liffey <amynka@gentoo.org> Date: Mon Feb 27 15:48:20 2017 +0100 app-admin/gentoo-rsync-mirror: fix config bug #199128 Sumbitted-by: Alois Schmid