Bug 1254372 - Unable to build chromium with ply 3.6
Summary: Unable to build chromium with ply 3.6
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-ply
Version: 23
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 21:59 UTC by Erinn Looney-Triggs
Modified: 2015-09-04 03:24 UTC (History)
2 users (show)

Fixed In Version: 3.6-2.fc23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-04 03:24:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Erinn Looney-Triggs 2015-08-17 21:59:29 UTC
I'll just reference the couple of bug reports I have found about the issue. This is fixed upstream in ply, however there has not been a new release, you may want to add the patches to the RPM. 

https://github.com/dabeaz/ply/issues/63
https://code.google.com/p/chromium/issues/detail?id=484119

Note that this seems to effect more than just the chromium builds, there is a reference to the slimit build being broken as well.

Comment 1 Fedora Update System 2015-08-18 11:42:52 UTC
python-ply-3.6-2.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/python-ply-3.6-2.fc23

Comment 2 Fedora Update System 2015-08-19 08:03:39 UTC
Package python-ply-3.6-2.fc23:
* should fix your issue,
* was pushed to the Fedora 23 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-ply-3.6-2.fc23'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-13668/python-ply-3.6-2.fc23
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2015-09-04 03:24:49 UTC
python-ply-3.6-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.