Package Details: sparkleshare-git 2.0.1.r115.g69b0736f-1

Git Clone URL: (read-only, click to copy)
Package Base: sparkleshare-git
Description: An open-source clone of Dropbox, written in C-sharp
Upstream URL:
Licenses: LGPL
Conflicts: sparkleshare
Provides: sparkleshare
Submitter: None
Maintainer: melchips
Last Packager: melchips
Votes: 20
Popularity: 0.000000
First Submitted: 2010-08-10 17:33
Last Updated: 2018-03-28 10:15

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

yiuin commented on 2013-06-19 18:20

I'm getting the following error when I try to start sparkleshare:
Starting SparkleShare... Done.
Error setting attribute: Setting attribute metadata::custom-icon-name not supported

Anyone else have this problem? It seems like maybe some gnome icons or gnome icon methods are required.

melchips commented on 2013-06-16 22:19

Patch has been removed from the PKGBUILD, as it was merged upstream.

melchips commented on 2013-06-16 22:18

As the error has been fixed upstream, the patch has been removed from the PKGBUILD.

melchips commented on 2013-06-16 22:08

@CrashLog :
Thanks for reporting, I made a pull request to fix the error upstream (see

I've included the matching patch in the PKGBUILD while it's not fixed upstream.

@eliasson :
Thanks for enlightening me on this topic.
I've now removed the depth option. People wanting shallow clones can always alter the PKGBUILD accordingly...

Crashlog commented on 2013-06-15 22:15

I get an error when I try to build this.
./SparkleBubbles.cs(58,21): error CS0103: The name `Logger' does not exist in the current context

eliasson commented on 2013-06-09 14:42

Shallow git clones are not at all the answer to the question of life, the universe, and everything. Their only benefit are some bandwidth savings on the *initial* clone. Updating a full repository will be much faster than updating a shallow one. Clones should only be done once on well-configured systems that keep the sources between builds and git packages are by definition unstable development versions that change often. Thus, updates are what matters in the long run. Shallow builds only make sense if you use tools like yaourt that throw away the sources for no reason after building the package.

See and for more discussions on this topic.

melchips commented on 2013-05-21 08:37

As the upstream repository has been merged with the fix, the patch has been cleared out of the PKGBUILD.

melchips commented on 2013-05-21 07:59

Thanks for the building error report yiuin.

I made a pull request to the Github project repository to fix the error upstream (see

In the meantime, I altered the PKGBUILD with the matching patch.

yiuin commented on 2013-05-20 20:55

Doesn't build since commit c4ccaaef681f876be81f5b8db5bc0454546c1493, there is an issue:
./../SparkleInvite.cs(69,50): error CS0103: The name `HttpUtility' does not exist in the current context

it seems like you need
using System.Web.Services;
but that doesn't work either, I don't know enough about mono to fix it.

melchips commented on 2013-03-18 17:50

Package updated with the good suggestion of tjbp (thanks by the way ^^)