Arch Linux User Repository

Thanks coolpyrofreak. Seems to have updated fine. Though I am not a fan of the new interface.

@cb474 - I set the PKGBUILD for this to conflict with the original spideroak package, so pacman should prompt you to remove spideroak before installing spideroak-one. Based on my experience, it should be a seamless transition and you shouldn't lose anything, but YMMV.

So when I install this will it automatically replace 5.2 from old AUR? Do I have to uninstall 5.2 first? Am I going to lose my settings and have to set up SpiderOak all over again? Thanks for any details on that. And thanks for maintaining and upgrading the package.

SpiderOak 6.0 is out, and this is a pretty major upgrade. Besides a new UI, new features, and bug fixes, SpiderOak has changed the name of this product (and the name of the binary) to SpiderOakONE to differentiate it from their Groups and Enterprise products. I'm changing the name of the package to spideroak-one to keep in line with this convention, and will merge the existing package to it. Groups or Enterprise would have to be a separate PKGBUILD, with the source obtained from SpiderOak directly. For both of those, some signup and interaction with the SpiderOak sales team is necessary before you can get the install file. In a minor change, I've changed the install file to the .deb file in order to clean up the PKGBUILD. It should build the same without any issues. I've also removed the CLI link from the install file and replaced it with the link to the release notes. Please let me know if you have questions. My email is in the PKGBUILD. Thanks!

@infinitezero Still sounds like an upstream issue to me. Either SpiderOak needs to rebuild the RPM source, or you need to recompile the PKGBUILD. I don't intend to be rude, but I don't really want to re-write the PKGBUILD for the .deb source just because one user is having an issue.

I did, see part of their response below. "The errors I was seeing were indicating that the process which scans your file system was crashing. There are differences in the libraries used by the rpm vs deb builds which caused the directory watcher to crash."

@infinitezero: Sounds to me like an upstream issue. You really should contact the developers: https://spideroak.com/help/

Makes me wonder if this is a marriage issue between the .rpm and Gnome 3.

I have a fix for the issue. The variable that is different, is the package used to create the AUR version, it is from the .rpm, not the .deb. Make sure you have uninstalled the previous SpiderOak install from the AUR. 01. Install deb2targz: $ pacaur -Syu deb2targz 02. Download current .deb from SpiderOak: 03. Convert: $ deb2targz spideroak_5.2.0_amd64.deb 04. Decompress: $ tar -xzvf spideroak_5.2.0_amd64.tar.gz 05. Copy the following newly created directories (etc, usr, opt) as follows: $ sudo cp -r etc/ / $ sudo cp -r usr/ / $ sudo cp -r opt/ / 06. Start SpiderOak and set it to, "Launch SpiderOak at OS Startup" $ SpiderOak ## Is case sensitive. 07. Reboot Now SpiderOak will automatically scan for changes like it should.

I have noticed over the last 5 months or so SpiderOak does not automatically (or if you set a time) scan the directories for changed files and upload them. I have not seen this issue with other distros running SpiderOak (for example Debian 7 & 8 and Ubuntu 14.04.2), only Arch, is there a fix for it? I have seen the same symptom on two different fresh Arch installs, and two different (fresh) installs of SpiderOak, include the most current 5.2.0. If I make a change a to file, or add a new file, SpiderOak does not detect it (not scanning for changes) unless I manual tell it to scan, or kill it and then restart it. I have even set it to backup every 5 minutes and it still does not scan for changes. All distros running gnome-shell. There is at least one other user experiencing the same issue. https://bbs.archlinux.org/viewtopic.php?pid=1529938#p1529938