Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #269719
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: After upgrade, what do you do about "removed" and "obsolete" packages ? |
| Date | 2024-05-30 12:40 +0200 |
| Message-ID | <IJLmp-gSvu-7@gated-at.bofh.it> (permalink) |
| References | <IJKA1-gRQe-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi, i wrote: > > Next documenation riddle is what the word "local" means in output lines > > like > > linux-image-5.10.0-rc2-ts/now 5.10.0-rc2-ts-37 amd64 [installed,local] Florent Rougon wrote: > I don't use this but guess it is as in aptitude, where “obsolete/local > packages” are packages that are installed (from dpkg's POV) but not > available from any of the repositories scanned in the last 'apt update' > run. So "local" would be just another word for "obsolete" ? Indeed, the output of apt list '?installed !?obsolete' | grep local shows only some packages with "locale" in their name, but none with "local" in the []-brackets. On the other hand apt list '?installed ?obsolete' | grep -v 'local]$' shows no packages, i.e. all lines of obsolete packages end by "local]". Nevertheless it would be nice to find documentation about this kind of info in the output of "apt list". Have a nice day :) Thomas
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-28 20:40 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Marco Moock <mm@dorfdsl.de> - 2024-05-28 21:10 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? The Wanderer <wanderer@fastmail.fm> - 2024-05-29 04:30 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-29 18:30 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Mike Kupfer <kupfer@rawbw.com> - 2024-05-29 19:10 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Max Nikulin <manikulin@gmail.com> - 2024-05-29 19:20 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-30 11:30 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Florent Rougon <f.rougon@free.fr> - 2024-05-30 11:50 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-30 12:40 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Florent Rougon <f.rougon@free.fr> - 2024-05-30 14:10 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Curt <curty@free.fr> - 2024-05-31 18:20 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-31 19:50 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Florent Rougon <f.rougon@free.fr> - 2024-06-01 01:00 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Florent Rougon <f.rougon@free.fr> - 2024-06-01 01:20 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-06-01 10:10 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? songbird <songbird@anthive.com> - 2024-06-01 14:20 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? Max Nikulin <manikulin@gmail.com> - 2024-05-30 18:50 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? "Thomas Schmitt" <scdbackup@gmx.net> - 2024-05-30 22:20 +0200
Re: After upgrade, what do you do about "removed" and "obsolete" packages ? David Wright <deblis@lionunicorn.co.uk> - 2024-05-30 20:10 +0200
csiph-web