Package Details: diaspora-mysql 0.7.18.2-1

Git Clone URL: https://aur.archlinux.org/diaspora-mysql.git (read-only, click to copy)
Package Base: diaspora-mysql
Description: A distributed privacy aware social network (MySQL)
Upstream URL: https://diasporafoundation.org
Licenses: AGPL3
Conflicts: diaspora-mysql-git, diaspora-postgresql, diaspora-postgresql-git
Submitter: jhass
Maintainer: jhass
Last Packager: jhass
Votes: 7
Popularity: 0.000013
First Submitted: 2016-09-05 18:58 (UTC)
Last Updated: 2023-07-12 16:26 (UTC)

Latest Comments

1 2 3 Next › Last »

jhass commented on 2022-09-13 18:34 (UTC)

Ah, these are generated by a script, so no maintenance effort on my side :)

fordprefect commented on 2022-09-11 12:00 (UTC)

While bumping the pkgver and rebuilding I realized, that in line 60 of the current PKGBUILD the pkgver is hardcoded again. I'd suggest using the existing $pkgver variable there. This reduces maintenance burden on you and makes the PKGBUILD more error prove for pkgver bumps.

jhass commented on 2022-05-22 14:00 (UTC)

It'll work fine against Ruby 2.7, just it'll spew a ton of deprecation warnings and we didn't yet run CI against it. So for the moment I'd like to keep it as is. I bumped the ruby2.6 package to the 2.6.10 release but dropped maintainership afterwards again since Ruby 2.6 is EOL and will see no more release after this.

fordprefect commented on 2022-05-17 09:18 (UTC)

Ruby2.6 is an orphan now, is it safe to switch to ruby2.7 (or even ruby3)?

Zergling_man commented on 2021-11-08 15:38 (UTC)

libffi updated and no longer provides libffi.so.7 which diaspora demands; symlinking to .so.8 bothers it because it fails to find some LIBFCLOSURE=7.0 or something inside.

fordprefect commented on 2021-04-19 19:26 (UTC)

Thanks for the comprehensive reply, makes all sense now.

jhass commented on 2021-04-19 17:14 (UTC) (edited on 2021-04-19 17:14 (UTC) by jhass)

I wasn't sure how backup would deal with removing a file so I kept it in there for the benefit of the doubt. Note that the toml was added too.

There's no straight forward converter, I would recommend to apply the settings to the new file manually with a side by side view with the yml. Meanwhile you can still re-create the symlink to /usr/share/webapps/diaspora/config/diaspora.yml and it'll continue working until 0.8, I just couldn't think of a good way to keep this in the package without superfluous and confusing deprecation warnings for users that chose to migrate.

I don't think references to $srcdir in such auxillary files is a real issue. I won't bother with cleaning this up, if you find a good and maintainable way, contributions welcome :) https://github.com/jhass/PKGBUILDs/tree/main/diaspora

Please always ignore each and every non-error messages from bundler, diaspora developers take care of those :)

fordprefect commented on 2021-04-19 09:52 (UTC) (edited on 2021-04-19 09:53 (UTC) by fordprefect)

Thank you for the update. It has a few issues, however:

  • etc/webapps/diaspora/diaspora.yml has been renamed to diaspora.toml, but the backup entry in the PKGBUILD is still the yml file. How to convert existing yml to toml by the way?

  • some files contain references to the $srcdir, but upon inspection these seem pretty unnecessary. Among these files is a Makefile for ruby_http_parser and som gem_make.out files seemingly containing log information from the gem compilation. Can these safely be deleted?

  • There are concerning post-install messages from the gems 'encryptor' and 'attr_encrypted' dealing with security implications. Are these safe to ignore?

Thanks for maintaining this software and making it available in the AUR. Much appreciated!

jhass commented on 2020-06-14 21:24 (UTC)

Hey, I just updated the package to 0.7.14 and thus Ruby 2.6. Does this still happen for you?

agaskins commented on 2020-06-14 21:08 (UTC) 

bundler: command not found: rake-2.5
Install missing gem executables with `bundle install`
==> ERROR: A failure occurred in build().
    Aborting...

1 2 3 Next › Last »