Arch Linux User Repository

Till last week's update, everything was fine.

I can see that he is using a different bundler version Bundler 2.5.4 is running, but your lockfile was generated with 2.4.13. Installing Bundler 2.4.13 and restarting using that version.

Deleting .bundler does not change this.

Compile error:

compiling transliterator.cpp
In file included from /usr/include/unicode/unistr.h:39,
                 from /usr/include/unicode/translit.h:27,
                 from transliterator.cpp:5:
/usr/include/unicode/stringpiece.h:133:29: error: ‘enable_if_t’ in namespace ‘std’ does not name a template type
  133 |             typename = std::enable_if_t<
      |                             ^~~~~~~~~~~
/usr/include/unicode/stringpiece.h:133:24: note: ‘std::enable_if_t’ is only available from C++14 onwards
  133 |             typename = std::enable_if_t<
      |                        ^~~
/usr/include/unicode/stringpiece.h:133:40: error: expected ‘>’ before ‘<’ token
  133 |             typename = std::enable_if_t<
      |                                        ^
In file included from /usr/include/unicode/uenum.h:25,
                 from /usr/include/unicode/utrans.h:22,
                 from /usr/include/unicode/translit.h:29:
/usr/include/unicode/localpointer.h:561:26: error: parameter declared ‘auto’
  561 | template <typename Type, auto closeFunction>
      |                          ^~~~
/usr/include/unicode/localpointer.h:573:76: error: template argument 2 is invalid
  573 |     explicit LocalOpenPointer(std::unique_ptr<Type, decltype(closeFunction)> &&p)
      |                                                                            ^
/usr/include/unicode/localpointer.h:583:78: error: template argument 2 is invalid
  583 |     LocalOpenPointer &operator=(std::unique_ptr<Type, decltype(closeFunction)> &&p) {
      |                                                                              ^
/usr/include/unicode/localpointer.h:599:59: error: template argument 2 is invalid
  599 |     operator std::unique_ptr<Type, decltype(closeFunction)> () && {
      |                                                           ^
/usr/include/unicode/uenum.h:69:1: note: invalid template non-type parameter
   69 | U_DEFINE_LOCAL_OPEN_POINTER(LocalUEnumerationPointer, UEnumeration, uenum_close);
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/unicode/uset.h:358:1: note: invalid template non-type parameter
  358 | U_DEFINE_LOCAL_OPEN_POINTER(LocalUSetPointer, USet, uset_close);
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/unicode/utrans.h:258:1: note: invalid template non-type parameter
  258 | U_DEFINE_LOCAL_OPEN_POINTER(LocalUTransliteratorPointer, UTransliterator, utrans_close);
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
make: *** [Makefile:238: transliterator.o] Error 1

make failed, exit code 2

Hi @aoneko, thanks for reporting that error. For me, both cbor and posix-spawn are failing to compile, and it seems to be due to Arch's recent GCC upgrade from 13.2 to 14.1. Both libraries are very old and not really maintained anymore (actually Mastodon is removing their dependency on posix-spawn), so in the meantime, I added a CFLAGS to ignore these errors. For more info, see https://github.com/rtomayko/posix-spawn/issues/91

aur/mastodon/src/mastodon-4.2.8/vendor/bundle/ruby/3.0.0/gems/cbor-0.5.9.6/ext/cbor
make DESTDIR\= sitearchdir\=./.gem.20240518-11265-869ort sitelibdir\=./.gem.20240518-11265-869ort
compiling buffer.c
compiling buffer_class.c
buffer_class.c: In function ‘read_until_eof’:
buffer_class.c:270:17: error: passing argument 3 of ‘rb_rescue2’ from incompatible pointer type
[-Wincompatible-pointer-types]
  270 |                 read_until_eof_error, (VALUE)(void*) args,
      |                 ^~~~~~~~~~~~~~~~~~~~
      |                 |
      |                 VALUE (*)(VALUE) {aka long unsigned int (*)(long unsigned int)}
In file included from /usr/include/ruby-3.0.0/ruby/ruby.h:38,
                 from /usr/include/ruby-3.0.0/ruby.h:38,
                 from compat.h:30,
                 from buffer_class.c:28:
/usr/include/ruby-3.0.0/ruby/internal/iterator.h:51:40: note: expected ‘VALUE (*)(VALUE,  VALUE)’ {aka ‘long
unsigned int (*)(long unsigned int,  long unsigned int)’} but argument is of type ‘VALUE (*)(VALUE)’ {aka
‘long unsigned int (*)(long unsigned int)’}
   51 | VALUE rb_rescue2(VALUE(*)(VALUE),VALUE,VALUE(*)(VALUE,VALUE),VALUE,...);
      |                                        ^~~~~~~~~~~~~~~~~~~~~
make: *** [Makefile:246: buffer_class.o] Error 1

This type of error tends to depends on the Ruby version which installed in your system. But you know that the Ruby version in Arch Linux distro is lower than the minimum requirement. I guess this might be the reason that caused the problem. Just for a reference.

This package uses Ruby from the official Arch repos, which hasn't been updated in a long time. However, I haven't had any problems running Mastodon with this old version of Ruby.

The ruby version seem to be outdated Here it requires 3.2.3 but the ruby bundler is 3.0.6

Is anyone else experiencing segfaults with an error message like /var/lib/mastodon/vendor/bundle/ruby/3.0.0/gems/blurhash-0.1.7/lib/blurhash.rb:9: [BUG] Segmentation fault at 0x00007f827fafd000? There's an issue on the Mastodon repo about a similar bug, but it's claimed to be fixed. One remedy is to comment out Environment="LD_PRELOAD=libjemalloc.so" in the systemd service files for mastodon-web and mastodon-streaming or add Environment="LD_PRELOAD=" to the override files, but that leads to increased memory usage.

@peippo there seems to be another release that is adressing this:

https://github.com/mastodon/mastodon/releases/tag/v4.2.3

Thanks for the update! Right after your pushing the PKGBUILD, the json-canonicalization gem was yanked upstream and replaced by a new version. The bundle does not build right now, but json-canonicalization-1.0.0 seems safe.

See https://rubygems.org/gems/json-canonicalization/versions/0.3.2

@bjo You can replace the URL in the source array to point to a tar.gz of glitch-soc instead and the PKGBUILD will probably still work.

Any idea how to integrate glitch-soc into this PKGBUILD?