On 7/10/22, David Wright <deb...@lionunicorn.co.uk> wrote: > On Sun 10 Jul 2022 at 15:24:11 (-0700), L L wrote: >> How can I find out why apt-get is keeping a package back? > > I usually look at the output of apt-cache show <package>.
I accidentally stumbled upon that I can "apt-get upgrade <package>" and see what is likely the trigger for held packages. For me, it always hesitates and waits for approval. Most often, packages I've seen are being held back because of an upgrade to the next versioning plateau or because completely brand new packages are being installed along with. Being able to "-s" simulate with apt-get is something I always forget exists. I just test drove it, and it worked for upgrade in general: apt-get upgrade -s There wasn't anything held back this time so I can only assume that simulate would additionally work for: apt-get upgrade <package> -s That can be run just like that, as regular User instead of root. Simulation doesn't give the 100% full picture. It might not generate enough focus on the held package to answer why it's being held. May be why I don't remember to use it. I played with simulation a couple times, and it's a cute trick. At the end of the day, though, I just go straight for the real upgrade. For me so far, that route has been informative and has worked safely #1 because it doesn't continue until I hit the ENTER key again. :) Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
