Bug 18834 - rpmdb open failed
Summary: rpmdb open failed
Status: RESOLVED FIXED
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-01 10:06 UTC by gang chen
Modified: 2012-01-05 10:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gang chen 2008-12-01 10:06:41 UTC
Error Type: <type 'exceptions.TypeError'>
Error Value: rpmdb open failed
  File : /usr/share/PackageKit/helpers/yum/search-name.py , line 20, in <module>
    backend = PackageKitYumBackend(sys.argv[1:],lock=False)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 242, in __init__
    self._setup_yum()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py , line 1555, in _setup_yum
    self.yumbase.doConfigSetup(errorlevel=0,debuglevel=0)     # Setup Yum Config
  File : /usr/lib/python2.5/site-packages/yum/__init__.py , line 139, in doConfigSetup
    errorlevel=errorlevel)
  File : /usr/lib/python2.5/site-packages/yum/__init__.py , line 191, in _getConfig
    self._conf = config.readMainConfig(startupconf)
  File : /usr/lib/python2.5/site-packages/yum/config.py , line 753, in readMainConfig
    yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
  File : /usr/lib/python2.5/site-packages/yum/config.py , line 823, in _getsysver
    idx = ts.dbMatch('provides', distroverpkg)
Comment 1 Richard Hughes 2008-12-02 00:38:02 UTC
commit 3018a83e2963b09133b462ea0f1d0d067b02a463
Author: Richard Hughes <richard@hughsie.com>
Date:   Tue Dec 2 08:36:35 2008 +0000

    yum: catch all exceptions from self.yumbase.doConfigSetup() as yum doesn't seem capable of catching it's own except


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.