filemoon

New Members
  • Content Count

    18
  • Joined

  • Last visited

About filemoon

  • Rank
    Member

Recent Profile Visitors

349 profile views
  1. Hi. Can you update GPGs on official repo please? "W: GPG error: http://linux-packages.getsync.com resilio-sync InRelease: The following signatures were invalid: KEYEXPIRED 1482402887 KEYEXPIRED 1482402887 KEYEXPIRED 1482402887" Regards Chris
  2. +1 I have very same issue. ./rslsync: symbol lookup error: ./rslsync: undefined symbol: _ZNSt7num_putIcSt19ostreambuf_iteratorIcSt11char_traitsIcEEE2idE
  3. Can you create deb repository for Resilio application. Old btsync official repository is not up-to-date. I'm quite sure repo will be updates as product was rebranded. Regards Chris
  4. I have very same problem all folders disconnected on all devices (disconnect is default folder action) - arm servers/x86 server/osx workstation. 2.3.7 - version. Is it just extremely annoying ;\
  5. How to start btsync binary on ARM64 system: http://forum.odroid.com/viewtopic.php?f=135&t=18806&p=124525#p132607
  6. It is - when you are using arm64 you can run armhf binaries - no issues. I have no idea why this is not working
  7. Hi. Silvenga - you are big and doing great job (sorted). Thank you (I was a bit overenthusiastic - installation is ok but binary is not working with arm64 cpu (strange error) - same story with binary downloaded directly form their webpage (but repo is 100% ok- I've contacted support let's see if they can help me).
  8. "W: Failed to fetch http://deb.silvenga.com/btsync/dists/any/InRelease Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file" Very same error (apt cache was removed).
  9. Hi. I have new member in my arm familly Odroid C2. But I'm unable to instal btsync from repo. "W: Failed to fetch http://deb.silvenga.com/btsync/dists/any/InRelease Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)"
  10. There is a issue with update - all my Debian bases arm servers (4) hangs during update with very same message " The following packages will be upgraded: btsync-core 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/4,441 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Reading changelogs... Done (Reading database ... 25660 files and directories currently installed.) Preparing to unpack .../btsync-core_2.3.6-1.0_armhf.deb ... Unpacking btsync-core (2.3.6-1.0) over (2.3.3-1.0) ... Processing triggers for btsync (2.3.0-1.0) ... "
  11. Yes it is - my recommendation is to use it with Silvenga repo. I have two XU4 in my btsync network. https://launchpad.net/~silvenga/+archive/ubuntu/btsync
  12. No I was able to copy missing files (from other machine where btsync was installed previously). I've tried to run cleanup and install again/force install but there was no success. But when I had working arm machine I was able to check what is missing.
  13. Thank you for answer. I have issue to run it on one of my rasbian nas - reinstalling is not fixing the issue. Installation is completed but when I'm trying to start it is not strting. I see some "components" are missing btsync-core (binary was not there after installation). Trying to fix it manually .... I was able to fix it, I copy missing files from other (working) rasbian - but I think there may be problem with repo.
  14. @Silvenga Is your repo ok? "dpkg: warning: files list file for package 'btsync-core' missing; assuming package has no files currently installed"
  15. I'm trying to investigate the issue. Funny is all my full syncs are on the servers only - on stations/phone I have selective only. I always upgrade binary via ssh replacing old version (always in same folders). And was no issue. The is no mistake from my side. Until version 2.3 - when I log to web interface I have initial screen (create username/password screen). You may be a right about forum - but I'd like to warn everyone before they consider moving to ver 2.3.