On Tue 12 May 2020 at 12:12:33 (+0200), Vincent Lefevre wrote: > On 2020-05-07 18:24:59 -0500, David Wright wrote: > > On Wed 06 May 2020 at 12:31:35 (+0200), Vincent Lefevre wrote: > > > I use unstable. I doubt that packages get renamed in stable > > > (except between full upgrades, where the issue has already > > > been solved with the oldlibs section). > > > > I don't understand the relevance of oldlibs: only one of the packages > > that I removed was in that section, imagemagick, which gets pulled in > > under that name by inkscape as a Recommends. > > oldlibs was mentioned by Sven Joachim as solving the issue > automatically (at least with apt). > > I also have a Debian/stable machine, but no manually installed > packages were renamed in the upgrade to buster, so I could not > check... IIRC, I've never noticed any issue when upgrading this > Debian/stable machine anyway.
https://wiki.debian.org/RenamingPackages I think I understand how that's expected to work now. Checking on two top-level packages I have removed (cryptsetup/pdftk), I notice that though they are in Sections admin/text in the Packages list, their internal Section is oldlibs in buster versions of control; control is not a file I normally peruse, but deborphan does, I presume. What I don't know is when this Section category is acted upon if I do nothing. Do the transitional packages last until the next full release? (They certainly haven't disappeared in buster's point releases.) But in any case, you can see that my writing a script for removing packages like cryptsetup and pdftk would not be very productive. My little manual cleanup looks more like mere impatience. Cheers, David.
