Package Details: lsyncd 2.3.1-9

Git Clone URL: https://aur.archlinux.org/lsyncd.git (read-only, click to copy)
Package Base: lsyncd
Description: Live Syncing (Mirror) Daemon
Upstream URL: https://github.com/lsyncd/lsyncd
Licenses: GPL-2.0-or-later
Submitter: djgera
Maintainer: carsme
Last Packager: carsme
Votes: 67
Popularity: 0.38
First Submitted: 2009-03-25 20:03 (UTC)
Last Updated: 2024-03-03 16:48 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

brauliobo commented on 2024-03-16 20:08 (UTC)

I had to create /etc/lsyncd and /var/log/lsyncd directories, which should have been created by the package?

carsme commented on 2024-01-31 07:34 (UTC)

@la1den Definitely, makes sense to me. Changed in 2.3.1-8.

la1den commented on 2024-01-29 14:27 (UTC)

The ProtectHome option in the lsyncd.service file is enabled by default, which prevents the service from accessing home directories. However, most users may need to sync files within their home directories. Therefore, wouldn't it be better to remove this option?

carsme commented on 2024-01-19 16:42 (UTC)

@flaviut, Great suggestion, fixed in 2.3.1-7. Thanks!

flaviut commented on 2024-01-19 15:09 (UTC)

On my system, I have CMake default to Ninja, so this package doesn't build right. Easy fix though:

diff --git a/PKGBUILD b/PKGBUILD
index 221af70..aa8c4d9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -65,7 +65,7 @@ check() {
   sed --in-place '/exclude-rsyncssh.lua/d' CMakeLists.txt
   sed --in-place '/churn-rsyncssh.lua/d' CMakeLists.txt

-  make -C build run-tests
+  cmake --build build --target run-tests
 }

 package() {

carsme commented on 2024-01-19 09:47 (UTC)

I seem to be mistaken, the tests only take 10 minutes for me, which I think is acceptable. Still, if you have suggestions to reduce the test time, I'm open to hear them :)

carsme commented on 2024-01-19 08:57 (UTC)

@mmlenz, I prefer to run at least some tests to verify the functionality, but I agree that the whole suite takes incredibly long time (~1 hour for me). Do you have any suggestion on how to speed it up? Or, if we were to run a smaller selection of tests, which tests should we skip?

mmlenz commented on 2024-01-17 18:22 (UTC)

These new tests are a bit excessive. They just run and run. Never seen a package take this long to build just running a test suite.

carsme commented on 2023-08-07 17:24 (UTC) (edited on 2023-08-10 06:54 (UTC) by carsme)

Just pushed an update with two significant changes:

  • Running tests.
  • Run the service as a separate user (lsyncd) with some hardening enabled.

There is a risk this is broken for some users or affects some use-cases. Let me know if you experience any problems.

chieltbest commented on 2023-05-06 13:28 (UTC)

It seems the latest commit (3e43094bdfaa) no longer installs lsyncd.service, everything works fine when installed manually though

1 2 3 4 5 6 .. 8 Next › Last »