-
I used this script https://community-scripts.github.io/ProxmoxVE/scripts?id=post-pve-install on PVE 8 and when I went to upgrade to PVE 9, after following the checklist here https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Continuously_use_the_pve8to9_checklist_script, when I did apt dist-upgrade it failed with the errors shown here https://pastebin.com/TvbpPijm I asked on the Proxmox forum and they reckon it's the no-nag part of the script that has caused the problem. I tried moving the file /etc/apt/apt.conf.d/no-nag-script to /root but that hasn't helped. apt list --upgradable shows:
but I can't install any of those as they throw up unmet dependency errors. apt dist-upgrade shows:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Bullshitting by Forum. The “no-nag” part of the post-pve-install Your apt list --upgradable clearly shows that you have already upgraded to Debian 13 Bookworm->Trixie (Systemd 257.8, AppArmor 4.1, etc.). => This is a classic upgrade dependency issue, not a broken apt.conf snippet. => The problem isn't the “no-nag” part. If it had messed up, you would see something like this right away: As help: cat /etc/apt/sources.list Show the Problems with: apt install proxmox-ve |
Beta Was this translation helpful? Give feedback.
Bullshitting by Forum.
The “no-nag” part of the post-pve-install
script only writes a small config to /etc/apt/apt.conf.d/no-nag-script.
→ If the file is corrupted or created with incorrect syntax, you will immediately see a syntax error (malformed tag) every time you run apt update.
→ This would be a clear parser error directly during the update, not just a bunch of “kept back / unmet dependencies” as in your pastebin.
Your apt list --upgradable clearly shows that you have already upgraded to Debian 13 Bookworm->Trixie (Systemd 257.8, AppArmor 4.1, etc.).
The packages are all correctly available from the PVE9 repo (pmx2, pve9.x, etc.).
dist-upgrade is holding them back because dependenci…