• Content Count

  • Joined

  • Last visited

About jaapp

  • Rank
    New User
  1. Hey man, it's cool. I was just pointing this out to help you make your product even better. I'm a very happy btsync user, and your work regarding the packaging is absolutely vital and well appreciated. The phrase "Waste some time" was only used to build a case why the message was a "small nuisance". I assumed you where interested in some basic UX-feedback.No need to blow a fuse. You might scare off the next bug reporter.
  2. I had the same upgrade experience as michaelarnauts. It's a small nuisance, that caused me to waste some time trying to verify that I wasn't running two instances.
  3. I use btsync mainly for sharing files and for backup. For my phone it has rid me of using an USB cable for data transferring. I have synced my entire SDCard to a network share on a NAS. If I want to change some MP3's or video's on my phone, I just alter the network share and my NAS will then sync those changes to my phone. I always have my phones photos in reach. If I need to alter some config files of a random Android app, I use a text editor on a laptop. It's perfect. I love it.
  4. Thanks for the reply. Changed the repository and the updated package works like a charm.
  5. I just tried to update my btsync installation to version 1.4.0-1. it failed. After the installation the webui still shows version 1.3.109 Here is the result from my shell: username@hostname:~$ sudo apt-get upgradeReading package lists... DoneBuilding dependency treeReading state information... DoneCalculating upgrade... DoneThe following packages will be upgraded: btsync btsync-common libpam-systemd libsystemd-daemon0 libsystemd-login0 libudev-dev libudev1 rsyslog systemd-services udev10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.Need to get 7066 kB of archives.After this operation, 562 kB of additional disk space will be used.Do you want to continue? [Y/n]Get:1 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main udev amd64 204-5u buntu20.5 [734 kB]Get:2 http://ppa.launchpad.net/tuxpoldo/btsync/ubuntu/ trusty/main btsync-common amd64 1.4.72-1 [5586 kB]Get:3 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main libudev-dev amd64 204-5ubuntu20.5 [25.2 kB]Get:4 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main libudev1 amd64 20 4-5ubuntu20.5 [33.2 kB]Get:5 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main libpam-systemd am d64 204-5ubuntu20.5 [25.5 kB]Get:6 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main systemd-services amd64 204-5ubuntu20.5 [197 kB]Get:7 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main libsystemd-daemon 0 amd64 204-5ubuntu20.5 [9698 B]Get:8 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main libsystemd-login0 amd64 204-5ubuntu20.5 [26.7 kB]Get:9 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main rsyslog amd64 7.4 .4-1ubuntu2.1 [353 kB]Get:10 http://ppa.launchpad.net/tuxpoldo/btsync/ubuntu/ trusty/main btsync all 1 .4.0-1 [75.1 kB]Fetched 7066 kB in 0s (9290 kB/s)Preconfiguring packages ...(Reading database ... 260279 files and directories currently installed.)Preparing to unpack .../udev_204-5ubuntu20.5_amd64.deb ...Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'Unpacking udev (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../libudev-dev_204-5ubuntu20.5_amd64.deb ...Unpacking libudev-dev (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../libudev1_204-5ubuntu20.5_amd64.deb ...Unpacking libudev1:amd64 (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../libpam-systemd_204-5ubuntu20.5_amd64.deb ...systemd-logind stop/waitingUnpacking libpam-systemd:amd64 (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../systemd-services_204-5ubuntu20.5_amd64.deb ...Unpacking systemd-services (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../libsystemd-daemon0_204-5ubuntu20.5_amd64.deb ...Unpacking libsystemd-daemon0:amd64 (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../libsystemd-login0_204-5ubuntu20.5_amd64.deb ...Unpacking libsystemd-login0:amd64 (204-5ubuntu20.5) over (204-5ubuntu20.4) ...Preparing to unpack .../btsync-common_1.4.72-1_amd64.deb ...Unpacking btsync-common (1.4.72-1) over (1.3.109-1) ...Preparing to unpack .../btsync_1.4.0-1_all.deb ... * Stopping btsync instance 'btsync' * Failed to stop btsync instance btsyncUnpacking btsync (1.4.0-1) over (1.3.1-1) ...Preparing to unpack .../rsyslog_7.4.4-1ubuntu2.1_amd64.deb ...Unpacking rsyslog (7.4.4-1ubuntu2.1) over (7.4.4-1ubuntu2) ...Processing triggers for ureadahead (0.100.0-16) ...Processing triggers for man-db ( ...Processing triggers for hicolor-icon-theme (0.13-1) ...Setting up libudev1:amd64 (204-5ubuntu20.5) ...Setting up udev (204-5ubuntu20.5) ...udev stop/waitingudev start/running, process 20911Removing 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'update-initramfs: deferring update (trigger activated)Setting up libudev-dev (204-5ubuntu20.5) ...Setting up libsystemd-daemon0:amd64 (204-5ubuntu20.5) ...Setting up systemd-services (204-5ubuntu20.5) ...Setting up libpam-systemd:amd64 (204-5ubuntu20.5) ...systemd-logind start/running, process 20986Setting up libsystemd-login0:amd64 (204-5ubuntu20.5) ...Setting up btsync-common (1.4.72-1) ...Setting up btsync (1.4.0-1) ...Installing new version of config file /etc/init.d/btsync ...dpkg: error processing package btsync (--configure): subprocess installed post-installation script returned error exit status 1Setting up rsyslog (7.4.4-1ubuntu2.1) ...Installing new version of config file /etc/rsyslog.conf ...The user `syslog' is already a member of `adm'.Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogdrsyslog stop/waitingrsyslog start/running, process 21167Processing triggers for libc-bin (2.19-0ubuntu6.3) ...Processing triggers for initramfs-tools (0.103ubuntu4.2) ...update-initramfs: Generating /boot/initrd.img-3.16.1-031601-genericProcessing triggers for ureadahead (0.100.0-16) ...Errors were encountered while processing: btsyncE: Sub-process /usr/bin/dpkg returned an error code (1)username@hostname:~$ sudo service btsync stop * No btsync instance is running.username@hostname:~$ apt-cache policy btsyncbtsync: Installed: 1.4.0-1 Candidate: 1.4.0-1 Version table: *** 1.4.0-1 0 500 http://ppa.launchpad.net/tuxpoldo/btsync/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status
  6. Well, I was talking about updates wasn't I..
  7. From the manual: Read only secret is generated on the basis of the master secret and is used for one-way synchronization. It means that any folder with a read-only secret will be fully synced, but changes made in it will not be reflected in the folders operated by a master secret. Also, it is not possible to change secret for read only folders.
  8. Gio, you don't want to have a RO folder in that scenario at all. You need to see RO folders as one way streets: They can be updated, but they never update other machines. If you make the folder on the server RO it will only accept updates from other machines, but never propagate these updates. In your case you want: Client1 (RW) <-> Server (RW) <-> Client2 (RW) Not: Client1 (RW) -> Server (RO) <- Client2 (RW) Otherwise Client1 and Client2 will never update each other unless they are both online at the same time.
  9. Lolcat, i assume OP is looking for the "restore modified files to original version" option, which you can find the web interface under the folder preferences in the advanced tab. OP wants to know how to configure this without a (web) gui. Which is a perfectly reasonable question. Afaik this configuration setting is not documented.