If you're running @nextcloud on #fedora, you'll want to upgrade to #Nextcloud 24 before upgrading to Fedora 36 or else you'll get a php compatibility error. I was able to hack the versioncheck.php to override it and upgrade to 24 and then everything was OK, but you'll have a much easier time upgrading nextcloud first.
@vwbusguy @nextcloud thanks for the heads up, I was just going to upgrade to F36 still being on NC23.
Why do you do that?
@sesivany @albi @vwbusguy The advantage of Fedora is too great, this is why I stick to it too. However, just like in case of PHP upgrades are not always seamless. In my case the issue is the DB format migrations in Postgres. Every time I upgrade, I get ready to restore, because once in a while the new server refuses to read the old DB. Then, "postgresql-setup --upgrade" is equivalent of hacking versioncheck.php. The manual for the tool even warns that it does not always work!
@pro I recently found out about a tool to upgrade the database on postgres, called pg_upgrade, at least on Artix/Arch. You have to have the old version installed somewhere (there's a package on artix/arch that will install the old postgres versions under /opt/) then you just give it the path to the old and new database, and old and new postgres binaries, and it handles moving the data over. Of course, that wasn't necessary on Ubuntu since it handled it automatically, but needs must
- replies
- 0
- announces
- 0
- likes
- 0