Package Details: spideroak-one 7.5.0-1

Git Clone URL: (read-only)
Package Base: spideroak-one
Description: Secure file backup, sync and sharing client. This provides the client for SpiderOakONE.
Upstream URL:
Keywords: backup
Licenses: custom
Conflicts: spideroak, spideroak-beta
Provides: spideroak
Replaces: spideroak
Submitter: coolpyrofreak
Maintainer: coolpyrofreak
Last Packager: coolpyrofreak
Votes: 273
Popularity: 0.243191
First Submitted: 2015-07-18 19:17
Last Updated: 2019-02-15 03:12

Pinned Comments

coolpyrofreak commented on 2018-09-13 02:34

Upstream support for 32-bit on Linux has ended, so I'm removing it from the PKGBUILD. The article below has more information, and download links to the last 32-bit versions.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

coolpyrofreak commented on 2017-01-10 15:31

@iegubkin - All I can tell you is that I can't reproduce your error. harfbuzz isn't a dependency, so it sounds like an upstream problem to me. You should contact SpiderOak support directly.

iegubkin commented on 2017-01-10 00:21

I'm confused. I re-installed the package and it gives the same error.

$ wget -c
$ tar -xvzf spideroak-one.tar.gz
$ cd spideroak-one
$ makepkg -s
# pacman -U *.pkg.tar.xz

Is this what you meant by "you might want to try re-running makepkg with a fresh git clone"? Thanks

coolpyrofreak commented on 2017-01-08 03:25

@iegubkin - I'll try to figure this out tomorrow. It's entirely possible we'll need an upstream fix, though.

EDIT - Just rebuilt the package with updated harfbuzz package, and it seems to be working fine. It executes from CLI without any errors, so you might want to try re-running makepkg with a fresh git clone.

iegubkin commented on 2017-01-08 03:12

The recent update of harfbuzz 1.3.4-1 to 1.4.1-1 seems to have killed spideroak-one. It crashes with:

>> SpiderOakONE
Traceback (most recent call last):
File "<string>", line 6, in <module>
File "", line 128, in <module>
File "", line 183, in <module>
File "", line 168, in main
File "oak/", line 21, in <module>
File "PyQt4/", line 26, in <module>
File "PyQt4/", line 17, in _bbfreeze_import_dynamic_module
ImportError: /usr/lib/ undefined symbol: FT_Get_Var_Blend_Coordinates

Similar to bug with Zim Desktop:
"needs to be rebuilt against the new harfbuzz lib"

downgrading back to 1.3.4-1 fixes the problem.

coolpyrofreak commented on 2016-06-03 01:34

I'm thinking about renaming this package to spideroakone (removing the hyphen) so that the package name is the same as SpiderOak's naming conventions. While it's not a big change, I wanted to advertise it before I made any changes. I'd appreciate any comments or thoughts anyone might have on this. Thanks!

scachemaille commented on 2016-04-25 21:52

A new version is out.
The download link point to newer version 6.1.4 so the sha256sums is not valid anymore.

coolpyrofreak commented on 2016-03-11 23:56

@cfr42 - Sorry, I just have a habit of always using the -v flag with tar. I removed it from the PKGBUILD, so you should see a much cleaner build now.

cfr42 commented on 2016-03-11 22:24

Great to see the update - thanks for this. May I make the quite minor suggestion that the change to the package build which makes untarring the package verbose be undone when you next update? As far as I know, PKGBUILDs do not normally do this and I can't, to be honest, see the point. If there is a point, I think maybe adding a message explaining what users should look for in the output would be useful as it really isn't clear to me *why* I'm being given all this information, which makepkg does not provide for any other packages I've built! And apologies if this suggestion is off-base in some way. I realise you made the change for a reason, even if I cannot currently appreciate that reason.

lockheed commented on 2016-03-10 09:36

==> Validating source files with sha256sums...
terms.txt ... Passed
==> Validating source_x86_64 files with sha256sums...
spideroakone_6.1.2_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check

It's probably because the scripts downloads newer version 6.1.3

cfr42 commented on 2016-02-06 00:41

No worries - seems happy enough to build now ;).