Summary: | dev-python/pycparser-2.11: TypeError: cannot create weak reference to 'Struct' object | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Antoine Lemoine <mail> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | bugs.gentoo.org.list, dolsen, josef64, pageexec, zorry |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Antoine Lemoine
2015-05-05 20:47:01 UTC
The error is knows and appears after the installation of pycparser-2.11. According to https://bugs.launchpad.net/openstack-gate/+bug/1446882 the solution is to downgrade pycparser to 2.10 version. Maybe this is not the right place to ask a question, but it may help people in the same situation: How can I downgrade a package without emerge, ebuild or a similar tool? as a quick fix just manually edit /usr/lib64/python2.7/site-packages/pycparser/c_ast.py to look like this (line numbers shown just for context): 22 class Node(object): 23 __slots__ = ('__weakref__',) 24 """ Abstract base class for AST nodes. this is basically commit https://github.com/markrwilliams/pycparser/commit/5298fd85018735462bdc037b47a62ce0fc5164d7 applied by hand. It sounds like you have app-portage/layman[sync-plugin-portage] installed, and that is breaking portage installation due to this issue. Thanks for the report, and sorry for the breakage. You may also be able to work around this by running emerge using python3. +*pycparser-2.12 (06 May 2015) + + 06 May 2015; Mike Gilbert <floppym@gentoo.org> +pycparser-2.12.ebuild, + -pycparser-2.11.ebuild: + Version bump, should fix bug 548718. I had a pycparser-2.10.tbz2 lying around (long live binary packages) and just extracted that over /. I had to do something, you have no idea how broken my system was :/ I've reworked the laymansync plugin so that this type of problem would only affect an actual sync, not any other emerge operation. Also, this problem is only affecting py2.7. Layman running in py-3.3, 3.4 do not make use of this pkg. *** Bug 549410 has been marked as a duplicate of this bug. *** |