Package downgrade needed after canceling subscription?

[MightySlaytanic]

Hi,
I'd like to understand what I should do on my PVE installation if I enable subscription repositories and after x years I want to cancel my subscription. After canceling the subscription is it sufficient to comment out the subscription-only repositories and wait until the non-subscription packages will advance more than the last subscription-packages installed or do I need to manually downgrade PVE packages to the last versions available in the non-subscription repository?

The same for PBS.

I hope the question is clear.

 

[hlindqvist]

Hi,
I'd like to understand what I should do on my PVE installation if I enable subscription repositories and after x years I want to cancel my subscription. After canceling the subscription is it sufficient to comment out the subscription-only repositories and wait until the non-subscription packages will advance more than the last subscription-packages installed or do I need to manually downgrade PVE packages to the last versions available in the non-subscription repository?

The same for PBS.

I hope the question is clear.

From my understanding the non-subscription packages are *ahead* (as kind of a pre-release), not the other way around:

"This is the default, stable, and recommended repository, available for all Proxmox VE subscription users. It contains the most stable packages and is suitable for production use." -- https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo

vs

"This is the recommended repository for testing and non-production use. Its packages are not as heavily tested and validated." -- https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo


I think in the scenario that you describe, you would simply replace the enterprise subscription repo with the non-subscription repo, which would likely lead to some small leap ahead in terms of package versions.

(If "can I just comment it out?" implies that you currently have *both* repos configured, I imagine that might mean that you are already favoring the non-subscription packages)

 

[MightySlaytanic]

From my understanding the non-subscription packages are *ahead* (as kind of a pre-release), not the other way around:

"This is the default, stable, and recommended repository, available for all Proxmox VE subscription users. It contains the most stable packages and is suitable for production use." -- https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo

vs

"This is the recommended repository for testing and non-production use. Its packages are not as heavily tested and validated." -- https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo


I think in the scenario that you describe, you would simply replace the enterprise subscription repo with the non-subscription repo, which would likely lead to some small leap ahead in terms of package versions.

(If "can I just comment it out?" implies that you currently have *both* repos configured, I imagine that might mean that you are already favoring the non-subscription packages)

Currently I’m without a subscription and so I have commented the subscription repos. Since I’m thinking about a subscription to support Proxmox development I’d like to understand what would I have to do in case I cancel the sub in the future.

I don’t know why but I thought that the subscription repos had features that come later to non subscription ones.

Non hanks for the answer