Software Installation History

Get info about yum package installation history 

rpm:

# rpm -qa –last

# yum list installed

# yum history [sub command]

Yum History Sub-Commands:

(from yum manpage)
history

The history command allows the user to view what has happened in
past transactions (assuming the history_record config. option is
set).  You can use info/list/packages-list/packages-info/summary
to view what happened, undo/redo/rollback to act on that  infor‐
mation and new to start a new history file.

The info/list/summary commands take either a transaction id or a
package (with wildcards, as in Specifying  package  names),  all
three  can  also  be passed no arguments. list can be passed the
keyword “all” to list all the transactions.

The info command can also take ranges of transaction ids, of the
form  start..end, which will then display a merged history as if
all the transactions in the range had happened at once.
Eg. “history info 1..4” will merge the first  four  transactions
and display them as a single transaction.

The  packages-list/packages-info commands takes a package  (with
wildcards, as in Specifying package names). And show  data  from
the point of view of that package.

The undo/redo/rollback commands take either a single transaction
id or the keyword last and an offset from the  last  transaction
(Eg.  if you’ve done 250 transactions, “last” refers to transac‐
tion 250, and “last-4” refers to  transaction  246).   The  redo
command can also take some optional arguments before you specify
the transaction. “force-reinstall” tells it reinstall any  pack‐
ages  that  were  installed  in  that  transaction (via install,
upgrade or downgrade).   “force-remove”  tells  it  to  forcibly
remove any packages that were updated or downgraded.

The   undo/redo  commands  act  on  the  specified  transaction,
undo’ing or repeating the work of that  transaction.  While  the
rollback  command  will undo all transactions up to the point of
the specified transaction. For example, if you have  3  transac‐
tions,  where  package  A; B and C where installed respectively.
Then “undo 1” will try to remove package A, “redo 1” will try to
install  package A (if it is not still installed), and “rollback
1” will try to remove packages B and C. Note that after a “roll‐
back  1” you will have a fourth transaction, although the ending
rpmdb version (see: yum version) should be the same in  transac‐
tions 1 and 4.

The addon-info command takes a transaction ID, and the packages-
list command takes a package (with wildcards).

The stats command shows some statistics about the  current  his‐
tory DB.

The  sync  commands  allows  you  to change the rpmdb/yumdb data
stored for any installed packages, to whatever is in the current
rpmdb/yumdb (this is mostly useful when this data was not stored
when the package went into the history DB).

In “history list” you can change the behaviour of the 2nd column
via the configuration option history_list_view.

In  “history  list”  output  the  Altered column also gives some
extra information if there  was  something  not  good  with  the
transaction (this is also shown at the end of the package column
in the packages-list command).

– The rpmdb was changed, outside yum, after the transaction.
< – The rpmdb was changed, outside yum, before the transaction.
* – The transaction aborted before completion.
# – The transaction completed, but with a non-zero status.
E – The transaction completed fine, but had warning/error output
during the transaction.
P – The transaction completed fine, but problems already existed
in the rpmdb.
s –  The  transaction  completed  fine,  but  –skip-broken  was
enabled and had to skip some packages.

this

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s