tuxpoldo

Members
  • Content Count

    730
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by tuxpoldo

  1. If you have installed btsync with the unofficial packages, run: apt-get dist-upgrade
  2. Please try to see what error is thrown when btsync is launched manually. First you have know under which user btsync runs (you have specified it when installing btsync). Then execute the following command: sudo -u <USERNAME> /usr/lib/btsync-core/btsync-core --nodaemon --config /etc/btsync/debconf-default.confwhere <USERNAME> is the user under which btsync will run.
  3. Yes! It was a bug (See Issue #179). I'm just uploading the updated version to the YeaSoft Repo. Launchpad will follow...
  4. According the documentation, the directory_root (and probably also the directory_root_policy statement) must be placed into the webui section.
  5. Ahhh OK - the Launchpad PPA was fully updated only a few hours ago...
  6. Wrong. THis may prevent future updates to work properly. I suppose that the btsync package on your side is still not up to date. Please check that the btsync package has the version 2.0.0-1 with the following command: dpkg -l btsyncWhich repository are you using?
  7. Just update the YeaSoft Repo. Because of an incompatibility between the new BitTorrent Sync executable and the Desktop GUI, I decided to distribute the new BitTorrent Sync executable in a new package "btsync-core". This makes it possible to update the BitTorrent Sync Server Package installations without compromising the BitTorrent Sync Desktop GUI Package installations (they will be updated later on, as soon as I have fixed the GUI). Unfortunately Ubuntu rewards changed package dependencies with yeasoft-gate2 ~ # apt-get upgradeReading package lists... DoneBuilding dependency treeReading state information... DoneThe following packages have been kept back: btsync0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. This is quite annoying but there are two ways to circumvent it: apt-get install btsync-core btsync or: apt-get dist-upgrade The second way may be dangerous, since it may install also other unwanted stuff... Do it only if you know what you are doing.
  8. Hi Folks, LAST WARNING - LAST WARNING - LAST WARNING - LAST WARNING I will update the btsync package in a few hours from now to version 2. This is your last chance to switch the repository in order to keep your installation on version 1.4. Beware: there is no easy way back. There are some implications due to the new functionality of Version 2.0: since version 2.0 has an automatic synchronisation of shared folders in a 2.0 identity, the directory_root parameter in the configuration file must point to writable directory, if you link your instance to another already configured 2.0 device. If you are operating a default instance maintained by debconf, directory_root is automatically set to the home directory of the user you selected as the user the instance is running. If the default user (btsync) or a user with a UID < 1000 was selected, /mnt is taken as directory_root and the owner of /mnt will be changed to the user. Obviously you can change the directory_root at any time via dpkg-reconfigure btsync. If you have self maintained configuration files, you should make sure a directory_root is specified, if you wish to link the instance to another device. Stay tuned.
  9. Do not do this now. The packages are still on 1.4.111 - if you have installed the latest official release you are on 2.0.83
  10. Just issue the following commands on your machine and you will return to the default repository: $(which sudo) rm -f /etc/apt/sources.list.d/tuxpoldo-btsync*.list /etc/apt/sources.list.d/btsync.listsh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync-repository.sh)" Yes. They are preserved and are still supported by 2.0 (you will see them as "1.4" folders). The only thing I do not know is if the 10-folder limit applies also to existing 1.4 folders....
  11. Hi Folks, in a few days (perhaps tomorrow) I will update the packages in the repositories to BitTorrent Sync 2.0. The discussion in the Server Package Topic has shown that there is a group of users that do not want to update to 2.0 and prefer staying on 1.4. In order to make this possible, a new repository has been created. If you want to stay on 1.4, you should read this message very carefully and follow the instructions below immediately, because I will publish the update to 2.0 in the next few days (perhaps tomorrow) and any old version will be updated if you do not change the repository. If you already have any BitTorrent Sync package installed: $(which sudo) rm -f /etc/apt/sources.list.d/tuxpoldo-btsync*.list /etc/apt/sources.list.d/btsync.listsh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync14-repository.sh)"If you want to install BitTorrent Sync 1.4 on a new machine: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync14-repository.sh)"
  12. OK Folks, the decision has been taken. BitTorrent Sync 1.4 will be made available in a separate repository. I just published the last update to 1.4 (1.4.111) and duplicated the repository. If you want to stay on 1.4, you should read this message very carefully and follow the instructions below immediately, because I will publish the update to 2.0 in the next few days (perhaps tomorrow) and any old version will be updated if you do not change the repository. If you already have any BitTorrent Sync package installed: $(which sudo) rm -f /etc/apt/sources.list.d/tuxpoldo-btsync*.list /etc/apt/sources.list.d/btsync.listsh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync14-repository.sh)"If you want to install BitTorrent Sync 1.4 on a new machine: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync14-repository.sh)"
  13. This was also one of the ideas I took in consideration. But unfortunately it has the same side effect as solution 2: only people that ready the forum will be informed that they have to install btsync2 /btsync2-gui in order to get an update. The internet will be still full of articles that tell the to "apt-get install btsync"
  14. Hi Folks, in the last days many people has asked about the new version, but there was also a plenty of users asking for a separate repo since they want to keep the 1.4 version. I'm still thinking about how I can satisfy all requirements. I'm still quite unsure on how to proceed: every option has advantages and disadvantages: Update all packages to the new version: this will make all people that want to stay on 1.4 unhappy and additionally will make it hard for them to roll back to an old version Create a new repository for Version 2/Name the packages for Version 2 differently: this will make all people unhappy that wants to update to version 2 since the majority of them do not know about the new repository/the new package name. There is a plenty of blog articles, news and howtos with information about the btsync repository. If people search google for btsnyc and linux, they will still find all that outdated information. Create a new repository for Version 1.4 and update the standard repository to version 2: this would give people that want to stay on 1.4 a chance to do so and also to install 1.4 from scratch. But in order to avoid the automatic update to 2.0 they have to manually switch the repository.Personally I would prefer the solution 3. In any case I will try to release the new stuff on Sunday. So please stay tuned for news, especially if you want to keep your stuff on 1.4... Please share your opinions about the update strategy here in the forum.
  15. Yes. The GUI is running. You should see an indicator icon and you should be able to invoke the UI via the indicator menu. If you do not see the btsync indicator icon, you should try to run the ui from the command line and see if any error message is produced. Here an example: leo@debpoldo ~ $ btsync-gui --log INFOINFO:root:Starting btsync agent...By using this application, you agree to our Privacy Policy, Terms of Use and End User License Agreement.http://www.bittorrent.com/legal/privacyhttp://www.bittorrent.com/legal/terms-of-usehttp://www.bittorrent.com/legal/eulaBitTorrent Sync forked to background. pid = 15653. default port = 8888INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Refresh status...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Refresh status...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Refresh status...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Refresh status...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Refresh status...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostINFO:root:Shutting down application...INFO:root:Stopping btsync agent...INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): localhostleo@debpoldo ~ $ btw: it is OK that the configuration file is missing. It is deleted immediately after launch. You are posting in the wrong forum. You issue seems related to the Server Version of the package. I suppose, you have installed the server version and than replaced the original btsync executable with the 2.0 one. I have bad news for you: There is no way back, since the internal database is not compatible. The only way to work again with 1.4.x is to remove entirely the database created by 2.0.x (you will probably find it in /var/lib/btsync).
  16. I've just updated the btsync-common package. But it will take one or two hours to publish....
  17. It is a feature and you should read the documentation (e.g. the first posting in this thread) to understand how it works. In any case: look at the beginning of the file //!/usr/lib/btsync/btsync-daemon --config//// Default instance automatically created by debconf//// 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 CONFIGURATIONThe file is created, because on the initial installation you chose that you want debconf to maintain a default instance. If you do not want this, or you want to reconfigure your default instance, you have to execute dpkg-reconfigure to change this behaviour. Since you prefer to maintain you own configuration file, please execute: dpkg-reconfigure btsyncand answer no to the first question ("Do you want to define a default BitTorrent Sync instance?").
  18. Hi there, you are posting in the wrong thread. Since this issue may be of interest also for other people, I would kindly ask you to post the message again in Debian And Ubuntu Server Unofficial Packages For Bittorrent Sync (the most easy way: click edit on your message, than switch to text mode in the editor - it's the first icon on the top left - select all, copy and paste it in the editor of the new thread). Please add also the information which distribution you are exactly using.
  19. I'm pleased to announce a new version of the BitTorrent Sync server package. Users of the YeaSoft repository will get the new package immediately. Users of the Launchpad PPA have probably to wait for a few hours... btsync (1.4.1-1) unstable; urgency=low * Removed check for mandatory disablement of misinterpreted "check_for_updates" setting (Closes #170) * Fixed redundant restart messages (Closes #166) * Added support for modular configuration files (Closes #124) * Updated debconf localisation from poeditor.com - Thanks to all volunteers -- Leo Moll <leo.moll@yeasoft.com> Sat, 06 Dec 2014 14:52:11 +0100
  20. You have some syntax errors in your configuration file. Remove the comments after the secret and the comma after the folder. The resulting file should look like: //!/usr/lib/btsync/btsync-daemon --config//// DAEMON_UID=btsync// DAEMON_GID=btsync// DAEMON_UMASK=002{ "storage_path" : "/var/lib/btsync/", "check_for_updates" : false, "display_new_version": false, "disk_low_priority" : true, "lan_encrypt_data" : true, "rate_limit_local_peers" : true, "folder_rescan_interval" : 600, "folder_defaults.delete_to_trash" : true, "folder_defaults.use_dht" : false, "folder_defaults.use_lan_broadcast" : true, "folder_defaults.use_relay" : true, "folder_defaults.use_tracker" : true, "folder_defaults.known_hosts" : "","shared_folders" : [ { "secret" : "****", "dir" : "/folder/" } ]}
  21. There was no need to disable the UI: the Linux version only has the Web UI and no other component. You're welcome to use all of my code/scripts, since it is Open Source. You will find everything you need on the GitHub project page.
  22. You are in the wrong thread. This thread applies to the Debian/Ubuntu and derived distributions packages. Please ask your question in the BitTorrent Sync for NAS forum. Since the indicator is not supported any more by the originating developer, there will be no more versions of the btsync-user package. You can upgrade to the newer btsync-gui package (See related thread) or wait for the next version of btsync-gui that will be installed automatically for people still on btsync-user. Yes. You can do that. But if you are talking about the Debconf-maintained default instance, there is no device_name setting any more in the configuration file. You can change the device name directly from the Web UI. Sorry for that. Mainly this is due to two factors: I have a new job and (as usual) it's a 12-14 hours job. And as a consequence my spare time is very reduced. In the last weeks I had a lot of trouble with a bereavement in my family.