Bug 234109 - An unknown error has occured
Summary: An unknown error has occured
Status: RESOLVED UPSTREAM
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: The Boson Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-11 23:34 UTC by jeremypass
Modified: 2010-07-21 17:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jeremypass 2010-04-11 23:34:10 UTC
Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    I Don't Know

These are the details from KPackageKit:

Error Type: 
Error Value: Error getting repository data for installed, repository not found
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in 
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)
Comment 1 Andreas Beckermann 2010-04-17 18:39:47 UTC
This has nothing to do with boson - reassigning to KPackageKit. Though this report seems pretty useless to me, the reporter did not even specify what went wrong or what he/she tried to do...
Comment 2 Jonathan Thomas 2010-07-21 17:30:38 UTC
This is a problem with the Yum PackageKit backend itself, not KPackageKit. Please report this bug to Fedora.