Package Details: crashplan 4.7.0-4

Git Clone URL: https://aur.archlinux.org/crashplan.git (read-only)
Package Base: crashplan
Description: An online/offsite backup solution
Upstream URL: http://www.crashplan.com
Keywords: backup crashplan
Licenses: custom
Submitter: billyburly
Maintainer: georgyo
Last Packager: georgyo
Votes: 122
Popularity: 1.810230
First Submitted: 2011-09-17 03:06
Last Updated: 2016-07-20 15:07

Latest Comments

georgyo commented on 2016-09-22 23:27

It's a crashplan thing, if you can figure out why it creates it, let me know.

The pid inside the file is also wrong, the correct pid is in /opt/crashplan/CrashPlanEngine.pid. It creates that pid in it's working directory by default. It wouldn't be too hard to move to a standard location. I'll test that out in a bit.

Sparticuz commented on 2016-09-22 20:49

Crashplan seems to be putting it's pid into /usr instead of /run. Is that an aur thing or a Crashplan thing?

jasonhansel commented on 2016-08-22 02:29

@timemaster did you manage to create a PKGBUILD that allows CrashPlan auto-update? It might be useful to post it here (or even submit it to the AUR)

georgyo commented on 2016-08-09 00:48

I really can't explain why the checksum is failing for so many people. I still can't reproduce. It keeps failing because its doing the checksum against the bad version cached by your AUR helpers. However, how so people downloaded a bad tar ball is puzzling me.

timemaster commented on 2016-08-09 00:22

probably a permission issue. when using official crashplan install script, it install crashplan run as root and can update itself, at least what I think after today installation. I am also tired of this, because for 2 weeks the checksum on the crashplan zip file of this package failed and the current installation did not work as not updated. I

jasonhansel commented on 2016-08-06 18:45

Whenever CrashPlan releases a new version, I get emails saying that my backup hasn't fully completed until I perform the upgrade. While I know that this violates the usual package-management philosophy, I'm wondering if it's possible to have a crashplan package that *enables* automatic update, in order to avoid this issue. Does anyone know how CrashPlan's auto-update feature works, so that I could create such a package?

trimalchio commented on 2016-07-20 22:06

Sorry I guess I should have mentioned I'm using pacaur. I cleared my cache as @tmoorge suggested and it's working now. Thanks!

tmoore commented on 2016-07-20 17:38

@DrTeeth
You may need to clean out your pacaur cache directory.
rm -rf ~/.cache/pacaur

georgyo commented on 2016-07-20 15:14

It's possible that they are doing A B testing... I can't get the error, I have tried pacaur, yaourt, makepkg, and 10 iterations of clean-chroot-manager. Every single time it downloads the file and passes the checksum.

DrTeeth commented on 2016-07-20 15:03

@trimalchio @georgyo

When trying to update crashplan using pacaur -Syu, I get

==> Validating source files with sha256sums...
CrashPlan_4.7.0_Linux.tgz ... FAILED

However, when I download crasplan from the aur directly and run "makepkg -sri ", it installs with no problems.


All comments