Package Details: mastodon 3.5.3-1

Git Clone URL: (read-only, click to copy)
Package Base: mastodon
Description: Your self-hosted, globally interconnected microblogging community
Upstream URL:
Keywords: activitypub fediverse mastodon server
Licenses: AGPL3
Submitter: flacks
Maintainer: Ta180m
Last Packager: Ta180m
Votes: 10
Popularity: 0.23
First Submitted: 2018-06-19 19:35 (UTC)
Last Updated: 2022-05-26 21:39 (UTC)

Latest Comments

Ta180m commented on 2022-04-28 21:03 (UTC) (edited on 2022-04-28 21:23 (UTC) by Ta180m)

@istobic I've ran this package for nearly a year now and it's not much of a hassle.

Edit: I adopted the package and just pushed a major overhaul that fixes the issues listed in my previous comment.

istobic commented on 2022-04-27 15:40 (UTC) (edited on 2022-04-27 15:40 (UTC) by istobic)

@Ta180m: Is it still the same hassle as described in the pinned comment, or can you recommend using the package (your updated version)?

Ta180m commented on 2022-03-30 23:43 (UTC) (edited on 2022-03-30 23:53 (UTC) by Ta180m)

This is my updated version of the diff for Mastodon 3.5.0:

Ta180m commented on 2022-02-24 21:57 (UTC) (edited on 2022-02-24 23:04 (UTC) by Ta180m)

I made several improvements for this package:

  • Updated link to

  • Correctly set ReadWritePaths in the systemd service file

  • Use sudo instead of su for the post-install instructions because it's cleaner

  • Changed the tmpfiles configuration to not recursively modify /var/lib/mastodon and instead use chmod the files this package owns

Here's the diff:

Note: the chmod command seems to fail with bash: /usr/bin/chown: Argument list too long, so I think running chown mastodon:mastodon -R /var/lib/mastodon post-install might be a better option.

heftig commented on 2021-11-14 00:13 (UTC)

The tmpfiles config you install modifies /var/lib/mastodon recursively on every boot and anytime pacman touches tmpfiles.d. That can be quite slow, taking 30 seconds or more each time.

You might want to go back to chmod'ing post-install/upgrade and only modify the dirs and files contained in the package, and not recursively.

Ta180m commented on 2021-07-29 16:38 (UTC)

Due to permission issues, I had to add


to the override files of the systemd services for this package to work.

liolok commented on 2020-05-25 03:40 (UTC)

An advise from previous packager (not maintainer):

Do use Docker, let this package rest in peace. (Unless you are able to take cover all the upstream sh*t)

count0 commented on 2020-03-05 20:49 (UTC)

Does not seem to be working with newer ruby 2.7... Does not build.

hhirtz commented on 2019-03-04 22:17 (UTC)

Gemfile.lock should not be removed:

diff --git a/PKGBUILD b/PKGBUILD
index 8eb9f76..f47195d 100644
@@ -38,10 +38,9 @@ sha512sums=('1829f16a5f98d1815168c8ecfd80b75bb3489e7b3e5eb06a858b0d35bdecc5a4542

 build() {
   cd mastodon-$pkgver
-  rm Gemfile.lock
-  bundle lock --update
-  bundle install --deployment --without development test
+  sed -i "s/1.17.3/$(bundle --version | cut -d' ' -f3)/g" Gemfile.lock
+  bundle install -j$(getconf _NPROCESSORS_ONLN) --deployment --without development test
   yarn config set ignore-engines true
   yarn install --pure-lockfile

fbrennan commented on 2018-12-20 00:41 (UTC)

I'm not interested in fixing the namcap errors. Most of them are wrong anyway - namcap can't tell, but yes ffmpeg and magick are both used. Others would require that each Node module and Ruby gem be itself individually packaged and required instead of downloaded and built. Just by the nature of Node versioning that would be a nightmare to deal with.

buzo commented on 2018-12-19 16:28 (UTC) (edited on 2018-12-19 16:29 (UTC) by buzo)

Did you run namcap on the resulting package? It produces a huge amount of warnings and errors, see this paste.

Also, please rename the source tarball, preferably like this:


fbrennan commented on 2018-12-11 04:43 (UTC)

Thank you @luka-devnull :-)

And for your previous comments as well. Helped me update the package after your first flag.

luka-devnull commented on 2018-12-08 09:31 (UTC)

v2.6.5 is out, which fixes a bug with yarn yanking packages in the pre v2.6.4 releases (including v2.6.2)

It's as easy as just updating the version number and the sha512sum though.

luka-devnull commented on 2018-11-09 03:45 (UTC)

You should also include libidn as a dependency. It doesn't build without it.

count0 commented on 2018-09-07 14:50 (UTC)

I'm getting the following build error when trying to upgrade to 2.5.0:

[1/6] Validating package.json... error mastodon@: The engine "node" is incompatible with this module. Expected version ">=8". error Found incompatible module info Visit for documentation about this command. ==> ERROR: A failure occurred in build(). Aborting... :: failed to build mastodon package(s)

flacks commented on 2018-08-29 21:03 (UTC)

Celti, thanks for the feedback. Updated.

Celti commented on 2018-08-29 09:34 (UTC) (edited on 2018-08-29 10:19 (UTC) by Celti)

git is a required makedepend. This fails to build in a container without it.

EDIT: Apparently npm is also a required makedepend to prevent yarn from arbitrarily changing the working directory and causing build failures for being unable to find .yarnclean (peripherally described as a docker issue in #6809 but also valid here).

EDIT 2: It also appears that yarn is a full dependency, not a makedepend — precompiling assets when running bundle exec rails mastodon:setup fails entirely without it.