Package Details: rslsync 2.5.12-1

Git Clone URL: (read-only)
Package Base: rslsync
Description: Resilio Sync (ex:BitTorrent Sync) - automatically sync files via secure, distributed technology
Upstream URL:
Licenses: custom:resilio
Submitter: widowild
Maintainer: widowild (fryfrog)
Last Packager: fryfrog
Votes: 340
Popularity: 0.626527
First Submitted: 2016-09-25 13:20
Last Updated: 2018-01-11 18:05

Dependencies (0)

Required by (0)

Sources (5)

Latest Comments

widowild commented on 2018-01-11 17:45


  • Fixed inability to auto-update Sync

fryfrog commented on 2018-01-03 17:08

If you're still seeing checksum failures, have you deleted the previously downloaded file and re-downloaded?

EarthMind commented on 2018-01-03 06:49

Update: it seems to work now after the current try. Thanks for your help though

fryfrog commented on 2018-01-02 16:49

The package sums were fixed way back on 12/21 when @TamasBarta and @mart-e mentioned it. I just double checked and they haven't changed again. What error are you seeing?

EarthMind commented on 2018-01-02 12:37

I'm having that issue also

mart-e commented on 2017-12-21 14:33

Same here, the sha256sum for the x86_64 is 9938c2ecb8f9c6a49f322e02730bdb4efee165627bc6dea9ba0f60dbc7058bf0 Possible that there is a new version released?

TamasBarta commented on 2017-12-21 12:00


When trying to upgrade, validity check fails, I get the following output:

==> Validating source files with sha256sums...
    rslsync.service ... Passed
    rslsync_user.service ... Passed
    rslsync.conf ... Passed
==> Validating source_x86_64 files with sha256sums...
    rslsync_x64-2.5.10.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

This is only on one of my machines, but between upgrading the two, some days passed, it is possible, that the resource file changed.

widowild commented on 2017-12-19 12:38

2.5.10 - Fixed crash when syncing encrypted folders - Improved saving configuration on exiting - Minor improvements and fixes

EarthMind commented on 2017-09-27 17:16

Hi fryfrog

That was my initial post yes. But what I misunderstood was that the PGP signatures are for the .deb and .rpm packages. The tar archives aren't signed in any way nor any separate signature file is available for those.

I edited my post shortly after realizing this.

Thank you for the update too

fryfrog commented on 2017-09-26 18:03

@EarthMind, can you point at an example of using PGP signatures in a AUR package? All the ones I manage and have looked at use md5/sha. And of them, rslsync is the only one that changes the package hash w/o changing the version. :/

"Why don't you do the verification the proper way, that is by verifying
the PGP signature instead of adding file checksums, which as far as I
know, are not provided by Resilio themselves?"

Also, for some reason I can see the above in my email, but not your comment. :/

All comments