Created attachment 523725 [details]
Description of problem:
I ran yum update today on my rhel6 x86_64 box. Luci no longer starts. An abrt report is created.
Version-Release number of selected component (if applicable):
python-repoze-who-friendlyform 1.0.8-2.el6 vs. luci-0.23.0-17.el6.x86_64
service luci restart
Steps to Reproduce:
service luci start indicates the service has started, but it does not
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
AFAIK, the only N-V-R of that package that Red Hat has shipped was:
It looks like that version of friendlyform is in EPEL 6:
but appears to be the only version that's been built into EPEL6:
Looking in backtrace in that ABRT tarball I see the error is:
pkg_resources.py:550:resolve:VersionConflict: (WebOb 0.9.6.1 (/usr/lib/python2.6/site-packages), Requirement.parse('WebOb>=0.9.7'))
Looking in the 1.0.8 tarball, within:
install_requires=['repoze.who >= 1.0', 'zope.interface', 'WebOb>=0.9.7'],
whereas in the 1.0b3 tarball, within:
I merely see:
install_requires=['repoze.who >= 1.0', 'zope.interface'],
That new requirement on "WebOb" isn't reflected in the metadata of that EPEL6 rpm, and currently, within RHEL6, we're shipping python-webob-0.9.6.1, which wouldn't satisfy that version.
CCing Toshio re the EPEL6 package.
I am sorry I didn't realize this was an EPEL package! Do I need to close this and open a different BZ?
Reassigning to EPEL package as per comment 3. I thought that EPEL shouldn't ship a package if RHEL has it. Is that not true?
Wow, three year old bug. :) Yes, EPEL should not ship a package if RHEL has it. I'll figure out how to get this blocked in epel 6.
Retired in pkgdb and git, ticket filed to block in EPEL. Won't help those people who already have the package installed, but new users shouldn't hit this issue.