Closed joshuazick1 closed 4 years ago
@joshuazick1 Temporary fix is to downgrade pve-manager to version 6.1-7:
pve-patches/pve-6.1-3-diff-backup-addon reinstall
dpkg -i pve-manager_6.1-7_amd64.deb
pve-patches/pve-6.1-3-diff-backup-addon apply
@ayufan Hunk #3 at @@ -635,13 +803,40 @@ is not directly compatible VZDump.pm, unfortunately - I couldn't wrap my head about how to adapt the patch, new version of subroutine looks entirely different.
@joshuazick1 Temporary fix is to downgrade pve-manager to version 6.1-7:
The following may be easier to run for those who aren't familiar with wget or curl to download the previous pve-manager package:
pve-patches/pve-6.1-3-diff-backup-addon reinstall
apt -V install 'pve-manager=6.1-7*'
apt-mark hold pve-manager
pve-patches/pve-6.1-3-diff-backup-addon apply
This will make pve-manager stick to the 6.1-7 version and apt won't try to upgrade it anymore until you run:
apt-mark unhold pve-manager
Thank you @ayufan for all your work, it's really appreciated. If you need any help following up with the upstream changes, please let me know.
apt-mark hold pve-manager
Bad idea, it's quite easy to forget about held packages, plus right now downgrading manager back one version works, since almost nothing else changed, but what it further changes in underlying components break that compatibility? Best course of action right now is to downgrade, sub to issue, and lay off apt update/upgrade for a bit.
@ivdok @tillo @joshuazick1
I updated patch to 6.1-8
.
I see that the Proxmox started working on Proxmox Backup Solution/Service (?). So, it might seem that relevance of this patch goes away in some time in the future. Lets see how much things they do change to make maintaining of this patch burden.
I was setting up a new Proxmox server today and was trying to apply your patch to it It failed with this