Support apps with unbounded platformVersionSpec #1

Open
opened 2026-08-04 13:46:01 +00:00 by julian · 0 comments
Owner

The Debian repo has components like nextcloud-34 that only include packages compatible with Nextcloud server v34. This assignment happens when the app packages are built and is limited to the 4 most recent Nextcloud server major versions.

For app releases with a platformVersionSpec like >=32.0.0 <35.0.0 this works well: When the package is built, we add it to nextcloud-32, nextcloud-33, nextcloud-34. When Nextcloud 35 gets released, the app will necessarily release a new version with an updated platformVersionSpec.

A few apps have unbounded platformVersionSpec values like >=21.0.0 <100.0.0. They don't necessarily release a new version when a new Nextcloud server major release is published. So the components it is added to could get out-of-date.

To fix that we could download the repo Packages file for the "main" component, parse it, generate the component a given package should be in, fetch the Packages file for the nextcloud-* components and check if it is in there.

I don't think I will do that, unless we need an app that has this problem.

The Debian repo has components like `nextcloud-34` that only include packages compatible with Nextcloud server v34. This assignment happens when the app packages are built and is limited to the 4 most recent Nextcloud server major versions. For app releases with a platformVersionSpec like `>=32.0.0 <35.0.0` this works well: When the package is built, we add it to nextcloud-32, nextcloud-33, nextcloud-34. When Nextcloud 35 gets released, the app will necessarily release a new version with an updated platformVersionSpec. A few apps have unbounded platformVersionSpec values like `>=21.0.0 <100.0.0`. They don't necessarily release a new version when a new Nextcloud server major release is published. So the components it is added to could get out-of-date. To fix that we could download the repo Packages file for the "main" component, parse it, generate the component a given package should be in, fetch the Packages file for the nextcloud-* components and check if it is in there. I don't think I will do that, unless we need an app that has this problem.
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
packages-nextcloud/nextcloud-apps#1
No description provided.