Package Details: diaspora-mysql-git

Git Clone URL: (read-only)
Package Base: diaspora-git
Description: A distributed privacy aware social network (development head) (MySQL)
Upstream URL:
Licenses: AGPL3
Conflicts: diaspora, diaspora-mysql, diaspora-postgresql, diaspora-postgresql-git
Submitter: Splashy
Maintainer: jhass
Last Packager: jhass
Votes: 26
Popularity: 0.000000
First Submitted: 2010-09-16 19:31
Last Updated: 2016-02-24 11:34

Latest Comments

jhass commented on 2015-12-16 22:03

Thanks for the pointer, the package actually always patched the version in the config with the commit sha, however we changed how we version the development version and that patch broke. I just replaced it with a more robust version, so that should work again.

If your pod correctly shows the configured services on /statistics, /statistics.json and /nodeinfo/1.0, then the issue for not displaying them is at

andrej commented on 2015-12-16 15:00

Just a small improvement idea: Could the package possibly contain a relevant part of the Git repo? I mean, not the repo in its entirety with all the commits and branches, but at least something that works with 'git status'.

The reason for having a bit of .git in the package is this part of code that generates the version string:

If the .git repo is unavailable, the version string either isn't there or looks odd and David Morley's site doesn't like that. (Sometimes the version field is just empty, but it has already happened that the pod wasn't listed at all because of that.)

<likely_unrelated>Also there appears to be some magic powder for announcing extensions (wordpress, facebook, twitter, tumblr) which my pod is missing. It supports all the extensions, yet none of them are shown on</likely_unrelated>

Anyway, many thanks for maintaining this package. It's awesome how seamless the updates have become in comparison to the manual updates I had to do in the past.

jhass commented on 2015-11-03 17:14

The task is hooked into assets:precompile:

The issue was rather with the files location being tmp/cache, which the package doesn't and shouldn't include.

I changed the files location to public/assets instead,

andrej commented on 2015-11-02 18:44

Perhaps the build could have
bundle exec rake assets:uglify_bookmarklet
somewhere, so that it doesn't serve 500s after an update. This problem is quite new, it wasn't there a few weeks ago.

jhass commented on 2015-01-07 17:16

Diaspora doesn't support Ruby 2.2 yet. Unfortunately while the Ruby developers announced they would follow SemVer now, they pretty much fail to do so. Thus 2.2 is in fact a major upgrade that breaks backwards compatibilities in some parts. You found one in eventmachine. Now while eventmachine was updated to fix that, other of our dependencies are not, the one I know of is ruby-oembed, there might be others since nobody did real testing yet.

I locked down the package to use Ruby 2.1 for now.

andrej commented on 2015-01-07 15:56

I got stuck on an eventmachine build issue today. rb_select_thread is not declared somewhere in the headers (after the recent ruby updates).

I was able to work around the issue by adding eventmachine 1.0.4 into the Gemfile (instead of the default 1.0.3) and by adding...

HOME=$_srcdir DB=$_db $_bundle update eventmachine

...before all the other $_bundle commands.

jhass commented on 2015-01-03 13:43

No, I don't think so, since there actually aren't any real mirrors for

andrej commented on 2015-01-03 12:19

Is it possible to blacklist some of the rubygems mirrors? After a more or less random number of installed gems, I'm hitting the following issue:

Gem::RemoteFetcher::FetchError: Errno::ETIMEDOUT: Connection timed out - connect(2) for "" port 443 ...

andrej commented on 2014-10-07 04:03

OK. I reported this. It seems to affect other packages as well.

jhass commented on 2014-10-05 23:18

The second link is to the old indivdual package before the AUR supported split packages. I got that package deleted from the AUR and submitted the split package instead. That the old tarball is still downloadable is probably a bug that you can happily report ;)

All comments