Silvenga

Members
  • Content Count

    23
  • Joined

  • Last visited

  • Days Won

    4

About Silvenga

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

426 profile views
  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: https://github.com/Silvenga/btsync-deb/issues/10
  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 up
  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: http://ubuntuforums.org/showthread.php?t=1558616 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: https://github.com/Silvenga/btsync-deb.
  12. Please check out my answer to that issue here: https://github.com/Silvenga/btsync-deb/issues/3. 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 (https://github.com/Silvenga/btsync-deb/issues/4). 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 "deb.silvenga.com" 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 http://deb.silvenga.com/btsync any maindeb-src http://deb.silvenga.com/btsync 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 http://deb.silvenga.com/btsync 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.