Username: Password: Remember me
Search + Advanced
Package Details

syncthing 1.3.4-1
Open Source Continuous File Synchronization

Category: network

Submitter: Bridouz
Maintainer: sampla
Votes: 2

License: MPLv2

Last Updated: 2020/02/07 - 02:33:49 +0000
First Submitted: 2019/02/17 - 15:09:18 +0000

Tarball :: PKGBUILD



Comment by: sampla on Sat, 05 Oct 2019 04:04:09 +0000

As of Syncthing 1.2.x, the check() failures seem to have stopped. Please correct me if I'm wrong, but I think it's now safe to ignore my prior comments on this page.

Comment by: sampla on Wed, 22 May 2019 08:47:44 +0000

If check() fails for you, please run these commands to try again manually. This is necessary because prepare() only expects to be ran once, as it would if check() passed consistently.

cd /tmp/ccrbuild-$UID/syncthing/syncthing
makepkg --noprepare --check  # Repeat this command until it succeeds.
makepkg --install

Comment by: sampla on Wed, 22 May 2019 04:43:38 +0000

Update on check() failures:

I tried much larger sample sizes and got different results.

Building Syncthing 1.1.3 with Go from the ___ package succeeds:
- With "go": 55/100 times.
- With "go-pie": 0/100 times.

So it always fails with buildmode=pie, but only about half the time without. This is with "export GO_TEST_TIMEOUT_SCALE=2" superstitiously added to check(). I'm testing another 100 times with that commented out. If it has a similar failure rate, I'll upload the PKGBUILD without it. Otherwise, I'll upload whichever has the lowest failure rate.

If anyone has any ideas what's going on or how to fix this, please tell me. Otherwise, I think I'll report a bug upstream tomorrow.

Comment by: sampla on Thu, 16 May 2019 07:58:53 +0000

Update: Removing the pie patch from Go and rebuilding passed the tests.

This could be a bug in:
- Go (since code should run the same regardless of compiler mode)
- Syncthing (since it may be doing something lower-level than necessary in the tests in order to hit this)
- Chakra (since it changes Go's default in a sometimes-broken way)

Does anyone know where I can find official documentation of the stability of Go's "pie" build mode and if/how it's expected to change things? As-is, I don't know where to report the bug.

Comment by: sampla on Thu, 16 May 2019 07:20:35 +0000

I manually updated Go to 1.12.5, but Syncthing 1.1.3 still fails on testing. It's at ``, which is the same error as before. I'll try removing the "pie" (position independent executable) patch from Go and rebuilding again.

Comment by: sampla on Thu, 16 May 2019 01:21:24 +0000

@Bridouz: Thanks! Adopted.

I'll upload the 1.1.1 PKGBUILD once I'm at my real computer, and later versions once I can get them to build without failing tests.

Comment by: Bridouz on Wed, 15 May 2019 19:50:56 +0000

@sampla It's yours smile

Comment by: sampla on Wed, 15 May 2019 02:26:06 +0000

@Bridouz, do you still want to maintain this package? I feel like I could be a more frequent maintainer because the Syncthing app updating on my phone reminds me when new releases are made.

Comment by: sampla on Wed, 15 May 2019 01:41:55 +0000

Outdated Go reported. … issues/190

Comment by: sampla on Wed, 15 May 2019 01:13:20 +0000

Latest release is version 1.1.3 with sha256sum of d8d6b256e21a9db4be0453522206f044d4e54da15bd1d96a2624085948252a3d.

Versions 1.1.2, 1.1.3, and 1.1.4-rc.1 fail the tests. I suspect that Chakra's outdated version of Go may be to blame. I will submit a bug for it being out of date.

Latest release that passes tests on Chakra is version 1.1.1 with sha256sum of a796583c12894765394be38e8de858705491dc674289bb6936e68aeb4be23477.