Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 912998 Details for
Bug 1114183
[abrt] yum: yummain.py:106:exRepoError:AttributeError: 'YumSqlitePackageSack' object has no attribute 'id'
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
File: backtrace
backtrace (text/plain), 2.01 KB, created by
Robin Lee
on 2014-06-28 09:24:23 UTC
(
hide
)
Description:
File: backtrace
Filename:
MIME Type:
Creator:
Robin Lee
Created:
2014-06-28 09:24:23 UTC
Size:
2.01 KB
patch
obsolete
>yummain.py:106:exRepoError:AttributeError: 'YumSqlitePackageSack' object has no attribute 'id' > >Traceback (most recent call last): > File "/usr/bin/yum", line 29, in <module> > yummain.user_main(sys.argv[1:], exit_code=True) > File "/usr/share/yum-cli/yummain.py", line 367, in user_main > errcode = main(args) > File "/usr/share/yum-cli/yummain.py", line 178, in main > return exRepoError(e) > File "/usr/share/yum-cli/yummain.py", line 106, in exRepoError > repoid = e.repo.id >AttributeError: 'YumSqlitePackageSack' object has no attribute 'id' > >Local variables in innermost frame: >e: RepoError() >unlock: <function unlock at 0xfff140> >base: <cli.YumBaseCli object at 0xffaa50> >repoui: u'Unknown' >msg: u' One of the configured repositories failed (%(repo)s),\n and yum doesn\'t have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work "fix" this:\n\n 1. Contact the upstream for the repository and get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for the repository, to point to a working\n upstream. This is most often useful if you are using a newer\n distribution release than is supported by the repository (and the\n packages for the previous distribution release still work).\n\n 3. Disable the repository, so yum won\'t use it by default. Yum will then\n just ignore the repository until you permanently enable it again or use\n --enablerepo for temporary usage:\n\n yum-config-manager --disable %(repoid)s\n\n 4. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum will try to contact the repo. when it runs most commands,\n so will have to try and fail each time (and thus. yum will be be much\n slower). If it is a very temporary problem though, this is often a nice\n compromise:\n\n yum-config-manager --save --setopt=%(repoid)s.skip_if_unavailable=true\n' >logger: <logging.Logger object at 0xebb9d0> >repoid: u'<repoid>'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1114183
: 912998 |
912999