[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-22 Thread dino99
** Changed in: python2.7 (Ubuntu) Status: Confirmed => Invalid ** Changed in: python-pip (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu.

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

2015-12-21 Thread jose
This seems to have been solved. -- 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 ConfigParser Status in python-pip

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

2015-12-02 Thread Barry Warsaw
Why are you using toolchain-r? Are you sure that's where your getting your libpython2.7-minimal from for trusty? https://launchpad.net/~ubuntu- toolchain-r/+archive/ubuntu/test?field.series_filter=trusty This problem doesn't happen in a clean trusty chroot. -- You received this bug

[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] Re: libpython2.7 uses the 3.x name for ConfigParser

2015-12-01 Thread Rich Tong
It appears to break all pip search and pip install commands ** Changed in: python2.7 (Ubuntu) Status: Invalid => Confirmed ** Also affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Changed in: python-pip (Ubuntu) Status: New => Confirmed -- You received

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

2015-12-01 Thread Rich Tong
OK, the problem is that you cannot actually do a `pip install configparser` because pip itself uses ssl.py and this fails, so the only solution is to change the name. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7

[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,