tuxpoldo

Members
  • Posts

    730
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by tuxpoldo

  1. The reason stays in the official documentation: "Default setting for folder preference "Use predefined hosts". Hosts should be entered as single line of IP:port pairs comma-separated (no other delimiters allowed)." It is true, that BitTorrent Sync accepts anything in the string and continues working. But I suppose that BitTorrent Sync ignores anything it does not understand. I asked the support, if hostnames work as expected (that means: BitTorrent Sync has to periodically resolve them via DNS since the IP address could have changed). Let's wait for the answer. UPDATE: I got an answer from Roman: I will remove the number filter in the next release. See Issue #156
  2. The problem is due to an incompatibility between btsync-user and BitTorrent Sync 1.4. See Issue #155 - the problem will be fixed in the next release. If you are impatient, you should give btsync-gui a try. You can find more information in this topic. The installation of btsync-gui automatically replaces btsync-user and migrates the configuration: sudo apt-get install btsync-guiWARNING: Please keep in mind, that migrating back to btsync-user is not straightforward and requires manual interventions!
  3. This is the consequence of an undocumented SyncAPI change. See Issue #154. I also discovered, that the (also) undocumented parameter force=1 solves the problem. curl -u admin:admin 'http://localhost:8888/api?method=add_folder&dir=/mnt/btsync/test1&secret=ASFODAMD23QUM2H65QVTB6GZRVAOSRTN7'{ "error": 105, "message": "Destination folder is not empty. Add anyway?" } After adding force=1 curl -u admin:admin 'http://localhost:8888/api?method=add_folder&dir=/mnt/btsync/test1&secret=ASFODAMD23QUM2H65QVTB6GZRVAOSRTN7&force=1'{ "error": 0 }
  4. This is the consequence of an undocumented SyncAPI change. See Issue #154 - will be fixed ASAP in the new version.
  5. New version! Enjoy! btsync (1.4.0-3) unstable; urgency=low * Added debconf support for new advanced settings (Closes #150) - folder_defaults.known_hosts - peer_expiration_days - directory_root * Fixed broken Simplified Chinese translation (Closes #152) * Fixed and improved service stop behaviour (Closes #149) -- Leo Moll <leo.moll@yeasoft.com> Tue, 04 Sep 2014 22:58:10 +0200
  6. I could reproduce it. Will be fixed ASAP (I hope...). See Issue #154 Thank you! Update: This is the consequence of an undocumented SyncAPI change. Will be fixed ASAP in the new version.
  7. Ahem.... There was a bug in my howto (I fixed it in the original message). The reason it works, is that I have released 1.4.75 in the meantime. It should not be stable but experimental. Sorry.
  8. The experimental repository is very unofficial The 1.4.75 is now available in the experimental repository.
  9. There is already such a testing repo. You can edit the file /etc/apt/sources.list.d/yeasoft.list and change the contents to: deb http://debian.yeasoft.net/btsync experimental maindeb-src http://debian.yeasoft.net/btsync experimental mainGenerally I will publish my testing versions here before publishing them in the regular repositories. The AMD GEODE is a low power, Pentium compatible CPU used in embedded Boards like the PCengines Alix Boards. The architecture is i386 and you can generally install any i386 Linux flavour (only the kernel or drivers should not rely on things like the i686 instruction set, PAE or other modern stuff). All Linux i386 versions of btsync up to 1.3.109 did crash on GEODE processors since they were explicitly compiled for i686 CPUs. That's the reason the developers provided also a GEODE version. With 1.4.72 there was no GEODE version, but I noticed that the i386 version is now running also on GEODE. But after the publication of versioned links for 1.4.75, I discovered also a GEODE version. This makes things complicated.
  10. I discovered the build yesterday. But there are still some unclear facts like the reappearance of the GEODE build and some rumours in the forum that the Linux version of 1.4.75 crashes frequently. I will at least try to test it a few days before releasing.
  11. OK - Here it comes. Execute the following commands: `which sudo` apt-key adv --keyserver keys.gnupg.net --recv-keys 6BF18B15echo deb http://debian.yeasoft.net/btsync13 experimental main > ~/btsync.listecho deb-src http://debian.yeasoft.net/btsync13 experimental main >> ~/btsync.list`which sudo` mv ~/btsync.list /etc/apt/sources.list.d/btsync.list`which sudo` chown root:root /etc/apt/sources.list.d/btsync.list`which sudo` apt-get updatePlease keep in mind, that the internal database of 1.4 is not compatible with 1.3. If you want to revert, you have to start from scratch. uninstall 1.4, remove all internal databases (like the one in /var/lib/btsync) and reinstall everything with the new repository.
  12. This is a duplicate posting. Please see my answer in the corresponding topic.
  13. This is correct. Support for handling those links may be added in a future release, as soon as BitTorrent Inc. releases the corresponding API functions. As a workaround, you can access the web interface of BitTorrent Sync. To enable the web interface, stop BitTorrent Sync and than execute the following command from the command line: btsync-gui --webui --savedefaultsThe menu of the status indicator will now show also an option to connect to the web UI. Since the Web UI is vital for handling those kinds of links, I will enable the web UI by default in the next release. See Issue #148
  14. Unfortunately the huge changes to the web UI made the indicator applet totally incompatible with BitTorrent Sync 1.4. The problem is tracked in Issue #52 of the btsyncindicator project on GitHub. We have to wait for marxjohnson to fix the problem before I can publish a new release of btsync-user. This make take a while, since Mark was not very active in the last months. If you are impatient, you should give btsync-gui a try. You can find more information in this topic. The installation of btsync-gui automatically replaces btsync-user and migrates the configuration: sudo apt-get install btsync-gui UPDATE: In your duplicate posting in the wrong topic you wrote additionally: Can you please tell me, which version you were using, and which version you have now? You can find such information in the /var/log/dpkg.log files
  15. Ghostery is also installed on my browser, but it does not block it. I suppose that adblock is the problem... Maybe you can put the Web UI on the whitelist (in case adblock supports whitelists)?
  16. I tested it here on different platforms (btsync 1.4.72 installed with my btsync package) on several platforms (amd64,i386 both Ubuntu 12.04, 14.04 and Debian 7) and different browsers (Google Chrome on Mac OSX, Google Chrome on Debian) and it worked for me with the automatically created self signed certificate... Perhaps your browser is blocking it?
  17. I noticed that under certain circumstances the daemon does not really stop (on update/reconfiguration). Can you please restart/reboot the affected machines? As an alternative you can try to kill the daemon(s) manually and then restart them: sudo pkill btsync-daemonsudo service btsync restartI'm investigating the issue... See Issue #149
  18. Same problem, same solution Look: http://archive.yeasoft.net/btsync/ And this was my nice (not any more working) script for creating the source archive for Debian packaging: #!/bin/bash# base download locationsBASE_BIN_LOCATION=http://syncapp.bittorrent.comBASE_DOC_LOCATION=http://btsync.s3-website-us-east-1.amazonaws.comfunction cleanup_temp() { for ARCH in arm powerpc geode i386 x64 freebsd_i386 freebsd_x64; do rm -f btsync_${ARCH}-${VERSION}.tar.gz done rm -rf temp-btsync}function move_dest() { if [ -d ${VERSION} ]; then rm -rf "${VERSION}" fi mkdir -p "${VERSION}" mv temp-btsync/btsync-common/BitTorrentSyncUserGuide.pdf "${VERSION}" for ARCH in arm powerpc geode i386 x64 freebsd_i386 freebsd_x64; do mv btsync_${ARCH}-${VERSION}.tar.gz "${VERSION}" done mv btsync-${BINVERSION}.tar.gz btsync-common_${BINVERSION}.orig.tar.gz "${VERSION}"}function get_downloads() { echo "Getting BitTorrentSyncUserGuide.pdf" if ! wget -q ${BASE_DOC_LOCATION}/BitTorrentSyncUserGuide.pdf; then echo "Failed to get BitTorrentSyncUserGuide.pdf" >&2 return 1 fi mkdir -p temp-btsync/btsync mv BitTorrentSyncUserGuide.pdf temp-btsync/btsync for ARCH in arm powerpc geode i386 x64 freebsd_i386 freebsd_x64; do case ${ARCH} in x64) DEST=amd64 ;; freebsd_i386) DEST=kfreebsd-i386 ;; freebsd_x64) DEST=kfreebsd-amd64 ;; *) DEST=${ARCH} ;; esac echo "Getting btsync_${ARCH}-${VERSION}.tar.gz" if ! wget -q ${BASE_BIN_LOCATION}/${VERSION}/btsync_${ARCH}-${VERSION}.tar.gz; then echo "Failed to get btsync_${ARCH}-${VERSION}.tar.gz" >&2 return 1 fi mkdir -p temp-btsync/btsync/${DEST} if ! tar xzf btsync_${ARCH}-${VERSION}.tar.gz -C temp-btsync/btsync/${DEST}; then echo "Failed to extract btsync_${ARCH}-${VERSION}.tar.gz" >&2 return 1 fi touch -r temp-btsync/btsync/${DEST}/btsync temp-btsync/btsync/${DEST} touch -r temp-btsync/btsync/${DEST}/btsync temp-btsync/btsync done return 0}if [ -z $1 ]; then echo 'USAGE: makesrcarchive <version>' exit 1;fiVERSION=$1if ! get_downloads; then cleanup_temp exit 1;fiif [ "$2" != "-d" ]; then # get the real version number from binary # BINVERSION=$(temp-btsync/btsync/amd64/btsync --help | grep "BitTorrent Sync" | cut -d' ' -f 3) BINVERSION=${VERSION} # rename source directory mv temp-btsync/btsync temp-btsync/btsync-common # create archive echo "Creating source archive btsync-${BINVERSION}.tar.gz" tar czf btsync-${BINVERSION}.tar.gz -C temp-btsync btsync-common touch -r temp-btsync/btsync-common btsync-${BINVERSION}.tar.gz echo "Creating symbolic link to .orig archive" ln -sf btsync-${BINVERSION}.tar.gz btsync-common_${BINVERSION}.orig.tar.gz touch -h -r temp-btsync/btsync-common btsync-common_${BINVERSION}.orig.tar.gz # move to destination move_destfi# tidy upcleanup_temp
  19. I'm afraid that the toolchain of Debian "lenny" is too old (See http://gcc.gnu.org/ml/gcc/2013-02/msg00239.html) and does not provide the required function. Sorry - no chance. Since there is a lot of people really angry about 1.4, I'm seriously thinking about providing a repository with the latest 1.3 based packages (there is an info, that 1.3.109 is fully compatible with the 1.4 protocol...) .....
  20. Today (or yesterday?) they updated the btsync version. I discovered it by casually reading this topic and then checking... This will make our work really hard. Furthermore there is no changelog...
  21. Today (or yesterday?) they updated the btsync version. I discovered it by casually reading this topic and then checking... This will make our work really hard. Furthermore there is no changelog...
  22. This error has already been reported and fixed. See this forum post. Unfortunately the PPA builds are still not available, since Launchpad seems to be really busy and it will probably take a lot of time before the updates are available. PLEASE DO NOT USE THE PPA IF POSSIBLE. IT HAPPENS MORE AND MORE OFTEN THAT IT TAKES HOURS/DAYS FOR UPDATES TO BE PUBLISHED THERE. PLEASE USE THE YEASOFT REPOSITORY SINCE THIS IS THE MAIN REPOSITORY AND UPDATES ARE AVAILABLE IMMEDIATELY AFTER RELEASE. SEE THE INITIAL POSTING FOR DETAILS.
  23. This error has already been reported and fixed. See this forum post. Unfortunately the PPA builds are still not available, since Launchpad seems to be really busy and it will probably take a lot of time before the updates are available. PLEASE DO NOT USE THE PPA IF POSSIBLE. IT HAPPENS MORE AND MORE OFTEN THAT IT TAKES HOURS/DAYS FOR UPDATES TO BE PUBLISHED THERE. PLEASE USE THE YEASOFT REPOSITORY SINCE THIS IS THE MAIN REPOSITORY AND UPDATES ARE AVAILABLE IMMEDIATELY AFTER RELEASE. SEE THE INITIAL POSTING FOR DETAILS.
  24. That's correct. Setting the UMASK is considered as an advanced setting. During initial installation, only the most important settings are asked.