I'd like to run some unit tests as part of an RPM build.  I've set it up so that Xvnc gets started and the tests run in it (some are GUI tests that need X to run).  This fails in koji due to the fact that dbus can't start.  Colin Walters kindly wrote a small patch to fix this and posted it here:

http://fpaste.org/paste/5434

In case that gets erased, I'll copy it here:

diff --git a/py/mock/backend.py b/py/mock/backend.py
index 3cc0a9f..566f615 100644
--- a/py/mock/backend.py
+++ b/py/mock/backend.py
@@ -13,6 +13,7 @@ import logging
 import os
 import shutil
 import stat
+import uuid
 
 # our imports
 import mock.util
@@ -207,6 +208,7 @@ class Root(object):
         self.root_log.debug('touch required files')
         for item in [self.makeChrootPath('etc', 'mtab'),
                      self.makeChrootPath('etc', 'fstab'),
+                     self.makeChrootPath('var', 'lib', 'dbus')]:
                      self.makeChrootPath('var', 'log', 'yum.log')]:
             mock.util.touch(item)
 
@@ -233,6 +235,15 @@ class Root(object):
                 os.remove(resolvpath)
             shutil.copy2('/etc/resolv.conf', resolvdir)
 
+        # Anything that tries to use libdbus inside the chroot will require this
+        # FIXME - merge this code with other OS-image building code
+        machine_uuid = uuid.uuid4().hex()
+        dbus_uuid_path = self.makeChrootPath('var', 'lib', 'dbus', 'machine-id')
+        f = open(dbus_uuid_path, 'w')
+        f.write(machine_uuid)
+        f.write('\n')
+        f.close()
+
         # files in /etc that need doing
         for key in self.chroot_file_contents:
             p = self.makeChrootPath(key)