Arch Linux User Repository

One last comment for today, because it might help others: manually copying /opt/mastodon/postcss.config.js to /var/lib/mastodon/node_modules/font-awesome/css/ did allow me to run the precompile step. Not ideal, but works.

Thanks, @ZhangHua!

I also still added

Z /opt/mastodon/.bundle              -   mastodon    mastodon
Z /var/lib/mastodon/public           -   mastodon    mastodon
L /var/lib/mastodon/app              -   -           -           -   /opt/mastodon/app

to the tmpfiles.d, and manually usermoded mastodon’s home directory.

Note that the permissions I gave are maybe too generous, and that I don’t have any idea how the home directory of the user could be updated from the sysusers.d (would stopping all processes be enough?)

However, I still end up with an error during precompile, which I don’t seem to be able to solve:

    WARNING in ./app/javascript/styles/mastodon-light.scss (/var/lib/mastodon/node_modules/css-loader/dist/cjs.js??ref--6-1!/var/lib/mastodon/node_modules/postcss-loader/src??ref--6-2!/var/lib/mastodon/node_modules/sass-loader/dist/cjs.js??ref--6-3!./app/javascript/styles/mastodon-light.scss)
    Module Warning (from /var/lib/mastodon/node_modules/postcss-loader/src/index.js):
    Warning

    (1:225993) start value has mixed support, consider using flex-start instead
Child mini-css-extract-plugin ../../var/lib/mastodon/node_modules/css-loader/dist/cjs.js??ref--6-1!../../var/lib/mastodon/node_modules/postcss-loader/src/index.js??ref--6-2!../../var/lib/mastodon/node_modules/sass-loader/dist/cjs.js??ref--6-3!../../var/lib/mastodon/node_modules/font-awesome/css/font-awesome.css:
    Entrypoint mini-css-extract-plugin = *
       1 module

    ERROR in /var/lib/mastodon/node_modules/font-awesome/css/font-awesome.css (/var/lib/mastodon/node_modules/css-loader/dist/cjs.js??ref--6-1!/var/lib/mastodon/node_modules/postcss-loader/src??ref--6-2!/var/lib/mastodon/node_modules/sass-loader/dist/cjs.js??ref--6-3!/var/lib/mastodon/node_modules/font-awesome/css/font-awesome.css)
    Module build failed (from /var/lib/mastodon/node_modules/postcss-loader/src/index.js):
    Error: No PostCSS Config found in: /var/lib/mastodon/node_modules/font-awesome/css
        at /var/lib/mastodon/node_modules/postcss-load-config/src/index.js:91:15

Do you have any idea how to fix this? (google and stackoverflow did not help ;))

@peippo Oh I see, I forgot to set proper options, you can add options=(!lto) just like https://github.com/archlinux/svntogit-community/blob/packages/ruby/trunk/PKGBUILD#L16

@ZhangHua: I tried the PKGBUILD from your gist, but I cannot build it. I always end up in a segfault during ruby compilation:

<internal:gc>:240: [BUG] Segmentation fault at 0x0000000000000004

full build log here

edit: seems to be connected to LTO, see https://bugs.ruby-lang.org/issues/18062 . I’ll try building without LTO and will let you know.

edit 2: with options=(!lto) it builds, but the installed bundle seems to get lost - are all the symlinks in the correct direction, or should they be the opposite way around?

I think we may build a custom version of ruby instead using the system one, just like what the Dockerfile does, the size of custom one is just about 121MB and I think it is affordable compared to this package's size.

Edit: I have tried to use the custom version of ruby and it seems works well. If you want to try, you can use this gist to create a newer version of mastodon package. Please also note that there are some breaking changes such as moving program to /opt/mastodon and just make /var/lib/mastodon for storing data, you may want to run migrate steps to keep your server work after upgrading.

It seems like updates to the Ruby stdlib packages recently caused Mastodon to break with errors like this:

Oct 13 14:43:52 exozyme bundle[20494]: [20494] ! Unable to load application: LoadError: cannot load such file -- digest/version
Oct 13 14:43:52 exozyme bundle[20494]: Did you mean?  digest/version
Oct 13 14:43:52 exozyme bundle[20494]: bundler: failed to load command: puma (/var/lib/mastodon/vendor/bundle/ruby/3.0.0/bin/puma)
Oct 13 14:43:52 exozyme bundle[20494]: /var/lib/mastodon/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.11.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:27:in `require': cannot load such file -- digest/version (LoadError)
Oct 13 14:43:52 exozyme bundle[20494]: Did you mean?  digest/version

Until this is fixed, I recommend you do not upgrade any Ruby packages. Does anyone with more Ruby knowledge than me know what should be done to actually fix this?

line 76 should be -i nginx.conf because when run that command, current working directory has already been dist folder.

@MShrimp4 Thanks, fixed!

Default dist/nginx.conf needs to be changed:

#root /home/mastodon/live/public
root /var/lib/mastodon/public # Change to this one

Or add this line to package()

sed -e 's/home\/mastodon\/live/var\/lib\/mastodon/g' \
    -i dist/nginx.conf

@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.