Getting rpm update history with wildcarding

[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                                       pulseaudio* is not installed

so how can I see all components, particularly when I don't know what 
they are?

thanks

[Richard Shaw]

On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz <rgm(a)htt-consult.com&gt;
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
>
>  # rpm -q pulseaudio* --last
>
>  results in:
>
>  package                                       pulseaudio* is not installed
>
>  so how can I see all components, particularly when I don't know what
>  they are?
>  
To my knowledge, RPM doesn't keep a history in the database, it's more of a
current state... But there are logs that probably have what you're looking
for:

(sudo or as root)
# grep pulseaudio /var/log/dnf.rpm.*

Thanks,
Richard

[Ed Greshko]

On 06/14/18 20:32, Richard Shaw wrote:
>  On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz
> <rgm(a)htt-consult.com
>  <mailto:[e-mail]>> 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
>
>      # rpm -q pulseaudio* --last
>
>      results in:
>
>      package                                       pulseaudio* is not installed
>
>      so how can I see all components, particularly when I don't know what
>      they are?
>
>
>  To my knowledge, RPM doesn't keep a history in the database, it's more of a
> current
>  state... But there are logs that probably have what you're looking for:
>
>  (sudo or as root)
>  # grep pulseaudio /var/log/dnf.rpm.*
>
>  
Of course one could also use the "dnf history" command.


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a fact.

[Ahmad Samir]

On 14 June 2018 at 14:27, Robert Moskowitz <rgm(a)htt-consult.com&gt; 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
>
>  # rpm -q pulseaudio* --last
>  
FWIW, to match using a wildcard you'd have to use `rpm -qa pulseaudio*`.

--
Ahmad Samir

[Robert Moskowitz]

On 06/14/2018 09:08 AM, Ahmad Samir wrote:
>  On 14 June 2018 at 14:27, Robert Moskowitz
> <rgm(a)htt-consult.com&gt; 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
> >
> > # rpm -q pulseaudio* --last
> >
>  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-11.1-18.fc28.1.x86_64: command not found

[Richard Shaw]

On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz <rgm(a)htt-consult.com&gt;
wrote:

>  On 06/14/2018 09:08 AM, Ahmad Samir wrote:
>  > On 14 June 2018 at 14:27, Robert Moskowitz <rgm(a)htt-consult.com&gt; 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
>  >>
>  >> # rpm -q pulseaudio* --last
>  >>
>  > 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-11.1-18.fc28.1.x86_64: command not found
>  
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 pulseaudio

Richard

[Tony Nelson]

On 18-06-14 09:57:33, Richard Shaw wrote:
>  On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
> <rgm(a)htt-consult.com&gt;
>  wrote:
>  
>  >
>  > On 06/14/2018 09:08 AM, Ahmad Samir wrote:
>  > > On 14 June 2018 at 14:27, Robert Moskowitz <rgm(a)htt-consult.com&gt;  
>  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
>  > >>
>  > >> # rpm -q pulseaudio* --last
>  > >>
>  > > 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-11.1-18.fc28.1.x86_64: command  
>  not found
>  >
>  
>  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 pulseaudio 
That is not what he means.  Would one of you please look at the RPM
man page?

-- 
____________________________________________________________________
TonyN.:'                       <mailto:[e-mail]>
       '                              <http://www.georgeanelson.com/>

[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 there to here, from here to there, funny things are everywhere.
    -- Dr. Seuss, One Fish Two Fish, Red Fish Blue Fish

[Tim]

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.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

If you are not the intended recipient, why are you reading their email?
You bastard!

[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 habit, than any hard knowledge. 
Yeah.  That's worked for as long as I can remember.  I just
noticed while looking at the man page that it's apparently
not documented. :)

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It's not denial. I'm just very selective about what I accept as
reality.
    -- Calvin ("Calvin and Hobbes")

[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 done things like this:
>  > 
>  > rpm -qa \*pulse\*
>  > 
>  > More through force of habit, than any hard knowledge.
>  
>  Yeah.  That's worked for as long as I can remember.  I just
>  noticed while looking at the man page that it's apparently
>  not documented. :) 
Weird. I've always used that. Probably worth a BZ report.

I wonder what else is undocumented ...

poc

[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:
> >
> > rpm -qa \*pulse\*
> >
> > More through force of habit, than any hard knowledge.
>  Yeah.  That's worked for as long as I can remember.  I just
>  noticed while looking at the man page that it's apparently
>  not documented. :) 
[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-18.fc28.1.x86_64
pulseaudio-libs-11.1-18.fc28.1.x86_64
pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
pulseaudio-utils-11.1-18.fc28.1.x86_64

[egreshko@meimei ~]$ rpm -qa *pulse*
pulseaudio-11.1-18.fc28.1.x86_64
pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64
pulseaudio-module-x11-11.1-18.fc28.1.x86_64
pulseaudio-libs-11.1-18.fc28.1.x86_64
kde-settings-pulseaudio-28.0-2.fc28.noarch
pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
pulseaudio-utils-11.1-18.fc28.1.x86_64

Works fine here.  No escaping needed.  Not that it matters



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a fact.

[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 looking past it.
>  > > 
>  > > I've always successfully done things like this:
>  > > 
>  > > rpm -qa \*pulse\*
>  > > 
>  > > More through force of habit, than any hard knowledge.
>  > 
>  > Yeah.  That's worked for as long as I can remember.  I just
>  > noticed while looking at the man page that it's apparently
>  > not documented. :)
>  
>  [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-18.fc28.1.x86_64
>  pulseaudio-libs-11.1-18.fc28.1.x86_64
>  pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  pulseaudio-utils-11.1-18.fc28.1.x86_64
>  
>  [egreshko@meimei ~]$ rpm -qa *pulse*
>  pulseaudio-11.1-18.fc28.1.x86_64
>  pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>  alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64
>  pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>  pulseaudio-libs-11.1-18.fc28.1.x86_64
>  kde-settings-pulseaudio-28.0-2.fc28.noarch
>  pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  pulseaudio-utils-11.1-18.fc28.1.x86_64
>  
>  Works fine here.  No escaping needed.  Not that it matters 
The escaping is a precaution. Your example wouldn't work if you had a
filename starting with 'pulse' in the current directory.

poc

[Ed Greshko]

On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan <pocallaghan(a)gmail.com&gt;
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 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.
>  > >
>  > > Yeah.  That's worked for as long as I can remember.  I just
>  > > noticed while looking at the man page that it's apparently
>  > > not documented. :)
>  >
>  > [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-18.fc28.1.x86_64
>  > pulseaudio-libs-11.1-18.fc28.1.x86_64
>  > pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  > pulseaudio-utils-11.1-18.fc28.1.x86_64
>  >
>  > [egreshko@meimei ~]$ rpm -qa *pulse*
>  > pulseaudio-11.1-18.fc28.1.x86_64
>  > pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>  > alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64
>  > pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>  > pulseaudio-libs-11.1-18.fc28.1.x86_64
>  > kde-settings-pulseaudio-28.0-2.fc28.noarch
>  > pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  > pulseaudio-utils-11.1-18.fc28.1.x86_64
>  >
>  > Works fine here.  No escaping needed.  Not that it matters
>
>  The escaping is a precaution. Your example wouldn't work if you had a
>  filename starting with 'pulse' in the current directory.
>
>
>  
Yeah, but I'm always aware of that possibly. So it's never an issue for me.
I like less typing 😁

[Todd Zullinger]

Ed Greshko wrote:
>  On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan
> <pocallaghan(a)gmail.com&gt;
>  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-18.fc28.1.x86_64
> >> pulseaudio-libs-11.1-18.fc28.1.x86_64
> >> pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
> >> pulseaudio-utils-11.1-18.fc28.1.x86_64
> >>
> >> [egreshko@meimei ~]$ rpm -qa *pulse*
> >> pulseaudio-11.1-18.fc28.1.x86_64
> >> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
> >> alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64
> >> pulseaudio-module-x11-11.1-18.fc28.1.x86_64
> >> pulseaudio-libs-11.1-18.fc28.1.x86_64
> >> kde-settings-pulseaudio-28.0-2.fc28.noarch
> >> pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
> >> pulseaudio-utils-11.1-18.fc28.1.x86_64
> >>
> >> Works fine here.  No escaping needed.  Not that it matters
> >
> > The escaping is a precaution. Your example wouldn't work if you had a
> > filename starting with 'pulse' in the current directory.
>  
>  Yeah, but I'm always aware of that possibly. So it's never an issue for me.
>  I like less typing 😁 
It's your choice to use commands which depend on the state
of your current directory, of course.  But it's a very bad
habit to teach anyone reading this list who may not yet know
the details of shell glob expansion.  There are far better
ways to save two characters in the shell.

When you ask someone to run a command and they don't get the
output you think they should because their current directory
has files matching the unquoted glob, then you haven't saved
them or yourself any typing.

Please, think of the bits! :)

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When we remember we are all mad, the mysteries of life disappear and
life stands explained.
    -- Mark Twain

[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, as the OP suggests, he wishes to know the history of when packages named
pulseaudio* were updated he may run into a problem if he wasn't consistent in the
apps used to perform updates.  First of all, rpm doesn't keep a history of updates. 
He can then run into a problem if he used dnf for some and packagekit utilities for
others.  FWIW, there is a bugzilla requesting that the history recording of those be
unified.

Let's try not to get sidetracked by when/how name expansion is done.

[root@meimei ~]# dnf history list pulseaudio*
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
   251 | --refresh upgrade        | 2018-05-18 08:01 | Update         |    9  
   233 | system-upgrade upgrade   | 2018-05-06 07:53 | D, E, I, O, U  | 2860 EE
   152 | --refresh upgrade        | 2018-03-14 22:01 | E, I, U        |  159 EE
     2 | update                   | 2017-12-21 10:05 | I, O, U        |  654 EE
     1 |                          | 2017-11-05 15:25 | Install        | 1717 EE


Gets me transactions where pulseaudio* was involved. 

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a fact.

[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.
>
>  which has nothing to do with "history".
>
>  If, as the OP suggests, he wishes to know the history of when packages named
>  pulseaudio* were updated he may run into a problem if he wasn't consistent in the
>  apps used to perform updates.  First of all, rpm doesn't keep a history of updates.
>  He can then run into a problem if he used dnf for some and packagekit utilities for
>  others.  FWIW, there is a bugzilla requesting that the history recording of those be
>  unified.
>
>  Let's try not to get sidetracked by when/how name expansion is done.
>
>  [root@meimei ~]# dnf history list pulseaudio*
>  ID     | Command line             | Date and time    | Action(s)      | Altered
>  -------------------------------------------------------------------------------
>      251 | --refresh upgrade        | 2018-05-18 08:01 | Update         |    9
>      233 | system-upgrade upgrade   | 2018-05-06 07:53 | D, E, I, O, U  | 2860 EE
>      152 | --refresh upgrade        | 2018-03-14 22:01 | E, I, U        |  159 EE
>        2 | update                   | 2017-12-21 10:05 | I, O, U        |  654 EE
>        1 |                          | 2017-11-05 15:25 | Install        | 1717 EE
>
>
>  Gets me transactions where pulseaudio* was involved. 
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                   | 2018-05-24 21:54 | I, U           |  341 EE
      1 |                          | 2018-05-24 21:07 | Install        | 1593 EE

Of course it does not tell me WHAT was updated in #2.

But then all of this is before I hit the problems with audacity so I can report that I am
up to date on it...

[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                   | 2018-05-24 21:54 | I, U           |  341 EE
>       1 |                          | 2018-05-24 21:07 | Install        | 1593 EE
>  
>  Of course it does not tell me WHAT was updated in #2.
>  
>  But then all of this is before I hit the problems with audacity so I can report that I am
> up to date on it... 
Use 'dnf history info 2' to get further details on the
transaction.  The usage of dnf history is covered in the dnf
man page.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Life may have no meaning. Or even worse, it may have a meaning of
which I disapprove.
    -- Ashleigh Brilliant

[Todd Zullinger]

Richard Shaw wrote:
>  On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
> <rgm(a)htt-consult.com&gt;
>  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-11.1-18.fc28.1.x86_64: command not found
>  
>  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 pulseaudio 
I don't think Ahmad was saying that "rpm doesn't accept
wildcards" at all.  Quite the opposite; rpm accepts
wildcards, and has for as long as I can remember.

$ rpm -qa 'pulseaudio*'
pulseaudio-gdm-hooks-11.1-15.fc27.x86_64
pulseaudio-utils-11.1-15.fc27.x86_64
pulseaudio-module-x11-11.1-15.fc27.x86_64
pulseaudio-11.1-15.fc27.x86_64
pulseaudio-libs-glib2-11.1-15.fc27.x86_64
pulseaudio-module-bluetooth-11.1-15.fc27.x86_64
pulseaudio-libs-11.1-15.fc27.x86_64

You need to use the -a / --all option when querying with a
glob, e.g. rpm -qa 'foo*' instead of rpm -q 'foo*'.

Whether you prefer to use a glob or pipe to grep is a matter
of preference in most cases.  I try to avoid pipes when they
aren't needed out of habit, but the difference in characters
typed or performance is negligable.  The rpm globbing
support is quite limited, so if you need a more flexible
search string, then grep wins.

One thing note when passing globs to commands like this is
that it's important to quote or escape the glob to prevent
the shell from expanding it.  So either of these work:

    rpm -qa 'pulseaudio*'
    rpm -qa pulseaudio\*

It also works without the quotes as long as you don't have
anything which matches pulseaudio* in the directory where
you run the command.  That lulls many people into complaceny
and then they're surprised when they run it somewhere the
glob is exapnded by the shell and the command behaves
differently.  It's a good habit to always protect those
globs from the shell.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You will never find time for anything.  If you want time you must make
it.
    -- Charles Buxton

[Robert Moskowitz]

On 06/14/2018 09:57 AM, Richard Shaw wrote:
>  On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
> <rgm(a)htt-consult.com 
>  <mailto:[e-mail]>> wrote:
>
>
>      On 06/14/2018 09:08 AM, Ahmad Samir wrote:
>      > On 14 June 2018 at 14:27, Robert Moskowitz <rgm(a)htt-consult.com
>      <mailto:[e-mail]>> 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
>      >>
>      >> # rpm -q pulseaudio* --last
>      >>
>      > 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-11.1-18.fc28.1.x86_64: command
>      not found
>
>
>  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 pulseaudio 
But that does not give me the update history.  Going to have to pipe 
this output into something else

# rpm -qa | grep pulseaudio
pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
pulseaudio-module-x11-11.1-18.fc28.1.x86_64
pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
pulseaudio-utils-11.1-18.fc28.1.x86_64
xfce4-pulseaudio-plugin-0.4.1-1.fc28.x86_64
pulseaudio-libs-11.1-18.fc28.1.x86_64
pulseaudio-11.1-18.fc28.1.x86_64
alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64

[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 pulseaudio
>  
>  But that does not give me the update history.  Going to have to pipe this
>  output into something else
>  
>  # rpm -qa | grep pulseaudio
>  pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>  pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>  pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  pulseaudio-utils-11.1-18.fc28.1.x86_64
>  xfce4-pulseaudio-plugin-0.4.1-1.fc28.x86_64
>  pulseaudio-libs-11.1-18.fc28.1.x86_64
>  pulseaudio-11.1-18.fc28.1.x86_64
>  alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64 
You want to use dnf history, as Ed has said already.

    dnf history list 'pulseaudio*'

You can get further details on each transaction with 'dnf
info' using the transaction ID which 'dnf history list'
inlcudes.  Refer to the dnf man page for details on the dnf
history command.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Any clod can have the facts; having opinions is an art.
    -- Charles McCabe

[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 <rgm(a)htt-consult.com
> > <mailto:[e-mail]>> wrote:
> >
> >
> >     On 06/14/2018 09:08 AM, Ahmad Samir wrote:
> >     > On 14 June 2018 at 14:27, Robert Moskowitz <rgm(a)htt-consult.com
> >     <mailto:[e-mail]>> 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
> >     >>
> >     >> # rpm -q pulseaudio* --last
> >     >>
> >     > 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-11.1-18.fc28.1.x86_64: command
> >     not found
> >
> >
> > 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 pulseaudio
>  
>  But that does not give me the update history.  Going to have to pipe
>  this output into something else
>  
>  # rpm -qa | grep pulseaudio
>  pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>  pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>  pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>  pulseaudio-utils-11.1-18.fc28.1.x86_64
>  xfce4-pulseaudio-plugin-0.4.1-1.fc28.x86_64
>  pulseaudio-libs-11.1-18.fc28.1.x86_64
>  pulseaudio-11.1-18.fc28.1.x86_64
>  alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64 
Again, as other have said, rpm does NOT maintain a history. It queries
the rpm database of what packages are installed and that's it.

dnf and yum maintain histories (I believe packagekit does as well), but
they're accessed in different ways.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-    Overweight:  When you step on your dog's tail...and it dies.    -
----------------------------------------------------------------------