It is one of RPM's best kept secrets is that transactional rollback support is available as a built-in. Transactional RPM rollbacks are just like any other type of transactional rollback, meaning that a log of all actions is kept and that dependencies are also rolled back if necessary. Since Up2date is based upon RPM, it also natively supports it. The following steps describe how to enable it.
As root perform a `up2date --config`
Toggle the “enabledRollbacks” setting to “yes”. Save your config. This will enable you to rollback upgraded packages.
If you also want to be able to roll back install and erase (remove) operations, you will need to modify the /etc/rpm/macros.up2date file and uncomment the '#%_repackage_all_erasures 1' line. (hint: it's the only line in the file)
following an install, if you want to roll back the last change, type `up2date --undo`.
You may also do this with a finer grain of control by using the rpm command like so: `rpm -Uvh --rollback '2 hours ago'`. Here's a few more examples: `rpm -Uvh --rollback '9:00 am'; rpm -Uvh --rollback 'December 25th'`. This is obviously very powerful as it can put your system back to the way it was in a specific point in time.