Conary:conary rblist

From rPath Wiki

Conary's rollback system works like a push-pop stack in which rollbacks are "pushed" onto the stack when changesets are applied and "popped" off the stack when a rollback command is issued. If you wish to restore to a system configuration from a previous time, identify the rollback representing that desired point in time (using conary rblist), and "pop" the stack to that level by repeatedly applying the most recent rollback (using conary rollback).

Use conary rblist to list all available rollbacks. Since the amount of output is likely to be quite large, consider piping it through less:

# conary rblist
r.686:
        updated: zile(:data :doc :runtime) contrib.rpath.org@rpl:devel/2.2.16-1-1 -> 2.2.18-1-1
r.685:
...
r.1:
        installed: info-daemon (:user) conary.rpath.com@rpl:1/1-1-0.1

r.0:
        info-haldaemon (:user) conary.rpath.com@rpl:1/1-2-0.1

Each rollback is listed from newest to oldest. A unique name is given to each rollback in the list using the format r.<sequence-number>, where <sequence-number> starts at zero and increments.

The information displayed for each rollback includes:

• The rollback name
• The operation performed on the system that created the rollback
• For update and erase operations, the old version
• For update and install operations, the new version

In the example, the last rollback (r.686) represents the update of zile from version 2.2.16-1-1 to version 2.2.18-1-1.