After emerging app-mobilephone/bitpim-1.0.5, The program will not launch. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS=~amd64 USE=usb emerge -av bitpim 2. ~ $ bitpim 3. Actual Results: /usr/lib64/python2.5/site-packages/wx-2.8-gtk2-unicode/wx/_core.py:14240: UserWarning: wxPython/wxWidgets release number mismatch warnings.warn("wxPython/wxWidgets release number mismatch") Traceback (most recent call last): File "/usr/lib64/bitpim-1.0.5/bp.py", line 20, in <module> import bp_cli File "/usr/lib64/bitpim-1.0.5/bp_cli.py", line 22, in <module> import phones.com_brew as com_brew File "/usr/lib64/bitpim-1.0.5/phones/com_brew.py", line 16, in <module> import com_phone File "/usr/lib64/bitpim-1.0.5/phones/com_phone.py", line 15, in <module> import commport File "/usr/lib64/bitpim-1.0.5/commport.py", line 12, in <module> import serial ImportError: No module named serial Expected Results: bitpim should load. After the emerge python gave this message which might be related. * Messages for package dev-lang/python-2.5.2-r5: * * If you have just upgraded from an older version of python you will * need to run: * * /usr/sbin/python-updater * * This will automatically rebuild all the python dependent modules * to run with python-2.5. * * Your original Python is still installed and can be accessed via * /usr/bin/python2.x. * /usr/sbin/python-updater: No such file or directory
python-updater is part of app-admin/python-updater and unless you used the _unsafe_ --nodeps option, when building Python, you should have it installed. Please run python-updater and confirm if the problem persists or not.
(In reply to comment #1) > python-updater is part of app-admin/python-updater and unless you used the > _unsafe_ --nodeps option, when building Python, you should have it installed. > > Please run python-updater and confirm if the problem persists or not. > Yup, that was certainly it. The strange thing however... although I could not find python-updater (the executable) anywhere on my computer, and certainly not in /usr/sbin/, portage indeed said it was installed. Anyway, a simple remerge and run of python-updater fixed the issue.
*** Bug 232321 has been marked as a duplicate of this bug. ***
