Bug 546316 (aeromechengr) - Yum Update Error
Summary: Yum Update Error
Keywords:
Status: CLOSED DUPLICATE of bug 541645
Alias: aeromechengr
Product: Fedora
Classification: Fedora
Component: yum
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-10 16:26 UTC by jdaviator24
Modified: 2014-01-21 23:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-10 16:31:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jdaviator24 2009-12-10 16:26:24 UTC
Description of problem:

I upgraded Fedora 11 to Fedora 12. After upgrading, I went in to do a yum update and I get the following error message when I try doing a software update:

Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module>
    main()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
    backend.dispatcher(sys.argv[1:])
  File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 699, in dispatcher
    self.dispatch_command(args[0], args[1:])
  File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command
    self.update_packages(only_trusted, package_ids)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages
    signed = self._is_package_repo_signed(pkg)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed
    repo = self.yumbase.repos.getRepo(pkg.repoid)
  File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo
    'Error getting repository data for $s, repository not found' $ (repoid)

Comment 1 seth vidal 2009-12-10 16:31:05 UTC

*** This bug has been marked as a duplicate of bug 541645 ***


Note You need to log in before you can comment on or make changes to this bug.