Description of problem: lsyncd version 2.0.7 is available, which offers feature enhancements and bug fixes from 2.0.4, including inotify support. How reproducible: Steps to Reproduce: 1. Install lsyncd 2. Notice version Actual results: lsyncd is installed, without inotify support Expected results: lsyncd is installed with inotify support Additional info: Updated .spec and SOURCE files attached.
Created attachment 624260 [details] spec file for lsyncd-2.0.7
Created attachment 624261 [details] sysvinit script for lsyncd
Created attachment 624263 [details] /etc/sysconfig/lsyncd for lsyncd-2.0.7
Created attachment 624264 [details] systemd service unit for lsyncd-2.0.7 First try at writing service units, as I would like to ultimately see lsyncd-2.0.7 on CentOS 5/6 .
One concern is that by default, the configuration file /etc/lsyncd.conf does not exist, and the service fails to start. However, since this package is intended to be manually configured in some way to accomplish its goal, I think this is okay.
I'm unable to change "See Also", so see also https://bugzilla.redhat.com/show_bug.cgi?id=805849
Created attachment 625341 [details] Enhanced spec with conditionals on systemd vs sysvinit
Created attachment 625342 [details] Updated sysvinit that checks for config file
Created attachment 625343 [details] Updated service unit, removes erroneous ExecReload
lsyncd 2.1.1 is now available. I'm willing to take over maintainership of this package, by the way.
lsyncd 2.1.2 is out. If someone could update this, I would be pretty happy.
Created attachment 649455 [details] Updated spec to 2.1.2 Adapted spec from updated version at https://github.com/repoforge/rpms/pull/213
Created attachment 649456 [details] Logrotate file for lsyncd.log
2.1.3 is available, but a new version should be released this weekend see https://github.com/axkibe/lsyncd/issues/170#issuecomment-10662741 Don't know, but maybe just skip this one. btw: why is the systemd unit file for F19+ only?
Created attachment 650554 [details] Updated spec to 2.1.3 Updated version to 2.1.3, and changed systemd >= Fedora 15.
Created attachment 650584 [details] Updated spec to 2.1.3 Fix comment
Created attachment 654490 [details] Updated spec to 2.1.4
I requested co-maintainer ship
Nirik asked me to raise cvs on this so someone with time can give me co-maintainership while Lubomir Rintel's pacakges are in limbo See also: http://lists.fedoraproject.org/pipermail/devel/2012-October/172007.html
Done.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19