Pull latest version of Nextcloud with uscan #5
Notifications
Due Date
No due date set.
Depends on
#6 maint: Update to Nextcloud 26.0.1
ijurisic/nextcloud-deb
Reference: ijurisic/nextcloud-deb#5
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As of right now, the latest version of Nextcloud is 26.0.1. The uscan command detects 25.0.6 as the latest version and downloads that instead.
Both the 25.0.x and 26.0.x lines are supported, and I completely understanding wanting to stay on the stable version for a while before switching to the latest release.
Given the way Nextcloud handles their releases, I'd ideally like to see a branch in this repo called something like
bullseye-stable
and another calledbullseye
.I envision the
bullseye-stable
branch as being the oldest version with at least 90 days worth of support left (currently the 25.0.x line).Meanwhile the
bullseye
branch would be the latest official release.There's an argument that could be made for having a third branch called
bullseye-beta
which would be unreleased versions (betas and release candidates).If this proposal is accepted, I would be willing to help maintain these branches.
Debian Bullseye use PHP 7.4 and Nextcloud 25 still support that version of PHP (under deprecated status), but Nextcloud 26 under system requirements need minimum PHP 8.0 (maybe work under PHP 7.4 but is not tested).
Not sure what is good direction, but one sulutions is to backport PHP 8.2 from Debian Bookworm (testing) to Debian Bullseye (stable) in that case we can here hanlde latest release of Nextcloud.
For more information can check on official documentation of Nextcloud, source link:
Nextcloud 25 - System requirements
Nextcloud 26 - System requirements
Ah, I didn't realize that Nextcloud was dropping support for the latest PHP in Debian.
In that case, I like the way you're currently handling this. I'll close this ticket and merge request and delete the branch. Thanks for the explanation.