Arch Linux User Repository

Package release 2 incorporates a mechanism to allow us to signal to each other when there is a new release. When the md5sum of the downloaded file changes, the first one of us to build SpiderOak will get this output message: "Please raise the out-of-date flag for this package: http://aur.archlinux.org/packages.php?ID=24401" This is necessary because upstream has chosen not to include the version number into the structure of the download link. When you flag the package out-of date, I will recompute the md5 sums, increment the pkgrel by one and resubmit the package. I think this is the best we can do - help each other if upstream won't help us.

Are you updating this package without updating the REL inside PKGBUILD? I notice the last update is fairly recent but if you don't increase that number, it won't register for us that we need to update.

This package really should have the version numbers on there. The Linux client doesn't auto-update like others, so just putting "latest" as the version number means that the package won't update unless one manually checks.

The only thing you can really do is email SpiderOak customer support, like I did, and let them know you want a tar.gz tarball for installation on distros that don't use RPMs or .debs. For now, the .deb works fine for installation. Thanks for maintaining it!

ahh yes, I should have seen that with the slackware packages.

The Slackware package won't work because it's only available for 32-bit.

Another thought, it looks like you didn't update rel version, so that even though the md5's are correct, nobody will be notified a fix is out. This may be intentional though.

1) dbus is still an optional dep vs an actual dep because the CLI does not need it. 2) they have released a 'slackware' build recently, that amounts out to a .tar.gz that could simply be cp'd from src -> pkg. This would be a cleaner way to install this app as it is more platform agnostic then debian.

updated & disowned since i don't use spideroak regularly.