Description of problem: Running 'fedora-review -n <name>' Version-Release number of selected component: yum-3.4.3-148.fc20 Additional info: reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/yum makecache executable: /usr/bin/yum kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: 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>'
Created attachment 912998 [details] File: backtrace
Created attachment 912999 [details] File: environ
Another user experienced a similar problem: Happened after running yum makecache reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/bin/yum makecache executable: /usr/bin/yum kernel: 3.15.6-200.fc20.x86_64 package: yum-3.4.3-152.fc20 reason: yummain.py:106:exRepoError:AttributeError: 'YumSqlitePackageSack' object has no attribute 'id' runlevel: N 5 type: Python uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This is also seen on Fedora 21, using yum-3.4.3-153.fc21 on ppc64.
I see this on Fedora 21 using yum-3.4.3-153.fc21 on x86_64 after yum groupinstall "KDE ..." -y --skip-broken doing: yum makecache, solve it !?
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.