[SOLVED] [PVE 9/Debian 13] Safe to add the Debian 13 non-free repo (not non-free-firmware) for nvidia-detect?

Sep 1, 2022
524
197
53
42
Hello,

After following the instructions on the wiki to upgrade from PVE 8 to PVE 9, my Debian sources look like this:
Bash:
root@andromeda1:/etc/apt/sources.list.d# cat ./debian.sources
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

So, I've got main, contrib, and non-free-firmware, which seems to be expected according to the wiki (though some wiki pages don't show contrib).

What I don't have is non-free, which became apparent this evening when I wanted to install nvidia-detect.
Would I damage my Proxmox install somehow or risk package conflicts or something if I enabled non-free?


EDIT: The docs here ( https://pve.proxmox.com/wiki/Package_Repositories#_debian_base_repositories ) don't show the non-free repo, which is why I hesitated to add the entries.

Thanks!
 
Last edited:
the non-free repos should work just fine (e.g. i have it here on my proxmox install too). Our package dependencies should prevent any problems, or it would warn you that the proxmox-ve metapackage will be removed. Of course this is no guarantee, it can always happend that we missed some interaction, but in several years of running this, I did not encounter any problems...