Post #2692987

2025-02-12 16:01 UTC

@thisismissem@hachyderm.io @renchap@oisaur.com @andypiper@macaw.social I went the long, but more easy to troubleshoot, route and cross-graded 4.1.22 to 4.2.0 and went upwards version by version from there. I've probably blacklisted my server's IP with rubygems, but I got there!

Replies (2)

@mike@mikecoats.social 2025-02-12 16:05

@thisismissem@hachyderm.io @renchap@oisaur.com @andypiper@macaw.social 4.2.0 - 4.2.2 will no longer install as a gem has been yanked. 4.2.3 has a change in node versions to be aware of on an old server, but the instructions for 4.2.0 can be followed on 4.2.3 to get the DB migrations in place. 4.2.4 has a change in ruby versions to be aware of, but once that's fixed you're fine. 4.2.5 - 4.2.15 all install without error.

Open ##2692989
@renchap@oisaur.com 2025-02-12 16:16

@mike@mikecoats.social @thisismissem@hachyderm.io @andypiper@macaw.social You should be able to update to the latest patch version skipping all the other ones, using the steps described in the minor version release notes. So 4.1.x => 4.1.22 => 4.2.15 (using the 4.2.0 upgrade instructions) => 4.3.3 (using the 4.3.0 instructions)

Open ##2692992