Re: Question on dpkg -l output.

2018-12-24 Thread aprekates
Thanks. Thats also what the maintainer of dpkg answered me to my bug report. On 23/12/18 6:49 μ.μ., Pascal Hambourg wrote: Le 22/12/2018 à 02:44, aprekates a écrit : Indeed some are virtual or pure virtual (although i dont know the diff) But also there are packages like 'ergo' which look nor

Re: Question on dpkg -l output.

2018-12-23 Thread Pascal Hambourg
Le 22/12/2018 à 02:44, aprekates a écrit : Indeed some are virtual or pure virtual (although i dont know the diff) But also there are packages like 'ergo' which look normal and the only relation i think found (reason to display it) is because libstd++6 depends on it. Also listed packages like '

Re: Question on dpkg -l output.

2018-12-22 Thread aprekates
Yes, i noticed that w* will pass if there is no such file  in current dir. But still i cant understand the output so i submit bugreport  Bug#917098: Thanks all for the feedback. On 22/12/18 6:13 μ.μ., Joe Pfeiffer wrote: Dan Ritter writes: Eduardo M KALINOWSKI wrote: On 21 de dezembro de 2

Re: Question on dpkg -l output.

2018-12-22 Thread Joe Pfeiffer
Dan Ritter writes: > Eduardo M KALINOWSKI wrote: >> On 21 de dezembro de 2018 20:24, aprekates wrote: >> > In a new installed system with Debian 9.6 >> > >> > $ dpkg -l >> > >> > will list only packages with 'ii' state and a couple of 'rc'. >> > >> > But if i  run: >> > >> > $ dpkg -l w* >>

Re: Question on dpkg -l output.

2018-12-21 Thread aprekates
Indeed some are virtual or pure virtual (although i dont know the diff) But also there are packages like 'ergo' which look normal and the only relation i think found (reason to display it) is because libstd++6 depends on it. Also listed packages like 'wink' not in the repos any more. On 22/12/

Re: Question on dpkg -l output.

2018-12-21 Thread Oliver Schoede
On Sat, 22 Dec 2018 01:10:34 +0200 aprekates wrote: > In my case both: > > $ dpkg -l w* > > and > > $ dpkg -l 'w*' > > will report the same list > Hi! I'm getting the same sort of output and it seems to me these are packages, dpkg knows about providing some virtual packages, that something

Re: Question on dpkg -l output.

2018-12-21 Thread aprekates
In my case both: $ dpkg -l w* and $ dpkg -l 'w*' will report the same list # dpkg -l w* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name   

Re: Question on dpkg -l output.

2018-12-21 Thread Dan Ritter
Eduardo M KALINOWSKI wrote: > On 21 de dezembro de 2018 20:24, aprekates wrote: > > In a new installed system with Debian 9.6 > > > > $ dpkg -l > > > > will list only packages with 'ii' state and a couple of 'rc'. > > > > But if i  run: > > > > $ dpkg -l w* > > > > i will get a dozen also of

Re: Question on dpkg -l output.

2018-12-21 Thread Eduardo M KALINOWSKI
On 21 de dezembro de 2018 20:24, aprekates wrote: > In a new installed system with Debian 9.6 > > $ dpkg -l > > will list only packages with 'ii' state and a couple of 'rc'. > > But if i  run: > > $ dpkg -l w* > > i will get a dozen also of 'un' packages. > > So i dont understand the logic of

Question on dpkg -l output.

2018-12-21 Thread aprekates
In a new installed system with Debian 9.6 $ dpkg -l will list only packages with 'ii' state and a couple of 'rc'. But if i  run: $ dpkg -l w* i will get a dozen also of 'un' packages. So i dont understand the logic of altering the output when i use a pattern . I would expect to see only 'ii'