Arch Linux User Repository

@serialhex: because when this package was started, bittorrent-sync had no version number, which is why the former packager used the date. And 20130401 is "newer" than 1.1.13, so the epoch had to be increased. Note that these versioning changes are exactly what the epoch variable is for. What does the epoch mess up exactly?

aszkid - if you started it up with the `sudo systemctl start btsync@aszkid` then the username you need to use is `aszkid` (or whatever your username is).

I'm not able to access the WebUI using the default credentials on the /etc/btsync.conf file (admin - password). Do i have to change them before starting?

crabman: why was it put there in the first place? there was no reason for it, and i loathe to put it back in as it is unnecessary cruft that messes with things. i would rather everyone upgrade & get a version w/o the epoch... is there any way to change this besides putting the epoch variable back in?

serialhex: i am the one who put the epoch=1 there. And its _very_ important. With it removed, everybody using an AUR manager (such as yaourt) will be stuck with version 1:1.1.27 because the manager thinks that version 1:1.1.27 is newer than version 1.1.42. Please readd it. crabman, aka Kilian Lackhove

Thanks serialhex, that's done the trick.

@roguewolf I just uploaded it again, the SHA256 on the uploaded package was wrong. You should be able to get it to work now, sorry for the trouble!

I've just tried again with the same result (SHA256 sum of downloaded copy of btsync_i386-1.1.42.tar.gz is ecc84e88db5fe3054306b1901fb437bf868df9b8ede5dfbc22b79105dd2a8e2b): $ wget https://aur.archlinux.org/packages/bi/bittorrent-sync/bittorrent-sync.tar.gz --2013-07-18 14:21:41-- https://aur.archlinux.org/packages/bi/bittorrent-sync/bittorrent-sync.tar.gz Resolving aur.archlinux.org (aur.archlinux.org)... 78.46.78.247, 2a01:4f8:120:34c2::2 Connecting to aur.archlinux.org (aur.archlinux.org)|78.46.78.247|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 4955 (4.8K) [application/x-gzip] Saving to: ‘bittorrent-sync.tar.gz’ 100%[======================================================================================================================>] 4,955 --.-K/s in 0s 2013-07-18 14:21:41 (312 MB/s) - ‘bittorrent-sync.tar.gz’ saved [4955/4955] $ tar -xvzf bittorrent-sync.tar.gz bittorrent-sync/ bittorrent-sync/PKGBUILD bittorrent-sync/bittorrent-sync.install bittorrent-sync/btsync.service bittorrent-sync/btsync@.service bittorrent-sync/btsync-makeconfig.sh bittorrent-sync/btsync-wrapper.sh bittorrent-sync/btsync.conf.doc $ cd bittorrent-sync/ bittorrent-sync$ makepkg ==> Making package: bittorrent-sync 1.1.42-1 (Thu 18 Jul 14:23:26 BST 2013) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found bittorrent-sync.install -> Found btsync.service -> Found btsync@.service -> Found btsync-makeconfig.sh -> Found btsync-wrapper.sh -> Found btsync.conf.doc -> Found terms-of-use.html -> Found privacy-policy.html -> Found btsync_i386-1.1.42.tar.gz ==> Validating source files with sha256sums... bittorrent-sync.install ... Passed btsync.service ... Passed btsync@.service ... Passed btsync-makeconfig.sh ... Passed btsync-wrapper.sh ... Passed btsync.conf.doc ... Passed terms-of-use.html ... Skipped privacy-policy.html ... Skipped btsync_i386-1.1.42.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

@roguewolf I just double-checked the checksum on that file and it checks out, maybe you downloaded a bad copy & should try again?

In any case, the service (/usr/lib/systemd/system/btsync@.service) assumes that the PID file is at ~/.config/btsync/sync.pid. Unless you explicitly set the "pid_file" setting in your config file, the sync.pid file is created in the "storage_path" directory. If you've changed either of those settings, you'll need to update the PIDFile setting in the service accordingly.