Upgrade to v4.1.2

[panomaki]

Problem

• Mastodon 4.1.2 was released today. Issue #367 and #374 were solved by mastodon/mastodon/issues/24230 upstream.

Solution

• This pull request does three things:
  1. Bumps mastodon source to 4.1.2
  2. Removes the temporary blurhash patch
  3. Bumps ruby to 3.0.6 as required by upstream

This pull request also supersedes #366, #368 and #375.

PR Status

• [X] Code finished and ready to be reviewed/tested
• [X] The fix/enhancement were manually tested (if applicable)

[Manually tested on a Virtualbox installation, both clean install and upgrade from 4.0.2]

Automatic tests

Please trigger automatic tests as I can't.

[lapineige]

!testme

[yunohost-bot]

May the CI gods be with you!

[lapineige]

It seems fixed.

[panomaki]

It seems fixed indeed; the tests pass 1 - 5; the install of the ancient 3.5 version fails in 6 so can't be upgraded and 7 times out?

[lapineige]

Why CI says backup&restore fails why the logs say it worked ? 🤔

[lapineige]

!testme

[yunohost-bot]

:v:

[panomaki]

It appears the yunohost-runner has problems installing mastodon_3.5.3_ynh1. As that is necessary to test the upgrade, it fails. @yalh76 is there something that can be done here? Is it something in check_process (which should include testing the upgrade from 4.0.2, but anyways an upgrade from 3.5.3 should still be possible, it's less than a year old)?

[panomaki]

Note: Mastodon 4.1.2 is a security patch that solves a vulnerability when using LDAP. As yunohost uses LDAP-authentication for mastodon by default, therefor this upgrade is urgent, but I cannot solve the fact yunohost-runner doesn't run through all tests... anybody able to help?

[panomaki]

Reran job 6613 with the added commits, passes. Changed README to reflect upgrade paths.

[lapineige]

This makes me wonder why the cache in even included in the backup, and not excluded by default.

[panomaki]

This makes me wonder why the cache in even included in the backup, and not excluded by default.

As far as I can see it that is because the yunohost backup system (I presume that this is also used here) does not allow to exclude directories outside /home (and you'd have to exclude /var/www/mastodon/live/public/assets.

[lapineige]

Oh, that's too bad :(

I wonder if it's a planed feature @YunoHost-Apps/apps-group, and/or if we could bypass this by putting date in /home and symlinking them… but depending on how users manage their files this might be an issue…

[lapineige]

So… ready for merging ? :)