Re: Getting rpm update history with wildcarding

2018-06-15 Thread Todd Zullinger
Ed Greshko wrote: > On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan > wrote: > >> On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote: >>> [egreshko@meimei ~]$ rpm -qa pulse* >>> pulseaudio-11.1-18.fc28.1.x86_64 >>> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64 >>> pulseaudio-module-x11-11.1-

Re: Getting rpm update history with wildcarding

2018-06-15 Thread Ed Greshko
On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan wrote: > On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote: > > On 06/15/18 13:44, Todd Zullinger wrote: > > > Tim via users wrote: > > > > Allegedly, on or about 14 June 2018, Todd Zullinger sent: > > > > > To be fair, I don't think the rpm man p

Re: Getting rpm update history with wildcarding

2018-06-15 Thread Patrick O'Callaghan
On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote: > On 06/15/18 13:44, Todd Zullinger wrote: > > Tim via users wrote: > > > Allegedly, on or about 14 June 2018, Todd Zullinger sent: > > > > To be fair, I don't think the rpm man page documents its > > > > wildcard support. If it does, I'm lookin

Re: Getting rpm update history with wildcarding

2018-06-15 Thread Ed Greshko
On 06/15/18 13:44, Todd Zullinger wrote: > Tim via users wrote: >> Allegedly, on or about 14 June 2018, Todd Zullinger sent: >>> To be fair, I don't think the rpm man page documents its >>> wildcard support. If it does, I'm looking past it. >> I've always successfully done things like this: >> >>

Re: Getting rpm update history with wildcarding

2018-06-15 Thread Patrick O'Callaghan
On Fri, 2018-06-15 at 01:44 -0400, Todd Zullinger wrote: > Tim via users wrote: > > Allegedly, on or about 14 June 2018, Todd Zullinger sent: > > > To be fair, I don't think the rpm man page documents its > > > wildcard support. If it does, I'm looking past it. > > > > I've always successfully do

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Todd Zullinger
Tim via users wrote: > Allegedly, on or about 14 June 2018, Todd Zullinger sent: >> To be fair, I don't think the rpm man page documents its >> wildcard support. If it does, I'm looking past it. > > I've always successfully done things like this: > > rpm -qa \*pulse\* > > More through force of

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Tim via users
Allegedly, on or about 14 June 2018, Todd Zullinger sent: > To be fair, I don't think the rpm man page documents its > wildcard support. If it does, I'm looking past it. I've always successfully done things like this: rpm -qa \*pulse\* More through force of habit, than any hard knowledge. --

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Rick Stevens
On 06/14/2018 09:23 AM, Robert Moskowitz wrote: > > > On 06/14/2018 09:57 AM, Richard Shaw wrote: >> On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz > > wrote: >> >> >> On 06/14/2018 09:08 AM, Ahmad Samir wrote: >> > On 14 June 2018 at 14:27, Robert Moskowitz

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Todd Zullinger
Robert Moskowitz wrote: > Ah, I left off the 'list' portion of your command > > # dnf history list pulseaudio* > ID | Command line | Date and time| Action(s) | > Altered > --- > 2 | update

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Todd Zullinger
Robert Moskowitz wrote: > On 06/14/2018 09:57 AM, Richard Shaw wrote: >> Don't include the tick marks, it tried to execute what's inside... What >> he means is that rpm doesn't accept wildcards so if you want to find >> partial matches, you need to pipe it to grep... >> >> # rpm -qa | grep pulseau

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Robert Moskowitz
On 06/14/2018 10:54 AM, Ed Greshko wrote: On 06/14/18 22:23, Tony Nelson wrote: That is not what he means.  Would one of you please look at the RPM man page? Sure    --last Orders the package listing by install time such  that  the  latest   packages are at the top.

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Robert Moskowitz
On 06/14/2018 09:57 AM, Richard Shaw wrote: On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz > wrote: On 06/14/2018 09:08 AM, Ahmad Samir wrote: > On 14 June 2018 at 14:27, Robert Moskowitz mailto:r...@htt-consult.com>> wrote: >> I want to get history

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Ed Greshko
On 06/14/18 22:23, Tony Nelson wrote: > That is not what he means.  Would one of you please look at the RPM > man page? Sure    --last Orders the package listing by install time such  that  the  latest   packages are at the top. which has nothing to do with "history".  If,

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Todd Zullinger
Tony Nelson wrote: > That is not what he means. Would one of you please look > at the RPM man page? To be fair, I don't think the rpm man page documents its wildcard support. If it does, I'm looking past it. -- Todd ~~ From th

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Todd Zullinger
Richard Shaw wrote: > On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz > wrote: > >> >> On 06/14/2018 09:08 AM, Ahmad Samir wrote: >>> FWIW, to match using a wildcard you'd have to use `rpm -qa pulseaudio*`. >> >> Don't think so: >> >> # `rpm -qa pulseaudio*` >> bash: pulseaudio-module-bluetooth-

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Tony Nelson
On 18-06-14 09:57:33, Richard Shaw wrote: On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz wrote: > > On 06/14/2018 09:08 AM, Ahmad Samir wrote: > > On 14 June 2018 at 14:27, Robert Moskowitz wrote: > >> I want to get history for all the pulseaudio components (to update my > >> audacity b

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Richard Shaw
On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz wrote: > > On 06/14/2018 09:08 AM, Ahmad Samir wrote: > > On 14 June 2018 at 14:27, Robert Moskowitz wrote: > >> I want to get history for all the pulseaudio components (to update my > >> audacity bug report at rpmfusion). > >> > >> #rpm -q pulsea

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Robert Moskowitz
On 06/14/2018 09:08 AM, Ahmad Samir wrote: On 14 June 2018 at 14:27, Robert Moskowitz wrote: I want to get history for all the pulseaudio components (to update my audacity bug report at rpmfusion). #rpm -q pulseaudio --last produces pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 May

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Ahmad Samir
On 14 June 2018 at 14:27, Robert Moskowitz wrote: > I want to get history for all the pulseaudio components (to update my > audacity bug report at rpmfusion). > > #rpm -q pulseaudio --last > > produces > > pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 May 2018 09:59:34 PM > EDT > > but > >

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Ed Greshko
On 06/14/18 20:32, Richard Shaw wrote: > On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz > wrote: > > I want to get history for all the pulseaudio components (to update my > audacity bug report at rpmfusion). > > #rpm -q pulseaudio --last > > produces

Re: Getting rpm update history with wildcarding

2018-06-14 Thread Richard Shaw
On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz wrote: > I want to get history for all the pulseaudio components (to update my > audacity bug report at rpmfusion). > > #rpm -q pulseaudio --last > > produces > > pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 May 2018 09:59:34 > PM EDT > > b

Getting rpm update history with wildcarding

2018-06-14 Thread Robert Moskowitz
I want to get history for all the pulseaudio components (to update my audacity bug report at rpmfusion). #rpm -q pulseaudio --last produces pulseaudio-11.1-18.fc28.1.x86_64  Thu 24 May 2018 09:59:34 PM EDT but # rpm -q pulseaudio* --last results in: package