[Touch-packages] [Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser

2015-12-22 Thread Andy Caldwell
Agreed, latest packages on toolchain-r are working correctly. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1513565 Title: libpython2.7 uses the 3.x name for

[Touch-packages] [Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser

2015-12-02 Thread Andy Caldwell
See my first comment, this is specific to the toolchain-r version of libpython-minimal (the issue was introduced in https://launchpadlibrarian.net/221233027/python2.7_2.7.10-3~14.04_2.7.10-4~14.04.diff.gz). A clean trusty is not affected. Is there a way to raise bugs against a PPA? If so I

[Touch-packages] [Bug 1513565] [NEW] libpython2.7 uses the 3.x name for ConfigParser

2015-11-05 Thread Andy Caldwell
Public bug reported: Installing a minimal virtualenv on Trusty Tahr (using libpython-minimal 2.7.10-4~14.04), I ran into crashes because: File "/usr/lib/python2.7/ssl.py", line 491, in inner import configparser ImportError: No module named configparser Looking at the code in

[Touch-packages] [Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser

2015-11-05 Thread Andy Caldwell
I've noticed that I'm using libpython2.7-minimal from the ubuntu- toolchain-r PPA so I'm re-raising this issue in that PPA instead. ** Changed in: python2.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,