Package Details: diaspora-mysql 0.9.0.0-2

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 (MariaDB/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.000000
First Submitted: 2016-09-05 18:58 (UTC)
Last Updated: 2025-01-28 13:29 (UTC)

Latest Comments

1 2 3 4 Next › Last »

sowieso commented on 2025-06-09 07:09 (UTC)

I tried to upgrade to Ruby 3.4 and ran in to several problems with this package.

1) Ruby 3.4 removed mutex_m from the default gemset. I added ›gem "mutex_f"‹ to the Gemfile to fix this. (According to the warnings, for Ruby 3.5 logger, benchmark, ostruct, syslog also need to be added.)

2) The next error I got was:

Could not open library '/usr/share/webapps/diaspora/vendor/bundle/ruby/3.4.0/gems/sassc-2.4.0/lib/
sassc/libsass.so': /usr/share/webapps/diaspora/vendor/bundle/ruby/3.4.0/gems/sassc-2.4.0/lib/sassc/libsass.so: cannot open shared object file: No such file or directory.

Unfortunately I have no idea why this happens. I solved it by copying the missing file to the mentioned position: cp /usr/share/webapps/diaspora/vendor/bundle/ruby/3.4.0/extensions/x86_64-linux/3.4.0/sassc-2.4.0/sassc/libsass.so /usr/share/webapps/diaspora/vendor/bundle/ruby/3.4.0/gems/sassc-2.4.0/lib/sassc/.

3) The last problem I had was that some binstubs are broken. Maybe there's a command that can regenerate them, but I don't know it. The problem afaiu is that we use the system's bundler, but the binstubs are generated by a different bundler.

%bundle install                                                                                                                                                                        
Bundler 2.6.7 is running, but your lockfile was generated with 2.5.9. Installing Bundler 2.5.9 and restarting using that version.
[…]

Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.

The --force command doesn't work, as it would overwrite the system's bundler. I temporarily solved this by outcommenting the bundler checks inside the binstubs.

I would be grateful if somebody could explain to me the reasons for 2) and 3).

fordprefect commented on 2025-04-18 10:17 (UTC)

With the replacement of redis by valkey this package needs some update. Is valkey hot-swappable or does this need config changes? Some guidelines would be well appreciated.

jhass commented on 2025-01-28 13:33 (UTC)

Hey guys, thanks for the feedback! Please try the new revision, I hope it'll fix these issues.

I'm not really using Arch as a daily driver anywhere anymore and my personal deployments since a while moved to a k3s cluster, so I might not be the best maintainer for these packages anymore, in case anyone wants to step up :)

sowieso commented on 2025-01-28 03:41 (UTC)

I guess the behavior of Bundler has changed, Gemfile resolution doesn't work when using a symbolic link (anymore?). bin/bundle is a symlink to /usr/bin/bundle, when executed it looks for a Gemfile inside /usr/bin, instead of ./. To me it looks like this a problem with Bundler, but the source code reads as if this was intended. Anyway, this can be fixed by adding this line to the systemd unit. Can you please add this to the package?

Environment=BUNDLE_GEMFILE=/usr/share/webapps/diaspora/Gemfile

The next problem I had was that I didn't have a Procfile inside Rails root. I'm not sure if this is a problem with my setup or a problem with the script. I added this Procfile (the upstream default).

web: bin/puma -C config/puma.rb
sidekiq: bin/bundle exec sidekiq

fordprefect commented on 2025-01-27 20:18 (UTC)

New issue: Started diaspora.service. /usr/Gemfile not found FATAL: Your bundle is not up to date, run the command "bundle install"

This looks awfully wrong. Can you point where to find help with this?

fordprefect commented on 2025-01-27 19:57 (UTC) (edited on 2025-01-27 20:03 (UTC) by fordprefect)

The service won't start due to the mini_portile2 gem missing, and I don't know how to install it. Can you give a hint or fix the build process? EDIT: Sorry, fixed it by installing extra/ruby-mini_portile2. Please add that as dependency.

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)?

1 2 3 4 Next › Last »