-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, it's been a while #139
Comments
Bit of a note here:
There is no Nextcloud version that supports both PHP versions (Up to v24 on Debian 11, v25 and beyond on Debian 12). This means there will likely be a stop-gap update along in the way (i.e. we won't be able to upgrade all the way to v68). Still unsure how to do this while making sure that a certain release can be installed in both Debian 11 and Debian 12 🤔 |
Perhaps you can use packages from https://sury.org/ to install the php version you need? This seems to be the php maintainer from Debian. (needs to be confirmed though) |
Yeah - to be fair I would really prefer if this didn't involve using third party repositories. But I'm not seeing another choice 😔 |
@ddavness any word on progression? We're a few revisions behind the main release. |
Apologies, was catching up to life (or perhaps, life was catching up to me! 😅) After thinking on this for a bit, I've decided that for the PHP issue, the stop-gap version will install a third-party repository on distros that do not support NC 25 out of the box (i.e. Debian 11 and Ubuntu 20.04), and then remove it* once the user upgrades to Debian 12/Ubuntu 22.04 * On Debian, the best way to do this is to create a |
After some investigation, I'm leaning towards the following: The stopgap version will be based on v67, which is the latest upstream version that installs NextCloud 25 (the last one to still support PHP 7.4 - even if deprecated) On that stopgap version:
From there, we skip straight ahead to the latest upstream version (currently v69), which is running Nextcloud 26:
|
Are you looking for any help? |
Currently working on merging v67 into the Biggest changes (and the largest source of merge conflicts) seem to be on the admin panel itself. Have to take a look on what changed from their side :) |
I'm very happy to see your update, @ddavness! I wish I could be of more help though! I've been reading the installation scripts to understand how this has all been put together and it's becoming clearer to me. Hopefully I can contribute in the near future! I haven't given up on changing the database to pg either, so as soon as I understand things better, I'm going to give it a bash! Thanks again for your effort! Ko-fi bought. |
As you've noticed, it's been a while since I last touched this project. Alas, life decided to do it's thing. I now have a job, yadda yadda, and am pursuing other projects.
Yet, I'm not intending to leave the project abandoned just yet.
What now from here?
It will be an herculean effort, since we're like 8 versions behind. Alongside that, Debian users are still required to sit on Debian 11; I want to add support to it along the way. Definitely expect this to take a while to complete!
It is definitely possible that the catch-up to the upstream version might be done gradually. Stay tuned for updates! 👋
And after that?
We'll see what the future holds. To keep workload low from my side, new features won't be actively worked on anymore by myself. Pull Requests will still remain welcome, naturally.
The text was updated successfully, but these errors were encountered: