Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2023-05-08 Thread Richard Lewis
On Thu, 15 Apr 2021 13:24:29 -0400 Antoine Beaupre wrote: > The release notes, in sections 4.2.2 and 4.8, actually suggest *three* > *different* ways of finding what are essential orphaned packages: > > aptitude search '~o' > aptitude search '?narrow(?installed, ?not(?origin(Debian)))' >

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2022-12-18 Thread Stuart Prescott
On 19/12/2022 08:10, Paul Gevers wrote: Hi On 15-04-2021 19:39, Antoine Beaupré wrote: I actually forgot that bullseye itself introduces yet another one: apt list ~obsolete But (I'm running bookworm): paul@mulciber ~/release-team/release-notes $ apt list ~obsolete Listing... Error!

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2022-12-18 Thread Paul Gevers
Hi On 15-04-2021 19:39, Antoine Beaupré wrote: I actually forgot that bullseye itself introduces yet another one: apt list ~obsolete But (I'm running bookworm): paul@mulciber ~/release-team/release-notes $ apt list ~obsolete Listing... Error! E: input:2-9: error: Expected end of file

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-21 Thread Andrei POPESCU
On Ma, 20 apr 21, 11:36:30, Antoine Beaupré wrote: > > I am not sure we should tell people to "remove any non-Debian package" > before the upgrade. They might have legitimate reasons to have > third-party package repositories...? A dist-upgrade is difficult enough, reducing complexity introduced

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-20 Thread Antoine Beaupré
On 2021-04-16 09:19:35, Justin B Rye wrote: > Antoine Beaupré wrote [...] aptitude search '?narrow(?installed, ?not(?origin(Debian)))' >>> >>> This one (apparently an improvement on the '~i(!~ODebian)' search that >>> was recommended for buster, though the logic is too subtle for me to

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-16 Thread Justin B Rye
Antoine Beaupré wrote >>> aptitude search '~o' >> >> This is nice and simple, but frankly as an aptitude user I wouldn't >> bother. Instead I'd do what the text just above mentions - launch >> aptitude, notice that there was a category for "Obsolete and Locally >> Created Packages" (which woul

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-15 Thread Antoine Beaupré
On 2021-04-15 21:08:27, Justin B Rye wrote: > Antoine Beaupre wrote: >> The release notes, in sections 4.2.2 and 4.8, actually suggest *three* >> *different* ways of finding what are essential orphaned packages: > > I don't think you mean "orphan" in either of the senses known to > "https://wiki.de

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-15 Thread Justin B Rye
Antoine Beaupre wrote: > The release notes, in sections 4.2.2 and 4.8, actually suggest *three* > *different* ways of finding what are essential orphaned packages: I don't think you mean "orphan" in either of the senses known to "https://wiki.debian.org/Glossary#orphan";. > aptitude search '

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-15 Thread Antoine Beaupré
I actually forgot that bullseye itself introduces yet another one: apt list ~obsolete Apparently, those are also a thing: comm -23 <(dpkg-query -W -f '${db:Status-Abbrev}\t${Package}\n' | grep '^.[^nc]' | cut -f2 | sort) <(apt-cache dumpavail | sed -rn 's/^Package: (.*)/\1/p' | sort -

Bug#987017: recommends 3 different ways to find obsolete packages, pick one

2021-04-15 Thread Antoine Beaupre
Package: release-notes Severity: minor The release notes, in sections 4.2.2 and 4.8, actually suggest *three* *different* ways of finding what are essential orphaned packages: aptitude search '~o' aptitude search '?narrow(?installed, ?not(?origin(Debian)))' apt-forktracer | sort Then