Arch Linux User Repository

Hello, installation on x86 fails; checksum isn't correct: ==> Retrieving Sources... -> Downloading spideroak_4.8.3_x86_64.rpm... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 19.5M 100 19.5M 0 0 1960k 0 0:00:10 0:00:10 --:--:-- 3104k -> Found terms.txt ==> Validating source files with sha1sums... spideroak_4.8.3_x86_64.rpm ... FAILED terms.txt ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build spideroak. ==> Restart building spideroak ? [y/N] ==> ---------------------------------- ==>

A couple of comments re: the PKGBUILD: - Why are you using the RPM package when you have a nice tarball available at https://spideroak.com/directdownload?platform=slackware&arch=i386 which is much easier to use? - It would be helpful to link to this post-install: https://spideroak.com/faq/questions/1017/ - Why don't you install the manpage and copyright notice provided by the package? - You don't seem to be copying etc/xdg/* - The occurrences of install could be simplified to just copying the slackware tarball in its entirety. Other than that, thanks for packaging this - its extremely useful.

Updated.

The sha1sum fails for the package fetched from spideroak. Also, there is a newer version available. ps. Thanks for packaging this.

The correct version should actually be 4.7.9948.

Well I started off with just SpiderOak --headless --verbose and it didn't do much. I figure this is because it had nothing to do. So I ran: SpiderOak --headless --verbose --backup <dir> for a couple of directories and this seemed to go OK. It's very slow but it seemed to finish. To check this, I tried: SpiderOak --headless --verbose --fulllist I got: Status: Waiting for initial updates from server and it sat there. To try to get a sense of how long, I cancelled it and reran it under time. It has now been sitting there for over 90 minutes. Have I misunderstood what this command should do? I expected it to just give me a list of the stuff backed up... I guess this is because it doesn't like to be asked for --headless with --fulllist. I thought --headless just told it not to spawn the GUI. Anyway, I'll try the GUI again in a bit. I'm not sure why it is quite so slow. My connection is reasonable so it isn't that.

Guys, please. This is not the place for those discussions. Please open a thread in the forum. These comments are meant for direct feedback to the package maintainer.

Thanks for responding. Sorry. I should have specified that I emailed spideroak's support - not Arch. I'll try with the headless version. Given that spideroak has a dependency on qt, it would be surprising if it worked with gnome etc. but not kde, wouldn't it? Unless the database became almost instantly corrupted, that's an unlikely explanation as I'd only just started to use it. The resource usage I mentioned was definitely *not* within a normal range. It only happened after I rebooted but it went truly insane. It pushed my temperatures as high as I've ever seen them - higher than when I'm using all cores flat out to generate a fractal, for example. Much higher than when I back up my entire drive to external disk. Since it had no reason to actually be doing anything at all (except checking nothing had changed to the few things I'd assigned to back up), I can't believe it behaves this way for other people else nobody would be able to use it. I have openssl installed already.

@cfr42, try to debug running it on cli: "SpiderOak --headless --verbose". Maybe the database is corrupted and you need to rebuild it. If everything is ok, the problem may be KDE compatibility, because there's no problem in my Gnome.