Post AsIFByyEH8dsBr1rDU by kazriko@alcatir.com
(DIR) More posts by kazriko@alcatir.com
(DIR) Post #AsHXqsQV7ArFmfwUlc by kazriko@alcatir.com
2025-03-21T02:33:26.006110Z
0 likes, 0 repeats
Upgrading to Pleroma 2.9.1 was harrowing. So many yaks to shave...
(DIR) Post #AsHXqtgURDF3gYQmKO by pro@mu.zaitcev.nu
2025-03-21T14:25:32.463908Z
0 likes, 0 repeats
@kazriko What did you hit? I'm on develop.
(DIR) Post #AsIFByMeWqaIJJRqe8 by kazriko@alcatir.com
2025-03-21T14:57:05.256302Z
0 likes, 0 repeats
@pro I was running the source code version on Debian, first the 2.9.1 needed Elixir 1.14, and Debian Bullseye didn't have it, so I had to move to that. Then I had to drop the apt sources list I was using for elixir before, then reinstall a bunch of packages that it dropped when moving from one source to another. Migrate the database from postgres 13 to 15. The debian upgrade broke my ethernet config, so I had to go OOB console and fix that. Then reinstall more missing packages that were causing compile errors. it took a couple of hours to get everything back up. Also, since I wasn't using Git, there were leftover cruft files from the sshd bbs functionality that was apparently removed and causing elixir compile issues, and I had to delete the files from my tree.
(DIR) Post #AsIFByyEH8dsBr1rDU by kazriko@alcatir.com
2025-03-21T14:59:31.477558Z
0 likes, 0 repeats
@pro So it really wasn't any Pleroma issues, just a lot of upgrades that pleroma required to the system, and issues with my older style of installation, that took a lot of busywork to sort out.
(DIR) Post #AsIFBzyyVqphKSNy1A by pro@mu.zaitcev.nu
2025-03-21T22:31:10.431216Z
0 likes, 0 repeats
@kazriko I see, thanks. I guess running on Fedora insulated me from this somewhat. Of course I have to deal with Postfix version bumps once in a while, but nothing more than that.