Re: scriptable way to list packages that are not installed

On 17/01/18 11:38 AM, Darac Marjal wrote: On 17/01/18 02:17, Charlie Gibbs wrote: > On 16/01/18 12:15 PM, david...@freevolt.org wrote: Is there a natural law or something, that every email message sent must contain at least one distracting error that is totally beside the point? Anyways,

Re: scriptable way to list packages that are not installed

On Wed, 17 Jan 2018, Darac Marjal wrote: On 17/01/18 02:17, Charlie Gibbs wrote: On 16/01/18 12:15 PM, david...@freevolt.org wrote: Is there a natural law or something, that every email message sent must contain at least one distracting error that is totally beside the point? Anyways, over

Re: scriptable way to list packages that are not installed

On 17/01/18 02:17, Charlie Gibbs wrote: > On 16/01/18 12:15 PM, david...@freevolt.org wrote: > >> Is there a natural law or something, that every email message sent >> must contain at least one distracting error that is totally beside the >> point? >> >> Anyways, over and out. > > "Over" means

Re: scriptable way to list packages that are not installed

The Wanderer writes: > I usually think of "Over and out" as being effectively equivalent to > "You can respond if you want to, but I'm not going to be listening". If I say that I mean "I am done transmitting. I will listen for your final transmission." If you have nothing more to say you should

Re: scriptable way to list packages that are not installed

On 2018-01-16 at 21:17, Charlie Gibbs wrote: > On 16/01/18 12:15 PM, david...@freevolt.org wrote: > >> Is there a natural law or something, that every email message sent >> must contain at least one distracting error that is totally beside the >> point? >> >> Anyways, over and out. > > "Over"

Re: scriptable way to list packages that are not installed

On 16/01/18 12:15 PM, david...@freevolt.org wrote: Is there a natural law or something, that every email message sent must contain at least one distracting error that is totally beside the point? Anyways, over and out. "Over" means "My transmission is finished; I expect a reply." "Out" means

Re: scriptable way to list packages that are not installed

On Tue, 16 Jan 2018, davidson wrote: On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote: Hi, John, On Sun, Jan 14, 2018 at 8:48 AM, john doe wrote: On 1/14/2018 7:28 AM, john doe wrote: $ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk cmake 2>&1 |

Re: scriptable way to list packages that are not installed

On Tue, 16 Jan 2018, davidson wrote: On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote: Hi, John, On Sun, Jan 14, 2018 at 8:48 AM, john doe wrote: On 1/14/2018 7:28 AM, john doe wrote: $ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk cmake 2>&1 |

Re: scriptable way to list packages that are not installed

On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote: Hi, John, On Sun, Jan 14, 2018 at 8:48 AM, john doe wrote: On 1/14/2018 7:28 AM, john doe wrote: $ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk cmake 2>&1 | awk '!/^ii/ || !/^un/{print $6}' git gawk

Re: scriptable way to list packages that are not installed

Hi, On Sun, 14 Jan 2018 22:18:26 +0200 Vasyl Vavrychuk wrote: > Hi, John, > > On Sun, Jan 14, 2018 at 8:48 AM, john doe wrote: > > On 1/14/2018 7:28 AM, john doe wrote: > > > > $ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git > >

Re: scriptable way to list packages that are not installed

Hi, John, On Sun, Jan 14, 2018 at 8:48 AM, john doe wrote: > On 1/14/2018 7:28 AM, john doe wrote: > > $ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk > cmake 2>&1 | awk '!/^ii/ || !/^un/{print $6}' > git > gawk > cmake I also tried to parse

Re: scriptable way to list packages that are not installed

Vasyl Vavrychuk wrote: > I would like to list not installed packages in my script. could this help you (if I understood right, that you want to know, if some of the packages (in this case) gawk, git, cmake are not installed: dpkg -l gawk git cmake | awk /^un/'{print $2}' cmake git Bernd

Re: scriptable way to list packages that are not installed

On Sun, Jan 14, 2018 at 05:52:45AM +0200, Vasyl Vavrychuk wrote: > I would like to list not installed packages in my script. Currently I do > > dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' > $PACKAGES | grep -v "^ii" | awk '{print $2}' > You may want to consider libdpkg-perl,

Re: scriptable way to list packages that are not installed

On 14-01-2018 01:52, Vasyl Vavrychuk wrote: > I would like to list not installed packages in my script. aptitude search '!~i' is a start It's possible to configure the output, see the manpage. -- Any excuse will serve a tyrant. -- Aesop Eduardo M KALINOWSKI

Re: scriptable way to list packages that are not installed

On 1/14/2018 7:28 AM, john doe wrote: On 1/14/2018 4:52 AM, Vasyl Vavrychuk wrote: I would like to list not installed packages in my script. Currently I do dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' $PACKAGES | grep -v "^ii" | awk '{print $2}' As an aside; you don't need

Re: scriptable way to list packages that are not installed

On 1/14/2018 4:52 AM, Vasyl Vavrychuk wrote: I would like to list not installed packages in my script. Currently I do dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' $PACKAGES | grep -v "^ii" | awk '{print $2}' As an aside; you don't need grep in this command: $ | awk

scriptable way to list packages that are not installed

I would like to list not installed packages in my script. Currently I do dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' $PACKAGES | grep -v "^ii" | awk '{print $2}' Problem is that dpkg-query outputs information about no matching packages in stderr in a not suitable for scripts