Hello, On Jun 8 11:04 Michael Schroeder wrote (shortened):
On Mon, Jun 07, 2010 at 08:32:27PM +0200, Cristian Morales Vega wrote:
... what's exactly a RPM transaction?
Everything you feed to rpm (or rpmlib) in one single step, e.g. multiple arguments on the rpm command line. ... Some background: rpm does all the erasures at the end of the (rpm-)transaction. So if a transaction dies in the middle because of a broken scriptlet you've got a very broken system. AFAIK there's no easy way to continue the transaction.
Isn't "all or nothing" the usual semantics of a transaction? I.e. if a transaction dies in the middle, nothing had actually changed. It seems, what is called "RPM transactions" are no usual transactions. But what else is the semantics of "RPM transactions"? I found http://www.linuxjournal.com/article/7034 which talks about RPM rollback via --repackage but it seems we don't use it because there is nothing in /var/spool/repackage on my system and I have "%_repackage_all_erasures 0" and "%_rollback_transaction_on_failure 0" in my /usr/lib/rpm/macros. I guess a reason why we don't we use it is that it may fill up disk space (very important on nowadays zillion GB harddisks ;-) or that RPM's transactional rollback feature might be still a work-in-progress or is there another reason no to use it? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org