tuxpoldo

Members
  • Posts

    730
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by tuxpoldo

  1. OK - your installation archive is OK But nothing has been installed. I really have no idea what's the problem on your machine. So I have now only two possible suggestions for you: 1. You can try a real hard uninstall and reinstall. But this will kill all your internal status data of btsync (in case there was a previous version installed). If this is OK for you: sudo apt-get --yes --purge remove btsync btsync-commonsudo apt-get --yes --purge autoremovesudo apt-get --yes install btsync2. If this does not help, or you cannot effort to lose the internal configuration data of btsync, I can offer to analyse the problem together with you by a screen sharing (TeamViewer) or SSH session. You should contact me by E-Mail (leo.moll@yeasoft.com) for details.
  2. This is really weird! I do not understand, why the startup file is not there. Can you please check sudo ls -la /etc/init.dp.S.: You can try to remove btsync and reinstall it: sudo apt-get -y remove btsyncsudo apt-get -y install btsyncIt's better not to use --purge, since it would kill /etc/btsync (with your configuration files) and /var/lib/btsync (which may contain a valid configuration).p.p.S.: If it was a new install and you do not risk to lose anything, you can also purge the old installation: sudo apt-get --yes ---purge remove btsyncsudo apt-get --yes ---purge autoremovesudo apt-get --yes install btsync
  3. ??? Try this: dpkg -l btsyncls -la /etc/init.d/btsyncand show me the output. This is really weird. Why you had to manually run dpkg-reconfigure?
  4. Fixed. Update available on YeaSoft's repository. Launchpad PPA, as usually, will take a few hours to update. btsync (1.4.0-2) unstable; urgency=low * Fixed installation error on systems with no configured default instance (Closes #147) -- Leo Moll <leo.moll@yeasoft.com> Tue, 02 Sep 2014 12:41:13 +0200
  5. Thank you! I was able to reproduce the problem. The fix will be released in a few minutes. See Issue #147 for more details.
  6. Can you please tell me which exact Distribution you are using?
  7. The packages have been published. Immediately available from YeaSoft's repository. Launchpad PPA will take a few hours. You can flag the topic as solved.
  8. Here it is! The long awaited update to 1.4. As usual it will take a few hours for people using the Launchpad PPA. The YeaSoft Repository is available immediately. Have fun! btsync-common (1.4.72-1) unstable; urgency=low * New upstream release * Removed special handling for GEODE cpu -- Leo Moll <leo.moll@yeasoft.com> Sun, 31 Aug 2014 14:28:13 +0200btsync-gui (0.8.4-1) unstable; urgency=low * Changed "synched" to "synced" to keep consistency (Closes #137) * Added Hungarian translation by Dávid Szilágyi (Closes #138) * Added experimental support for a set of dark icons for light themes (Closes #136) * Added support for new advanced configuration parameters of BitTorrent Sync 1.4 (Closes #146) -- Leo Moll <leo.moll@yeasoft.com> Thu, 01 Sep 2014 19:15:53 +0200
  9. Here it is! The long awaited update to 1.4. As usual it will take a few hours for people using the Launchpad PPA. The YeaSoft Repository is available immediately. Have fun! btsync-common (1.4.72-1) unstable; urgency=low * New upstream release * Removed special handling for GEODE cpu -- Leo Moll <leo.moll@yeasoft.com> Sun, 31 Aug 2014 14:28:13 +0200btsync (1.4.0-1) unstable; urgency=low * Add support for BitTorrent Sync 1.4 - Add support for SSL certificates (Closes #144) - Add support for folder default settings (Closes #145) * Fixed storage_path in order to allow sybolic linking (Closes #140) * Streamlined configuration data between configuration file and Web UI (Closes #142) * Removed deprecated setting lan_use_tcp (Closes #143) -- Leo Moll <leo.moll@yeasoft.com> Mon, 01 Sep 2014 12:00:00 +0200
  10. While adapting the btsync-gui to BitTorrent Sync 1.4 I discovered that the method get_prefs returns a plenty of new settings not visible in the Windows/Mac versions: {"bt.dl_queue_factor": "4","bt.extra_ul_max": "10","bt.extra_ul_rand": "128","bt.few_pieces_thres": "4","bt.http_pending_limit": "4","bt.prio_piece_thres": "20","bt.sequential_download": 0,"bt.sequential_files": 0,"bt.ul_queue_factor": "2","choker.interval": "10","choker.interval_auto": 1,"choker.interval_optim": "30","config_refresh_interval": "3600","connect_more_peers_interval": "1","device_name": "debpoldo - leo","disk_low_priority": 1,"diskio.rsize_factor": "16","download_limit": 0,"external_port": "0","folder_defaults.delete_to_trash": 1,"folder_defaults.known_hosts": "","folder_defaults.use_dht": 0,"folder_defaults.use_lan_broadcast": 1,"folder_defaults.use_relay": 1,"folder_defaults.use_tracker": 1,"folder_rescan_interval": "600","initial_install_version": "0","isp.peer_policy_date": "","isp.peer_policy_expy": "*1409589468","lan_encrypt_data": 1,"lang": 28261,"lang_iso": "en","listening_port": 62686,"log_size": "*10","max_file_size_diff_for_patching": "1000","max_file_size_for_versioning": "1000","net.diffserv_codepoint": "-1","peer.lazy_bitfield_factor": "24","peer.lazy_bitfield_mode": "0","peer.lazy_bitfield_nohave": "0","peer_expiration_days": "7","profiler_enabled": 0,"queue.started_bonus": "0","queue.switchtime": "60","queue.switchtime_prio": "300","rate_limit_local_peers": 0,"recv_buf_size": "10","reset_file_error_interval": "60","s_url": "","sdur": "0","send_buf_size": "10","sid1": "0","sid2": "0","sid3": "0","sid4": "0","sid5": "0","smaxage": "0","sminage": "0","smode": "0","ssamper": "0","state_notify_interval": "10","stitle": "","streaming.failover_rate_factor": "200","streaming.failover_set_percentage": "100","streaming.safety_factor": "110","sync_max_time_diff": "600","sync_state_with_peer_interval": "10","sync_trash_ttl": "30","ul_rate_download_thres": "0","update_peer_stat_interval": "10","upload_limit": 0,"upnp_cached_host": "","use_upnp": 1}Question Nr. 1: Does it make sense to display/support them in the GUI? Question Nr. 2: Is there any documentation for all these new settings?
  11. I'm about to release the new packages. Both the old btsync and btsync-gui packages should also work with a replaced btsync-core executable but you will get support for some new features only after the update.
  12. Since I'm about to release new versions of the btsync and btsync-gui package, it would be nice, if the volunteer translator can check if there are some new strings to translate. Thanks!
  13. If (as the name suggests) the supplied configuration file is the system (debconf) maintained configuration file for the default instance, it shows a serious anomaly. "storage_path" : "/home/r3m/public/btsync", The installer (debconf) creates the configuration file with the following value: "storage_path" : "/var/lib/btsync", Since there is no possibility to configure this value in debconf, this means that the file was changed manually. The comments at the top of the file say: // DO NOT EDIT THIS FILE MANUALLY - SERIOUSLY!!!//// THIS FILE WILL BE OVERWRITTEN AT EVERY UPDATE// OR RECONFIGURATION SO DO NOT EVEN TRY IT//// USE dpkg-reconfigure btsync INSTEAD TO MODIFY// THE CONFIGURATION Apart the fact that you blatantly ignored what was written there, the path you entered as storage_path seems not to be only a directory dedicated to keep all internal functional data of BitTorrent Sync. At least the name of the directory suggests that maybe that path is also one of your shared directories. In that case this will probably create a huge mess on your system and could be also the cause of several malfunctions. In case you specified in debconf NOT to create a default instance, and took only a previously created configuration file as template for your personal configuration, you should at least name it differently (e.g. myspecialconf.conf) in order to avoid conflicts with a subsequently created default instance (in fact your file would be overwritten). But please remember: storage_path is the location that BitTorrent Sync uses to store all internal data. It should be a dedicated directory not used by anything other and the BitTorrent Sync process must have full access to that directory.
  14. No - This is not the last version. Currently the last published version is 1.3.109 - 1.4.72 will follow in a few days when all integration tests have been finished. The reason you are stuck on 1.3.106 is that you are using an unsupported Ubuntu version and you are using the Launchpad PPA. Launchpad does not provide PPAs for unsupported Ubuntu versions (See the related Wikipedia article for a list of supported versions). Currently only 14.04 and 12.04 are fully supported. 10.04 is only supported as server version. Since your Ubuntu version does not get any more security updates, you are strongly advised to update to a supported version. If you instead want to continue using your outdated Ubuntu version (sometimes there are good reasons for this), you should switch to the YeaSoft Repository in order to get also the newer versions of the btsync packages.
  15. The repositories will be updated in a few days. I'm still testing the whole thing and making some modifications to the packages in order to make sure, everything works as expected. Generally there should be no compatibility issues between btsync 1.4 and btsync 1.3 installations, according to the release announcement: For Windows XP/Vista/Server 2003 users: DO NOT INSTALL SYNC 1.4 - it's not fully compatible with these operating systems at this time. Please use Sync 1.3.109 instead, which is fully compatible with Sync 1.4. Currently I'm working in a mixed environment: all my Mac machines are running 1.4 whilst my Linux machines are still running with 1.3.109
  16. First of all: there is no official package for Debian derived distributions. For the Linux platform BitTorrent Inc. provides only archives with the btsync executable for various architectures. You have to manage the whole installation manually. In any case here some advice: Before uninstalling the btsync-gui package, you must make sure, that known credentials are stored in the internal btsync status database. To do so, stop the btsync gui and than restart it from the command line by specifying the credentials you would like to use when connecting to the web interface. btsync-gui --bindui 0.0.0.0 --port 8888 --username WhatYouLike --password SuperSecret --savedefaults You can test if the credentials have been saved by connecting manually to the web UI with http://localhost:8888 Now you should stop btsync and uninstall everything: sudo apt-get --yes --purge remove btsync-guisudo apt-get --yes --purge autoremove Your entire btsync configuration will not be deleted. The internal database is stored in ~/.btsync Now you can download the suitable btsync archive from the official download location. After downloading it, you have to unpack the archive. In the archive you will find a file named btsync. Move this file to your home directory. If you launch it, it will find the configuration data from the previous version and use it.
  17. Needless to say, that I have exactly the same problem (DEB Packages). :-(
  18. I'm currently making a series of compatibility tests. The modularity of the Debian packages implies that the update of btsync-common to 1.4.72 affects the server version, the gui version and the legacy gui version. Before publishing the update I have to make sure, that all dependent packages (btsync, btsync-gui, btsync-gui-gtk and btsync-user) are working properly. Furthermore the specific download locations are still missing, making it impossible to generate/execute a reproducible build script. In addition the GEODE version is also missing... Regarding the GUI for Linux, there is a series of minimal adaptation that have to be done. First of all I have to add support for the new advanced configuration parameters and the new status codes. Additionally there are some small compatibility issues. In any case the new version of btsync-gui will still not offer all that new Share-via-Link stuff, since I still have no documentation about how it really works and there is still no documented API support for it. So stay tuned.
  19. I'm currently making a series of compatibility tests. The modularity of the Debian packages implies that the update of btsync-common to 1.4.72 affects the server version, the gui version and the legacy gui version. Before publishing the update I have to make sure, that all dependent packages (btsync, btsync-gui, btsync-gui-gtk and btsync-user) are working properly. Furthermore the specific download locations are still missing, making it impossible to generate/execute a reproducible build script. In addition the GEODE version is also missing... So stay tuned.
  20. The command and the configuration file setting will not work in your case. I suppose you took your information from the thread Debian And Ubuntu Server Unofficial Packages For Bittorrent Sync. All information in that thread is only related to the Debian/Ubuntu packages. Since your system is a QNAP NAS, I'm quite sure that you are using the btsync QPKG that is totally different from the Debian/Ubuntu package (that is not compatible with the QNAP OS and IMHO there is no way to install it on QOS).
  21. OK. Here are the bad news for you: you can not install anything more on your system. The reason is that your system is still running Ubuntu 11.10 (Oneiric Ocelot) that is not supported any more by canonical since 2013-05-09 and therefore Canonical has removed the package repositories. See the Liste des versions d'Ubuntu for details about Ubuntu versions and support periods. There are two excellent reasons to update/reinstall your system with a current version of Ubuntu: Since your system did not get any update since more than one year, it is highly vulnerable to hacker attacks. You have no chance to install anything new on your system.If your system is a server and you do not want to make a full update every 6 Months, you should take an LTS (Long Term Support) version of Ubuntu. he current LTS version is 14.04 and will be supported until April 2019
  22. OK - you have to install curl before (usually it is present on any system): sudo apt-get install curlWhen curl is installed you can redo sh -c "$(curl -fsSL http://debian.yeasof...repository.sh)" p.S.: do not forget to remove the server version of btsync.
  23. Interesting. And did you solve the missing package problem?