Arch Linux

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!
Tasklist

FS#21309 - pygtk apps do not start after upgrading to python3

Attached to Project: Arch Linux
Opened by Doug Penner (DarwinSurvivor) - Monday, 18 October 2010, 23:05 GMT
Last edited by Allan McRae (Allan) - Tuesday, 19 October 2010, 00:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
pygtk apps do not start after upgrading to python3


Additional info:
* package version(s)
pygtk 2.22.0-3
* config and/or log files etc.
bash: /usr/bin/sonata: /usr/bin/python2: bad interpreter: No such file or directory
bash: /usr/bin/terminator: /usr/bin/python2: bad interpreter: No such file or directory
bash: /usr/bin/ccsm: /usr/bin/python2: bad interpreter: No such file or directory

rhythmbox and gimp both run, but with references to the above error in their output.


Steps to reproduce:
1) upgrade to python3
2) start sonata, terminator, ccsm or almost any other pygtk app.

Have not confirmed on i686, but sure it would do the same.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 19 October 2010, 00:35 GMT
Reason for closing:  Not a bug
Comment by Ionut Biru (wonder) - Monday, 18 October 2010, 23:14 GMT
pacman -Q terminator sonata ccsm
Comment by Ionut Biru (wonder) - Monday, 18 October 2010, 23:15 GMT
is it me or you don't have python2 installed?
Comment by Dan McGee (toofishes) - Tuesday, 19 October 2010, 00:01 GMT
If your steps to reproduce does not include `pacman -Syu`, this bug is bogus.
Comment by Doug Penner (DarwinSurvivor) - Tuesday, 19 October 2010, 00:25 GMT
Sorry, I forgot to add "pacman -Syu" to my steps to reproduce, but I did do that when upgrading.
python2 IS installed but looking in /usr/bin/ I found "python2.7" but not "python2" (pacman -Ql listed python2.7 but not python2 in /usr/bin as well).
I reinstalled python2 (sudo pacman -S python2 --asdeps) and /usr/bin/python2 appeared and everything started working again.

I find it strange that reinstalling python2 added another executable but python2's version number didn't increase (so pacman didn't update it automatically). Should I open a bug for the python2 package requesting a version number increase?
Comment by Allan McRae (Allan) - Tuesday, 19 October 2010, 00:28 GMT
The python package has had the python2 symlink for years... not sure what went on for you not to have it.
Comment by Doug Penner (DarwinSurvivor) - Tuesday, 19 October 2010, 00:33 GMT
I've created a python2 bug report just in case I wasn't the only one to have this strange problem.
https://bugs.archlinux.org/task/21310

If nobody else has had this problem, then I guess I screwed something up, if it's happened to others, then something strange must have happened in the repos or something.

Loading...