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#35186 - [ponysay] PLEASE ENTER SUMMARY
Attached to Project:
Community Packages
Opened by Jack O'Connor (oconnor663) - Friday, 10 May 2013, 21:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 12 May 2013, 08:12 GMT
Opened by Jack O'Connor (oconnor663) - Friday, 10 May 2013, 21:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 12 May 2013, 08:12 GMT
|
DetailsDescription: /usr/bin/ponysay targets "python" instead of "python3", crashes if the user points "python" to Python 2.x
Steps to reproduce: - Relink "/usr/bin/python" to "/usr/bin/python2" - Install ponysay - Run it. It crashes on a print statement, because it's running under Python 2. For compatibility with a lot of code at work, I keep "python" pointing to Python 2 with a simlink in my ~/bin. To run ponysay, I have to explicitly call "python3 /usr/bin/ponysay", or else it crashes. The source seems to explicitly specify python3, and I if I run the PKGBUILD on my own box and install ponysay from that package, it runs fine. Could it be a build configuration issue with the community package that's causing it to point to "python" instead of "python3"? Thanks for your help. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Sunday, 12 May 2013, 08:12 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix. This is an upstream problem or elsewise a configuration problem on your own system. We obviously do not support relinking system packages like python.
Sunday, 12 May 2013, 08:12 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix. This is an upstream problem or elsewise a configuration problem on your own system. We obviously do not support relinking system packages like python.