[Yum-devel] [PATCH] Fix rpm chroot insanity, so we can access the history DB from unInstStop() cb.

James Antill james at and.org
Wed Jun 22 22:42:49 UTC 2011

 So the problem is that AGAIN, when we log stuff for installed rpms we
do it in _instCloseFile, which is outside the chroot ... but when we log
stuff for erase rpms we do it in _unInstStop, which is inside the
 sqlite will open it's journal file, which is it has a working path for
from outside the chroot ... being inside the chroot breaks this, which
results in complete failure of everything.

 Proposed fix is to move out of the chroot, before we call the
history/sqlite APIs, and then move back out again ... basically what rpm
does. Seems to work.
 yum/rpmtrans.py |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/yum/rpmtrans.py b/yum/rpmtrans.py
index 400d729..e0b7058 100644
--- a/yum/rpmtrans.py
+++ b/yum/rpmtrans.py
@@ -551,9 +551,15 @@ class RPMTransaction:
         if txmbr is not None:
+            #  Note that we are now back outside the smegging chroot, which
+            # confuses the heck out of sqlite when it tries to open it's journal
+            # file. So let's have fun:
+            os.chroot(".")
             pid   = self.base.history.pkg2pid(txmbr.po)
             state = self.base.history.txmbr2state(txmbr)
             self.base.history.trans_data_pid_end(pid, state)
+            os.chroot(self.base.conf.installroot)
             self.ts_done(txmbr.po, txmbr.output_state)

More information about the Yum-devel mailing list