On Fri, May 22, 2020 at 12:49:25PM +0200, Julian Andres Klode wrote: > Control: tag -1 moreinfo > > On Fri, May 22, 2020 at 12:19:54PM +0200, Sergio Gelato wrote: > > Package: apt > > Version: 18.104.22.168 > > > > I'm trying to pin some packages (nvidia stuff) the upgrade of which is best > > followed by an immediate reboot, so that I can upgrade the rest without > > waiting for a reboot window. I came up with the attached preferences > > configuration (based on the list of packages apt-get would otherwise try to > > upgrade on this system), and while it's definitely having some effect it > > seems that "apt-get upgrade" still wants to upgrade some of the pinned > > packages. I see no reason (neither good nor bad-but-documented) for this, > > so I call it a bug. > > You have pinned all versions of these packages to the same priority - 10, > including the installed version. I'm wondering more why the other > packages are kept back, I'd expect them to be upgraded too. > > What does policy say for them?
FWIW, as you want to emulate hold, the correct approach to do that is to pin the installed version high: Package: ... Pin: release a=now Pin-Priority: 1001 -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en