mastodon 4.4.1

sean

mergy Ruby 3.2 is available by running source scl_source enable ruby32 in your shell. The setenv script does this for you, along with setting a lot of other environment stuff for your Mastodon app.

mergy

Cool.

$ ruby -v
ruby 3.2.8 (2025-03-26 revision 13f495dc2c) [x86_64-linux]

$ node -v
v20.19.1

But my postgres looks like 11.22 right now. Looks like there is something opal gives me on playing v14...

sean

mergy edit your setenv script and change this bit...

/usr/pgsql-11/bin/

... to this:

/usr/pgsql-14/bin/

... then source the script to pick up the update.

mergy

Well - might be an issue (before your setenv edit comment - so I will try that)

$ postgresql-14-setup check_upgrade
cat: /var/lib/pgsql/13/data/PG_VERSION: Permission denied

Cannot upgrade because the database in /var/lib/pgsql/14/data is not of
compatible previous version 13.

sean

mergy I'm not sure what you're doing there. Your server was upgraded to PostgreSQL v14 about a year ago and your databases were upgraded at that time as well. Whatever you had running on v11 in the past is already running on v14 and there's no upgrade step necessary on your part.

mergy

Got it - yes, I just never did anything with that in setenv then. I will correct and see how it goes.

mergy

$ postgres --version
postgres (PostgreSQL) 14.18

Great. Well, feels like masto 4.4.1 is possible....

mergy

almost made it but stuck.

$ bundle exec rails assets:precompile
<internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:in require': uninitialized constant JSON::Fragment (NameError) from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:inrequire'
from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' from /opt/ruby32/lib/ruby/json/ext.rb:8:in<module:Ext>'
from /opt/ruby32/lib/ruby/json/ext.rb:6:in <module:JSON>' from /opt/ruby32/lib/ruby/json/ext.rb:3:in<main>'
from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:in require' from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:inrequire'
from /home/xxxx/apps/yyyy//mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' from /opt/ruby32/lib/ruby/json.rb:579:in<module:JSON>'
from /opt/ruby32/lib/ruby/json.rb:575:in <main>' from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:inrequire'
from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:in require' from /home/xxxx/apps/yyyy//mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:inrequire'
from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/compile_cache/json.rb:49:in init!' from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/compile_cache/json.rb:42:ininstall!'
from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/compile_cache.rb:34:in setup' from /home/xxxx/apps/yyyy//mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap.rb:68:insetup'
from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap.rb:112:in default_setup' from /home/xxxx/apps/yyyy/mastodon/vendor/bundle/ruby/gems/bootsnap-1.18.6/lib/bootsnap/setup.rb:5:in<top (required)>'
from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:in require' from <internal:/opt/ruby32/lib/ruby/rubygems/core_ext/kernel_require.rb>:38:inrequire'
from /home/xxxx/apps/yyyy/mastodon/config/boot.rb:18:in <top (required)>' from bin/rails:3:inrequire_relative'
from bin/rails:3:in `<main>'

nick

mergy I wonder and suspect perhaps bootsnap is in some conflict with Ruby 3.2 here. Can you try testing with DISABLE_BOOTSNAP=1 bundle exec rails assets:precompile?

mergy

nick Thanks! I will try. Also see if I maybe do a require json somewhere that could help. I will try.

mergy

Different errors.

Going to step away for a while and think. Feels like I need to do require json on some .rb files

nick

mergy Based on some possibly related Ruby bug reports I saw today, it sounded like some other options may be to either downgrade bootsnap or upgrade to use at least Ruby 3.3.2.

mergy

Thanks. I will try in the AM

mergy

Probably going to try and just work from a local ruby environment now and nix the scl ruby32

mergy

installed ruby 3.3.0 via rbenv but too much to untangle if not using scl ruby32. Probably going to restore and move on to stay with older masto here I suppose.

mergy

restoring for now... oh well.

mergy

back on v4.3.8 for now. meh

sean

I'll try to have an upgrade procedure for this soon.