• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Silvenga

  1. Thought that was going to happen. I was hoping there was a compatibility layer like with x86 -> x64 (I see now there isn't), I also saw that tuxpoldo's launchpad repo had arm64 builds (I see now there isn't any binaries). Ping me if Bittorrent provides an arm64 release and I'll update the repo.
  2. Ha! The package made it into my staging repo, but wasn't pushed to the production repo. Try again.
  3. I've added arm64 based off of the current arm packages, please try again.
  4. Reference and followup can be found here:
  5. Unfortunately, Ubuntu LTS doesn't ship with SystemD at this time and installing it is relatively unsafe.
  6. An Unofficial Btsync Ubuntu/Debian Packaging Project Fork Bittorrent Sync is an awesome solution for many problems ranging from synchronizing large amounts of files to certain centralized governing bodies. About three years ago, @tuxpoldo and many other contributors created the unofficial packaging project for Ubuntu/Debian to ease deployments on these systems - the project has since evolved to fill in the missing gaps of the official Sync project and continues to provide packages for legacy Btsync clients. Current features include, but are not limited to: Easy installing and upgrading Generated configuration files (via an easy command line interface) Run as a different user/group Startup/Shutdown scripts Support for multiple instances Custom nice levels A Reboot Unfortunately, after several years of active work, it seems @tuxpoldo has moved on and the unofficial packages got a bit stale. Since all the work is open source I was able to build new packages (with a few tweaks here and there) and since many members of the community used the packages I decided to share my work publicly. An archive of the original post from @tuxpoldo: I will be providing continued maintenance for this awesome project and until I am accustomed to this project (or Python for the matter) I can provide support for the btsync and btsync-common packages with new binary versions and bugfixes. I personally use these packages on several headless servers to sync files and will particularly support that use case. Debian and Ubuntu packages can be found under my private repository New versions should be automatically built and published to this location via my build server (found above) when new changelogs are released. These packages should also work for other Ubuntu/Debian derivatives (Mint, LUbuntu, Raspbian, etc.). The source to these packages (e.g. build scripts, changelogs, etc.) can be found in my GitHub fork: I encourage reporting issues with the packaging to this repository. Cheers! Installing Add my package signing key: apt-key adv --keyserver --recv-keys 992A3C9A3C3DE741 Add the btsync repository: add-apt-repository "deb any main" apt-get update Install btsync apt-get install btsync After following the prompts, open your browser to (if using the default configuration). TODO List Log to proper log folder. (log path is now customizable via #6) Setup logrotate. (might not be needed) Fix the formatting of this post. FAQ Adding a new synced folder results in the following error: Make sure the user Btsync is running as has read and write access to the path set when prompted for the "Start path for the web interface". Alternatively, / can be used. You would receive something like the following when running apt-get-repository: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 167, in <module> sp = SoftwareProperties(options=options) File "/usr/lib/python3/dist-packages/softwareproperties/", line 105, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/", line 595, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/", line 89, in get_sources (, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Raspbian/jessie Raspbian's add-apt-repository seems to be broken under at last Jessie. The following commands will resolve the issues: echo "deb any main" > /etc/apt/sources.list.d/silvenga-btsync-deb.list apt-get update apt-get install btsync Adding signing key fails with the following stacktrace: gpg: requesting key 3C3DE741 from hkp server gpg: no writable keyring found: eof gpg: error reading `[stream]': general error Make sure to run all the above commands as root either by using sudo or switching to the root user.
  7. @knireis I would make a copy of the Btsync settings and purge my version before installing the official packages. Your sync data will not be deleted. The settings can be found at: /etc/btsync/* and /var/lib/btsync/* Although, I haven't looked at the official packages as of yet.
  8. Just thought of something, @filemoon. Did you reinstall btsync and btsync-core?
  9. You were able to install it on another armel machine? That is strange - I've looked over the .debs in my repo and they appear to have been packed correctly - maybe something with Amazon's AWS? Or maybe the local installation went a little wonky (and the wonky was cached by apt-get). Try something like this: to cleanup and force a reinstall?
  10. It should be. I'll take a look when I get back home (I haven't seen anything wrong today). In the meantime, if you can, does reinstalling fix it?
  11. I have upgraded the packages to 2.3 found here:
  12. Please check out my answer to that issue here: This will preserve the fix across updates. I would recommend changing the user of btsync to you own user for security and convenience. You can change the user with: dpkg-reconfigure btsync. I would not recommend following that particular guide as it references the now legacy btsync 1.2 ( Some of the steps are no longer required and might complicate your setup.
  13. Yes, removing his sources would be the cleanest method; however, since my packages will have higher versions than Tuxpoldo's you could get away with only adding my sources. Make sure to use my personal repository at "" as I have depercated the usage of Canonical's repositories due to compatibility issues.
  14. Another user asked about a similar issue. If it is the same issue, in your /etc/apt/sources.list file (at the end) there should be two lines as follows: deb any maindeb-src any mainNormally the second line is commented out automatically by add-apt-repository. However, there was a bug in the Ubuntu Precise version that prevented this. Run the following to cleanup:add-apt-repository --remove "deb-src any main"In theory I should include source packages in my repository - I just haven't gotten to it.
  15. I'm noticing some seemly unrelated actions are crashing the btsync daemon. For example, if I restart the VPN btsync crashes without logs. I'm wondering if your issue is due to a bug in btsync somewhere (maybe permissions on one of your files?, etc.). Sorry I can't be more helpful.
  16. Np, could you check `/tmp/sync.log`? What distro are you running and are you running it with systemd? You could also try to dpkg-reconfigure btsync again.
  17. If anything, some minimal Debian/Ubuntu builds need the software-properties-common package to be installed for the add-apt-repository command to work. add-apt-repository is just a wrapper to automatically add sources to the /etc/apt/sources.list file and is sometimes considered superfluous, thus removed. I'm not used to BBCode forums, I can figure out how to do single tics like on a Markdown style forum... So bold it is! It might be a temporary issue. You can add the servers manually using the "Predefined hosts" option on the folder.
  18. Awesome! Feel free to email me (address on if I'm slow to update.
  19. I gave up on using Launchpad. I've uploaded the packages (including ARM) to my private repository - # Add my signing keyapt-key adv --keyserver --recv-keys 992A3C9A3C3DE741# Add the btsync repositoryadd-apt-repository "deb any main"Please check them out. It should work without modifications. Btsync 2.2.1 fixes the configuration issues reported earlier (which is included in the above packages).
  20. I'll make a request to Launchpad to enable arm builds for this repository when I get home. However, Launchpad can only build armhf arm packages as armel is being deprecated. I'll need to look into how @tuxpoldo made packages for the Pi.
  21. I used Btsync some time ago, but stopped when it began a subscription model. With the creation of the one-payment option I thought I would try Btsync again. Seeing that the official-unofficial packages have become a bit stale, I attempted to build my own based on the work of @tuxpoldo - upgrading along the way. So, until Mr. Moll upgrades his packages, I'm maintaining a personal fork of his repository here: I'll use it for my own deployments, but anyone is free to check them out. The binaries are published to Canonical's repositories on the PPA's: I've only tested btsync 2.2.1 under Ubuntu Trusty 64-bit in headless mode, but I don't anticipate any issues on other Debian based operating systems. I can add other Ubuntu distributions or CPU architectures if there's a want. Cheers!