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)
We're missing some information here. But first, I'd suggest you do
this:
> sudo rm -rf /var/chache/yum/*
This will manually flush all potentially inconsistent yum data.
You also haven't mentioned the existence of any non-Fedora
repositories in /etc/yum.repos.d/, which might contribute to this
issue.
Let me clarify.
I just ran yum -update a few minutes ago as root from inside a
terminal. And, you know what, it ran perfectly.
The above problem arose when the software update program (which is a
front end to yum) performed a routine software update. There seems to
be an inconsistency between what the front end program sees and the
actual repositories that the yum program sees. I'll try what you
suggested and get back to you.
*Interesting*. There may be some fascinating console interaction,
since a cron job or other applications wouldn't have a tty associated
with their output. But I also wonder if your upstream repository, as
selected by the yum mirror configurations, was having its own issues
and causing other clients to have trouble?