Upgrade instructions for PVE and PBS conflicting

[wrobelda]

Hi,

While upgrading one of my instances, which has both PBS and PVE installed, I noticed that the wiki pages for both suggest saving the PVE and PBS repository details to the same "proxmox.sources" file, i.e.

cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

It's not hard to imagine a bunch of users will overwrite one set with another in the process of upgrading.

 

[fba]

I agree. The instructions are clear by itself, but a hint to use cat >> on the second source would help or instead using individual files.

 

[UdoB]

I am not sure why they didn't call these "proxmox-pbs.sources" and "proxmox-pve.sources" (or similar) to avoid this headache...

 

[wrobelda]

I am not sure why they didn't call these "proxmox-pbs.sources" and "proxmox-pve.sources" (or similar) to avoid this headache...

They did for the enterprise repositories in the instructions. Seems like an unintended omission to not have done the same for the no-subscription repos.

 

[leesteken]

Would be nice if they would put test, no-subscription and enterprise in a single pve.source (and pbs.source for PBS) with only the enterprise enabled by default (replacing pve-enterprise.source). Instead of using different files when you enable them from the web GUI.