Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12518 - [boost] pyste is missing a dependency
Attached to Project:
Arch Linux
Opened by Dmitriy M (foxcub) - Saturday, 20 December 2008, 18:40 GMT
Last edited by Roman Kyrylych (Romashka) - Friday, 07 August 2009, 08:42 GMT
Opened by Dmitriy M (foxcub) - Saturday, 20 December 2008, 18:40 GMT
Last edited by Roman Kyrylych (Romashka) - Friday, 07 August 2009, 08:42 GMT
|
DetailsIf you run pyste.py (which is part of boost) it crashes because its GCCXMLParser uses external ElementTree rater than the one built into Python. The problem exists both in Boost 1.36.0 (currently in ArchLinux), and in 1.37.0 (most recently released version of boost). Currently, the easiest way to fix this is to install python-elementtree from AUR. So either this needs to be a dependency of boost (and I guess moved to community), or boost's PKGBUILD could apply a patch similar to the one in Ubuntu that switches pyste to use the ElementTree built into Python.
http://merges.ubuntu.com/b/boost/boost_1.34.1-14ubuntu2.patch |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Friday, 07 August 2009, 08:42 GMT
Reason for closing: Fixed
Additional comments about closing: Probably made obsolete by update patches; should at least be reviewed. Lack of recent chatter on this (cross os, as seen by Google) implies it is likely resolved.
Friday, 07 August 2009, 08:42 GMT
Reason for closing: Fixed
Additional comments about closing: Probably made obsolete by update patches; should at least be reviewed. Lack of recent chatter on this (cross os, as seen by Google) implies it is likely resolved.