I have a Hassen Hansson IT VM running on a QNAP successfully for a few years. I’ve been really conservative with upgrades, and I’m now on 23.0.12 and would like to upgrade to the latest 25.x.x release (NOT 26, it’s too new for me). Is this possible? The cmdline script /var/scripts/update.sh seems to only want to go to 26.
How should I upgrade to 25 with this VM? I know the other system components (PHP, the deb packages, etc) are up to date because I just ran the minor version upgrade.
The menu script automatically upgrades to the latest minor version, and then asks you if you want to go to the latest major version (if it exist). You can answer no.
Also, you shouldn’t be so conservative. You can’t jump from 23 to 25 in just one go. You need to upgrade each major version separately. We recommend upgrading at least one time each 2 months.
As already mentioned, the menu script will do this:
Your Nextcloud is on version 24 and 25 is latest:
NC 24 → latest NC 24 (asking question: do you want to upgrade to next major? yes/no) → (you choose yes) NC 25. But it only works for 1 major version as you can’t skip any.
Your Nextcloud is on version 24 and 25 is latest:
NC 24 → latest NC 24 (asking question: do you want to upgrade to next major? yes/no) → (you choose no) it stays at latest NC 24.
Your Nextcloud is on version 23 and 26 is latest:
NC 23 → latest NC 23 → Checks latest major (which is 26) and stops here since you can’t upgrade beteeen multiple major versions at once.
Hey there, I’ve accidentally fallen behind on these updates, and can’t seem to get it unstuck, and I’m having this issue
Is there any way I can go from 25 to 26, then 26 to 27?
It does make things clear, thanks. But still leaves me in a situation where it’s REALLY easy to get behind and update.sh won’t help. It just happened again. But I found a workaround!
I was on a not current 25. update.sh brought me to 25.10. Running it again, I was at 25.10 and 27.x is out and update.sh quits. What I want update.sh to do in this case is upgrade to the latest 26 version. But it won’t.
Looking at the code in github, I discovered I could do touch /tmp/nextmajor.version and that would cause update.sh to attempt and upgrade of my current version + 1. So I did that and it seems to have succeeded!
I’ll go ahead and try upgrading to 27 if the Nextcloud admin interface tells me all my apps are compatible.
thank you so much for posting this. Even though I have my updates set to automatic every week, somehow my Hansson VM missed a major version. this saved me the headache of doing everything manually
IMO, the update.sh script should give me the option of going from latest on 27 to 28, then 28 to 29.
As it is, I keep getting stuck in a situation where I am on a supported release (latest major - 2) , and update.sh will not upgrade me to latest major -1, then on it latest
UPDATE: I didn’t realize this a year ago, but it turns out you can put a version into /tmp/nextmajor.version, then run update.sh and it will upgrade to that version. THIS is what I have been looking for. So to summarize:
I was on version 27.y.z (something old, not latest v27)
ran update.sh, script correctly upgraded me to latest 27 (27.1.11 as of right now)
Reboot, make sure 27.1.11 working as expected.
Check https://download.nextcloud.com/server/releases/ or https://nextcloud.com/changelog/ see that 28.0.8 is the latest v28.
From command line, create a file called /tmp/nextmajor.version put a single line in it 28.0.8
Run update.sh. It will upgrade to 28.0.8.
Reboot, check that 28.0.8 is working as expected.
Optionally, run update.sh again to update to latest v29.