Package Details: syncthing-bin 1.20.2-1

Git Clone URL: (read-only, click to copy)
Package Base: syncthing-bin
Description: Open Source Continuous Replication / Cluster Synchronization Thing: binary.
Upstream URL:
Licenses: MPLv2
Conflicts: syncthing
Provides: syncthing
Submitter: jasonwryan
Maintainer: jasonwryan
Last Packager: jasonwryan
Votes: 29
Popularity: 0.160044
First Submitted: 2014-08-26 08:54 (UTC)
Last Updated: 2022-06-07 20:51 (UTC)

Dependencies (0)

Required by (6)

Sources (2)

Pinned Comments

jasonwryan commented on 2019-06-03 01:41 (UTC)

Jakob generally takes a day or two to upload the hash file after each release. Please don't flag the package out-of-date until after he has published that file...

Latest Comments

jasonwryan commented on 2021-08-03 21:13 (UTC)

@bt90 - I'll add them to the next release. Thanks!

bt90 commented on 2021-08-03 18:45 (UTC) (edited on 2021-08-03 18:51 (UTC) by bt90)

Can we also package the upstream sysctl config file?

    install -D -m 644 "etc/linux-sysctl/30-${_realname}.conf" \

Edit: maybe also the ufw preset?

    install -D -m 644 "etc/firewall-ufw/${_realname}" \

jasonwryan commented on 2021-07-26 15:59 (UTC)

@jonathon - this has been discussed on aur-general: this package is for those of us that don't want to install go for one package.

SanskritFritz commented on 2021-07-26 15:58 (UTC)

This package proved to be very useful for me, I'm still using it, as this seems to be more stable than the compiled one in the repos:

crox commented on 2021-07-26 14:35 (UTC)

The syncthing package in community is a recent inclusion. This AUR package existed as a way to install the binary distribution from upstream directly. I guess now that syncthing is in community this package is less useful, provided that the repo version is kept up to date. At this time, the package in community is one version behind upstream.

jonathon commented on 2021-07-26 14:18 (UTC)

What does this package provide that's different to syncthing in community?

From, "The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances... Exception to this strict rule may only be packages having extra features enabled and/or patches in comparison to the official ones."

rakhesh commented on 2020-09-19 11:35 (UTC)

Update to the case statement in PKGBUILD to support ARM64 (tested this on a Raspberry Pi4 running Manjaro aarch64).

        aarch64) _pkgarch="arm64"


GeoffreyFrogeye commented on 2020-09-11 18:39 (UTC)

It seems you used the SHA256 sum of the arm64 archive for 1.9.0. I'm pretty sure it used to be the sum of the arm archive.

jasonwryan commented on 2019-11-09 19:10 (UTC) (edited on 2019-11-09 19:11 (UTC) by jasonwryan)

@canton7 You can write a drop in file to add that line. I don't want to patch the upstream file.

canton7 commented on 2019-11-09 11:38 (UTC)

Can I suggest adding Environment=STNOUPGRADE=1 to the systemd unit file?

Currently it tries to auto-update, which will fail because it doesn't have filesystem permissions.

jasonwryan commented on 2019-06-03 01:41 (UTC)

Jakob generally takes a day or two to upload the hash file after each release. Please don't flag the package out-of-date until after he has published that file...

jasonwryan commented on 2016-12-19 20:03 (UTC)

That is odd. You are right, but when I uploaded the PKGBUILD they matched what was published in the github hash file (I built it on all my machines: x86 & ARM) and none complained about integrity checks...

crox commented on 2016-12-19 18:36 (UTC)

I think you've put the wrong SHA256 hash for the AMD64 release into the PKGBUILD, it should be ed5189ca01ad87667f34bf3a669ea7a21e818ffe3f2fef0b5d7cb343a1da7716 as per the released hashes from the project.

jasonwryan commented on 2016-03-28 19:58 (UTC)

Thanks jenrik: not sure how I missed that for .21. I'll move to 256 for the next release.

jenrik commented on 2016-03-28 14:22 (UTC)

sha1sums for 0.12.21-1 doesn't match. I get the following when I manually run sha1sum: 83e245763eaa2aa74d8ab280c2b563ae072aae61 syncthing-linux-386-v0.12.21.tar.gz 5401d90aefd4fd805a284f0a7ea1b6f25acf2c00 syncthing-linux-amd64-v0.12.21.tar.gz 5e08bb481d1f6f4f7e5d31e68fbae0854dac01a2 syncthing-linux-arm-v0.12.21.tar.gz We should maybe consider using the sha256sums offically provided by syncthing.

kiko commented on 2016-01-14 05:34 (UTC)

Heads up y'all:

jasonwryan commented on 2015-04-22 01:05 (UTC)

Thanks runical: updated with 0.11.0

runical commented on 2015-04-18 08:32 (UTC)

The project was re-licensed to MPLv2 a while back. [1,2] Can you update the license with the next release? [1] [2]

jasonwryan commented on 2015-02-10 20:59 (UTC)

Only that I hadn't been paying attention :p Thanks richli: I'll include them in the next release...

richli commented on 2015-02-10 16:25 (UTC)

Is there a reason the upstream systemd units are not used? The latest version (v0.10.22) included an update to handle the exit codes better. In the downloaded tarball, they're in etc/linux-systemd/{system,user}/.

jasonwryan commented on 2015-01-21 09:10 (UTC)

Yes, I'll upload a new PKGBUILD when 0.10.21 comes out: which should be any day now... Keep your shirts on.

lastmikoi commented on 2015-01-21 09:05 (UTC)

Flagging as out of date since the source URI is not valid anymore (as stated by roguewolf) The following unified patch made me able to upgrade: --- PKGBUILD.old 2015-01-21 10:01:48.233591592 +0100 +++ PKGBUILD 2015-01-21 10:03:27.553594162 +0100 @@ -36,7 +36,7 @@ ;; esac -source+=("${_realname}/releases/download/v${pkgver}/${_realname}-linux-${_pkgarch}-v${pkgver}.tar.gz") +source+=("${_realname}/releases/download/v${pkgver}/${_realname}-linux-${_pkgarch}-v${pkgver}.tar.gz") package() { cd "${_realname}-linux-${_pkgarch}-v${pkgver}"

roguewolf commented on 2015-01-16 08:51 (UTC)

Source should be changed from "…" to "…" (platform-specific releases aren't available on the author's personal fork).

csantosb commented on 2015-01-04 20:31 (UTC)

Just for the record, to keep old behaviour (start-up right after boot and let syncthing running after logout), refer to the wiki

jasonwryan commented on 2014-12-29 18:34 (UTC)

I have added the --user service file as requested.

xuhdev commented on 2014-12-25 07:31 (UTC)

About the `--user` mode, there is a reason to add such a service file for that: the service is only loaded after the first login and stops after the last logout. The service won't work if one has an ecrypted home directory which is unavailable until the user types her password to log in. Also see this issue

jasonwryan commented on 2014-10-24 09:22 (UTC)

@xuhdev: thanks, updated with the new release.

xuhdev commented on 2014-10-20 19:43 (UTC)

The license should be GPL not MIT

jasonwryan commented on 2014-10-19 09:07 (UTC)

@neroburner added...

neroburner commented on 2014-10-19 08:23 (UTC)

is it possible to set provides to "syncthing=0.10.2", syncthing-gtk has a dependency for at least version 0.10

jasonwryan commented on 2014-09-27 20:06 (UTC)

Clearly I haven't used that architecture... Fixed: thanks.

Mikaye commented on 2014-09-27 19:55 (UTC)

The armv5h is called "arm" on the arch field of the PKGBUILD.

jasonwryan commented on 2014-09-27 19:42 (UTC)

Added armv5

Mikaye commented on 2014-09-27 12:35 (UTC)

Please add arm architecture (armv5). Thanks !

jasonwryan commented on 2014-09-08 08:16 (UTC)

`--user` mode is still some way from being ready for prime time, and the man page you are referencing makes no mention of depreacting @service, so I see no compelling reason to change the current packaging.

jancici commented on 2014-09-08 07:50 (UTC)

sorry, I dont have a link, I did read that somewhere ... as you can read from that man page, section Unit Load Path, they are saying about two types or running. I thing that syncthing should be run in user mode.

jasonwryan commented on 2014-09-07 21:21 (UTC)

@janici do you have a link? The man page still indicates this is the correct way to start a service from a template:

jancici commented on 2014-09-07 18:37 (UTC)

I think that using systemctl start syncthing@UserName is deprecated {I am not 100% sure} So there should be syncthing_user.service which could be used as follow: systemctl --user start syncthing thanks

jasonwryan commented on 2014-09-05 22:32 (UTC)

I've automated the updating of all the sha1sums across the architectures, so you should just be able to run `makepkg -i` and have the package install...

roguewolf commented on 2014-09-02 18:55 (UTC)

That's very useful, thank you. I'll run that in future.

jasonwryan commented on 2014-09-02 18:08 (UTC)

Yes, because of the different architectures, you should run `updpkgsums && makepkg -i`. For future releases, I'll do my best to updates the sha1sums, but I wouldn't count on it...

roguewolf commented on 2014-09-02 10:25 (UTC)

Excellent, that did the trick, thank you. (PS - I had to change the tar sha1sum in the PKGBUILD to 30d2350ee90336e52662c644f0984b4f051997d5)

jasonwryan commented on 2014-09-01 18:07 (UTC)

This package will notify you when you install that it conflicts with synchting and ask you if you wish to remove syncthing and install syncthing-bin. If you select `y`, it will replace it *without* any impact on your repositories and nodes...

roguewolf commented on 2014-09-01 10:41 (UTC)

If I remove the community syncthing package and install this one, do you know if it will retain my nodes and repositories?