Closed m0n4 closed 1 year ago
Hi, thanks for your report! Can you please apply this patch and check if updating works afterwards? https://patch-diff.githubusercontent.com/raw/nextcloud/server/pull/35434.patch
Thank you!
Sorry I fixed the issue without waiting for a reply. The current version is "CustomString 25.0.2 RC1" so this let us update until NC26 as you expected.
@MichaIng as you meant you wanted to test on 32-bit next time, could you maybe check if https://patch-diff.githubusercontent.com/raw/nextcloud/server/pull/35434.patch makes the update to 25.0.2 RC1 work again on 32-bit? Thank you!
Hi, thanks for your report! Can you please apply this patch and check if updating works afterwards? https://patch-diff.githubusercontent.com/raw/nextcloud/server/pull/35434.patch
This patch fixed the issue for me on armhf, thanks.
Thanks for verifying!
Thanx for the report and the patch, it fixed the issue for me too.
Great ! I guess I can close it now
Lets leave it open until the fix is released
Works here as well. Is it somehow possible to skip the check during second stage update completely but only do it when checking for a new update resp. when trying to apply the first stage update (installing new files)? One cannot break the system more than being stuck between first and second stage anyway. Or is the same script called in both stages?
Is it somehow possible to skip the check during second stage update completely but only do it when checking for a new update resp. when trying to apply the first stage update (installing new files)? One cannot break the system more than being stuck between first and second stage anyway. Or is the same script called in both stages?
Sorry, I don't get the question.
Well: This code blocks the database migration and repair steps after the Nextcloud 26 files have been installed already, i.e. too late anyway. So I'm not sure what the purpose of the check at this stage is. Reasonable is it of course to not offer the update to Nextcloud 26 in the first place, and when running updater.phar
, to block download/install of NC26 files.
EDIT: Okay, it does make sense in case users use the manual update path, download and install the files manually. So it can be reverted without having database and possibly other things migrated to NC26 already.
EDIT: Okay, it does make sense in case users use the manual update path, download and install the files manually. So it can be reverted without having database and possibly other things migrated to NC26 already.
yes, this is the idea
Closing as the backport is merged
⚠️ This issue respects the following points: ⚠️
Bug description
commit faa747e44575269d9f4eb09d0a2c6aa3fe0501f8 introduced a fix to prevent 32-bit PHP version to upgrade to an unsupported version.
The check is done using Semver.
As Semver isn't available this raise un error:
This prenvents upgrading to the last supported version for 32bits machines
Steps to reproduce
Expected behavior
Upgrading to the last supported version ;-(
Installation method
Official All-in-One appliance
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
No response
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Running Raspbian 11 (Bullseye) on a raspi 3B+ Nexcloud have been upgraded from stable to stable since v15