Bug 18507 - Unable to add/remove packages
Summary: Unable to add/remove packages
Status: RESOLVED NOTOURBUG
Alias: None
Product: PackageKit
Classification: Unclassified
Component: backend-yum (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-12 14:05 UTC by Jacque
Modified: 2008-11-13 07:22 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 Jacque 2008-11-12 14:05:14 UTC
Error Type: <type 'exceptions.TypeError'>
Error Value: 'NoneType' object is unsubscriptable
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2202, in <module>
    main()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2199, in main
    backend.dispatcher(sys.argv[1:])
  File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 599, in dispatcher
    self.dispatch_command(args[0], args[1:])
  File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 525, in dispatch_command
    self.refresh_cache()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1128, in refresh_cache
    self.yumbase.repos.populateSack(which=[repo.id], mdtype='metadata', cacheonly=1)
  File : /usr/lib/python2.5/site-packages/yum/repos.py, line 223, in populateSack
    self.doSetup()
  File : /usr/lib/python2.5/site-packages/yum/repos.py, line 71, in doSetup
    self.ayum.plugins.run('postreposetup')
  File : /usr/lib/python2.5/site-packages/yum/plugins.py, line 176, in run
    func(conduitcls(self, self.base, conf, **kwargs))
  File : /usr/lib/yum-plugins/rpm-warm-cache.py, line 31, in postreposetup_hook
    if commands[0] in ('upgrade', 'install', 'remove'):
Comment 1 Richard Hughes 2008-11-13 07:22:26 UTC
If you remove yum-rpm-warm-cache then the problem will not happen. This is not a PackageKit bug, sorry.


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.