Description of problem: When upgrading from FC3 to FC4 with yum, I "accidently" tried to remove an unneeded package at the same time with "rpm -e". This resulted in yum's updating of packages to terminate leaving the rpmdb in an very consistent state. I guess sets up the rpm db transaction first before upgrading the packages. Steps to Reproduce: 1. install FC3 2. install fedora-release of fc4 3. yum upgrade 4. while that is updating packages run "rpm -e". Actual results: Yum aborted updating, leaving rpmdb with fc4 pkg data but only about half the packages actually upgraded. :-( Expected results: rpm -e to wait for lock on rpmdb to be freed. Additional info: Cleaning up after this is not fun... ;-) (Yes, I know, I will use anaconda next, honest!)
Sorry I haven't commented on this - but I don't think this is a yum bug. it seems more like an rpm bug. on the yum side I've done some thinking about how to fix the problem of being halfway done with a transaction and how to complete it but it's not going to happen tomorrow. I guess I'll refile this under rpm.
Yum aborted and left a partially installed transaction, and it's yum, not rpm, where the fix needs to happen. I guess I'll send the problem back to yum where the fix is needed.
Shouldn't there have been a transaction lock and the rpm -e wait for lock (waiting for transaction lock)
I wish...
Doing something like this isn't really supported due to problems like this which can occur