Description of problem:
On my F12, when try to run bkr:
[hpt@localhost tier1]$ bkr --help
Traceback (most recent call last):
File "/usr/bin/bkr", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 2655, in <module>
File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 648, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 546, in resolve
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 592795 has been marked as a duplicate of this bug. ***
*** Bug 593996 has been marked as a duplicate of this bug. ***
Closing this now. Since we have proper repos without the need for rhts-release anymore.
If you found this bug and you still have issues follow the instructions here to install the beaker repo for your platform:
And remove the rhts-release rpm from your system
rpm -e rhts-release
*** Bug 609248 has been marked as a duplicate of this bug. ***
*** Bug 602341 has been marked as a duplicate of this bug. ***
I am reopening this bug..
Following the instructions on an F11 laptop, I get the following issue:
beaker-client-0.5.32-2.fc11.noarch from beaker has depsolving problems
--> Missing Dependency: beaker is needed by package beaker-client-0.5.32-2.fc11.noarch (beaker)
Error: Missing Dependency: beaker is needed by package beaker-client-0.5.32-2.fc11.noarch (beaker)
i can't find beaker.rpm anywhere, thought it seemed like rhts repo had it in its metadata but the actual package didn't exist.
Yes, I did remove rhts-release, subsequently rhts repo as well.
For sure F11 is not supported anymore.
Upgrade is recommended.
(In reply to comment #12)
> For sure F11 is not supported anymore.
> Upgrade is recommended.
Yes, I understand that.
However, I was pointing to the fact that beaker-client package has a requires for beaker package which doesn't exist in beaker repo. At least for F11 , it doesn't.
I don't know if this is carried over to newer version, if it's not , then there is no issue, but if it's this should be fixed.
Hi Gurzhan, from what I can tell it is in the F13 repo
As marian has pointed out, the F13 repo is just symlinked to el6. So there's a chance there may still be conflicts