Package Details: spideroak-one 7.5.0-1

Git Clone URL: https://aur.archlinux.org/spideroak-one.git (read-only, click to copy)
Package Base: spideroak-one
Description: Secure file backup, sync and sharing client. This provides the client for SpiderOakONE.
Upstream URL: https://crossclave.com/
Keywords: backup
Licenses: custom
Conflicts: spideroak, spideroak-beta
Provides: spideroak
Replaces: spideroak
Submitter: warnem2
Maintainer: mbc
Last Packager: mbc
Votes: 269
Popularity: 0.004194
First Submitted: 2015-07-18 19:17 (UTC)
Last Updated: 2023-09-04 21:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 27 Next › Last »

<deleted-account> commented on 2011-09-15 12:54 (UTC)

@MartinZ extremely tacky way to get some free space.

mzecher commented on 2011-09-15 02:06 (UTC)

Thanks a lot for the package. For the new users how don't know, you may register with a referral link (this is mine: https://spideroak.com/download/referral/dd6b3051b5f1f10a5674d694f22dd3e8) and the Promo Code "worldbackupday" to begin with 6GB instead of the regular 2GB.

polslinux commented on 2011-09-10 08:23 (UTC)

9849 is out!

dserban commented on 2011-08-25 10:53 (UTC)

@sschober, try the Fedora-based version of this PKGBUILD: http://pastebin.com/raw.php?i=6FH2JzCr Let me know if this one is also segfaulting for you.

sschober commented on 2011-08-25 09:37 (UTC)

segfaults for me, when clicking on the backup->advanced button :/ See the full stacktrace here: https://gist.github.com/1170277

dserban commented on 2011-06-28 10:43 (UTC)

@mond, my observations: 1) Hardcoding the revision number into the PKGBUILD almost by definition guarantees that at some point the build process is going to retrieve out-of-date software from upstream. We wouldn't do that with *-git / *-svn / *-bzr packages, and so we won't do that with SpiderOak either. Upstream is essentially a version control system that has been enhanced to spit out a .deb file on demand, and IMO the PKGBUILD must reflect the VCS nature of upstream. 2) Replacing static libraries with their Arch-native equivalents is technically infeasible in SpiderOak's case because the SpiderOak binary incorporates the entirety of some version of Python. What you are suggesting would be possible were SpiderOak open-source and with python2 as a dependency. 3) I have added the .install file.

<deleted-account> commented on 2011-06-27 21:16 (UTC)

Hi, I think I made this PKGBUILD a lot more standard conform and removed more Debian/Ubuntu stuff. http://dl.dropbox.com/u/1715256/spideroak-9823-1.src.tar.xz Also what do you think about replacing most of the static libraries with the packages from extra/community?

cb474 commented on 2011-06-23 17:21 (UTC)

Thanks.

dserban commented on 2011-06-23 09:21 (UTC)

@cb474: My bad. Fixed.

cb474 commented on 2011-06-23 08:03 (UTC)

I'm not sure if this problem is caused by the PKGBUILD, but I noticed that when spideroak is installed, the shell script that launches it is called "spideroak," instead of "SpiderOak" as it used to be, with the capitals. There's a line in the PKGBUILD that seems to assign this name: "USRBINFILE="${pkgdir}"/usr/bin/spideroak". This causes a problem (at least in Gnome) if you set spideroak to launch at login, from the spideroak preferences. Spideroak automatically creates an entry in the Gnome Startup Applications, where it expects to launch spideroak with the command "/usr/bin/SpiderOak" with the capital "S" and "O". So the launch fails. Should the line in the PKGBUILD read "USRBINFILE="${pkgdir}"/usr/bin/SpiderOak" in order to work properly with the way spideroak is internally configured? Thanks.

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 27 Next › Last »