[SOLVED] yum.Errors.RepoError

[LazarusLong]

I've just installed Fedora 12 on two different machines. One is a fresh install on an HP desktop, the other is an update from 10 on a dell lappy.

Install was successfull, but I am having the same problem with updates on both machines.

The update list seems to get populated just fine (938 updates on my lap!). When I start the install process it identifies some other depencies that need updating as well. When I click install in that dialog this error pops up.

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 710, 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)

It says it can't find a repository, but it doesn't say which one it is looking for, so I don't even know where to start. I also can't tell if perhaps the error is in the python script itself, based on the last line.

I've seen this error reported elsewhere, but haven't seen any solutions yet. Anyone have a start point?

[glennzo]

Try

su
yum clean all
yum update

[LazarusLong]

Thanks Glennzo, this appears to have done the trick.

Found the solution here as well. I haven't reached a point where I'm running the Software Updates GUI, so it'll be interesting to see if this update fixed this problem.