Package Details: mastodon 4.3.8-1

Git Clone URL: https://aur.archlinux.org/mastodon.git (read-only, click to copy)
Package Base: mastodon
Description: Your self-hosted, globally interconnected microblogging community
Upstream URL: https://github.com/mastodon/mastodon
Keywords: activitypub fediverse mastodon server
Licenses: AGPL3
Submitter: flacks
Maintainer: Vamp898
Last Packager: Vamp898
Votes: 22
Popularity: 0.131497
First Submitted: 2018-06-19 19:35 (UTC)
Last Updated: 2025-05-07 07:43 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 11 Next › Last »

dodecahedron commented on 2024-10-10 02:32 (UTC)

@peippo I made the precompile assets step prioritize using the corepack-installed Yarn 4 over the system Yarn which should fix that issue for other people.

peippo commented on 2024-10-09 20:46 (UTC)

You’re probably right, this alone did not fix my mastodon-web service, I also had to uninstall system-wide yarn as it prevented the precompile-assets step. Perhaps the latter was the more important step

dodecahedron commented on 2024-10-09 14:16 (UTC)

I think you can safely ignore those warnings since poppler handles PDFs and openslide handles microscope slide images like TIFFs and you're probably not sending either of those on Mastodon.

peippo commented on 2024-10-09 12:35 (UTC)

It seems that libvips’s optional dependencies poppler-glib and openslide are required for mastodon (see the error message below), would it be possible to add them as dependencies to mastodon?

Oct 09 14:31:20 bundle[902]: unable to load "/usr/lib/vips-modules-8.15/vips-poppler.so" -- libpoppler-glib.so.8: cannot open shared object file: No such file or directory
Oct 09 14:31:20 bundle[902]: unable to load "/usr/lib/vips-modules-8.15/vips-openslide.so" -- libopenslide.so.1: cannot open shared object file: No such file or directory

peippo commented on 2024-08-19 10:45 (UTC)

When you update to 4.2.12, could you also change the dependency redis to valkey? See this news item

Sandwich commented on 2024-08-13 18:52 (UTC)

@mansuetus thanks. That worked for me!

mansuetus commented on 2024-08-13 16:21 (UTC) (edited on 2024-08-13 16:21 (UTC) by mansuetus)

@Sandwich same here, solved.

For ox :

cd /var/app/current/vendor/bundle/ruby/3.2.0/gems/ox-2.14.18/ext/ox
sudo -u mastodon make
sudo -u mastodon cp ox.so ../../lib

For ERB : (works now without this fix BUT once I did this and it helped)

** edit file : /usr/lib/ruby/3.2.0/erb.rb
** FIND : 
require 'erb/version'
require 'erb/compiler'
require 'erb/def_method'
require 'erb/util'
** MODIFY TO LOOK LIKE :
require '/usr/lib/ruby/3.0.0/erb/version'
require '/usr/lib/ruby/3.0.0/erb/compiler'
require '/usr/lib/ruby/3.0.0/erb/def_method'
require '/usr/lib/ruby/3.0.0/erb/util'

Hope this helps.

Sandwich commented on 2024-08-13 15:59 (UTC) (edited on 2024-08-13 16:00 (UTC) by Sandwich)

Since the latest Ruby update to 3.2 Mastodon fails starting because it cannot find some libreries. It looks to me like it is using system dependencies instead of bundler:

Aug 11 22:39:36 fedi bundle[282724]: bundler: failed to load command: puma (/var/lib/mastodon/vendor/bundle/ruby/3.2.0/bin/puma)
Aug 11 22:39:36 fedi bundle[282724]: <internal:/usr/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require': cannot load such file -- /usr/lib/ruby/3.2.0/erb.rb (LoadError)

the same issue for ruby-ox

I have recompiled and cleanly reinstalled the package with no change.

dodecahedron commented on 2024-06-13 14:20 (UTC)

@gaboflowers I think makepkg now generates debug symbols by default, so you might want to disable that in /etc/makepkg.conf since this package is huge so generation will take a long time and unless you're a Mastodon dev, you probably don't need debug symbols.

gaboflowers commented on 2024-06-13 07:45 (UTC) (edited on 2024-06-13 07:49 (UTC) by gaboflowers)

I tried to install it, but got stuck at one step. This is the last printed:

[5/6] Building fresh packages...
[6/6] Cleaning modules...
Done in 22.37s.
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Copying source files needed for debug symbols...

I googled, and it seems like "Copying source files needed for debug symbols" is a niche-popular step to get stuck at. Any ideas on what could be the reason here?

EDIT: Retried and it worked. I'm leaving this in case anyone goes through the same.

« First ‹ Previous 1 2 3 4 5 6 7 .. 11 Next › Last »