Arch Linux User Repository

@prurigo I just had an issue where my AUR helper(or even makepkg, I couldn't see it that well) tried to remove the previous build directory including the src/pkg folder. Some subdirectories in there are sadly marked read-only due to https://github.com/golang/go/issues/27161.

To prevent this, please add -modcacherw to the go commands (and consider also adding the other flags from the go packaging guidelines

@hucsmn: Nice find! This is definitely the way to go here-- no need to worry about de-synchronized deps and way fewer make dependencies. Pulled your changes into the package. Thanks!

@prurigro I've just looked into the tarball release and found that it brings a correct copy of dependencies under the vendor directory. Vendor mechanism is supported since go 1.6, it requires the package to be located under GOPATH to enable package searching for vendor directory. Therefore there is no need to apply my previous dummy patch to fix those dependency problems introduced by go get. Just make a fake GOPATH and move the source code into $GOPATH/src/github/syncthing/syncthing to satisfy go toolchain, then it successfully build. The modified PKGBUILD is here: <http://sprunge.us/zJ1be3>. Redundant build dependencies (git, godep, mercurial) were also removed.

Aha-- OK, hucsmn's patch works but an out of date $srcdir/src breaks things.

I released an update to v0.14.52 including the patch by hucsmn and the additional install instructions and systemd service fix provided by Iiridayn (credits included in the PKGBUILD- thanks!)

@hucsmn: The build is still failing for me with your patch. Is this intending to fix 0.14.51 or the ALARM build? (I tested unsuccessfully on the former). If it's a versioning issue with go get, thoughts on having the package manually download dependencies with specified commits?

It failed to build because go get has no proper version control mechanism. Try this patch to work around: <http://sprunge.us/J2Vztx>, inserting the following line of code to build(): curl sprunge.us/J2Vztx | patch -p1 -d $_pkgname-$pkgver/cmd/$_binname

btw, 0.14.51 is available now.

@prurigro I also get that same error on Arch ARM.

Hmm, I haven't tested the build on ALARM in a while-- is everyone else hitting that error on ALARM as well?

@mqs same error

@mqs same error