Is it possible to upgrade just selected packages from the update UI?

scyto

Well-Known Member
Aug 8, 2023
548
119
48
For example below if i wanted to upgrade just the FFR packages how can i do that in the UI, am i being stupid?
(or do I need to just accept per package upgrading has to be done via manual shell commands)

I was hoping to see an upgrade 'selected package' on the upgrade drop down or somesuch.

1694647606068.png
 
no, that's not supported. in general I would recommend upgrading all packages (while we try hard to encode all the needed inter-dependencies in the package metadata, it's always possible we've missed something which would result in a partial upgrade breaking something - and you also get the most likely to be well tested combination of packages if you don't keep random parts on old versions ;))
 
no, that's not supported. in general I would recommend upgrading all packages (while we try hard to encode all the needed inter-dependencies in the package metadata, it's always possible we've missed something which would result in a partial upgrade breaking something - and you also get the most likely to be well tested combination of packages if you don't keep random parts on old versions ;))
Agreed, as soon as you have those thunderbolt-net IPv6 and xDomain patches backported in the pve-kernel i plan to switch back to your kernel and drop my patched 6.5.2 ubuntu kernel, until then i can't upgrade all or it will break my cluster :)
 
Last edited:
Agreed, as soon as you have those thunderbolt-net IPv6 and xDomain patches backported in the pve-kernel i plan to switch back to your kernel and drop my patched 6.5.2 ubuntu kernel, until then i can't upgrade all or it will break my cluster :)
your kernel (image/package) should not be overwritten by ours (each kernel version gets its own package name and file paths), and you can pin yours in your bootloader :)
 
and you can pin yours in your bootloader
umm i have no idea how to do that :) .... goes google.....

this right? proxmox-boot-tool kernel pin 6.5.2-tbfixes-v2+

Code:
Setting '6.5.2-tbfixes-v2+' as grub default entry and running update-grub.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.2-tbfixes-v2+
Found initrd image: /boot/initrd.img-6.5.2-tbfixes-v2+
Found linux image: /boot/vmlinuz-6.5.2-tbfixes+
Found initrd image: /boot/initrd.img-6.5.2-tbfixes+
Found linux image: /boot/vmlinuz-6.2.16-10-pve
Found initrd image: /boot/initrd.img-6.2.16-10-pve
Found linux image: /boot/vmlinuz-6.2.16-8-pve
Found initrd image: /boot/initrd.img-6.2.16-8-pve
Found linux image: /boot/vmlinuz-6.2.16-3-pve
Found initrd image: /boot/initrd.img-6.2.16-3-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Adding boot menu entry for UEFI Firmware Settings ...
done

do i need to re-pin after installing a new official kernel package?
 
Last edited:
no, the pin should be saved persistently until you clear it.
 
  • Like
Reactions: scyto