[Bug 1413555] Re: init script fails with error code 0 when configuration test doesn't pass
Hello Thomas and thanks for taking an interest Personally, I experienced the bug using Ansible, which I would argue is well known. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1413555 Title: init script fails with error code 0 when configuration test doesn't pass To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413555] Re: init script fails with error code 0 when configuration test doesn't pass
Hello Thomas and thanks for taking an interest Personally, I experienced the bug using Ansible, which I would argue is well known. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413555 Title: init script fails with error code 0 when configuration test doesn't pass To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412545] Re: proxy isn't used after a dropped connection
The bug is fixed using the test script with version 1.7.1-1ubuntu0.1 0 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412545 Title: proxy isn't used after a dropped connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415028] Re: virtualenv's included pip does not use system libraries
I haven't looked into newer Ubuntu versions, so everything I'm posting is about Trusty. As far as I can tell, virtualenv's bundled pip wheel is not built by Debian maintainers, but by virtualenv's developers themselves. In fact, if you compare the wheel python-virtualenv installs in /usr/share /python-virtualenv/pip-1.5debian1-py2.py3-none-any.whl with the one in virtualenv's tree (https://github.com/pypa/virtualenv/raw/6dc9b1d376b041d83472c03c1ef334919a3b7c12/virtualenv_support/pip-1.5.4-py2.py3 -none-any.whl) their contents are identical. You can also tell that the bundled pip is not patched by comparing its contents with the contents of the python-pip package. The bundled pip has a _vendor directory and all imports reference it (eg from pip._vendor.requests import ***). The pip that is installed through apt is missing that directory and all imports have been patched to import system wide libraries (eg from pip import ***). The larger issue is whether the above behavior is correct. The pypa developers (maintainers of pip, virtualenv etc) prefer vendoring libraries, while Debian's python packagers prefer splitting packages and patch them accordingly. How this applies to virtualenv's bundled wheel which is installed as part of virtualenv's normal operation is not clear to me. I am not very familiar with Debian Python Policy, but I would argue that the contents of the bundled wheel should be patched as well, since: 1. The bundled pip's version is the same as the apt pip's version, so bugfixes on dependencies would equally apply to both. 2. Currently, the bundled pip is not the same as the pip apt installs, even though the are both the same version. Esesntialy, I think that the pip virtualenv installs should be the same as the one apt installs. If this can't be done at this point of the release, bugfixes would need to be applied to pip's vendored libraries (and their vendored libraries). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415028 Title: virtualenv's included pip does not use system libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1415028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415028] Re: virtualenv's included pip does not use system libraries
Maybe I'm missing something, but I don't see way any other package would need an SRU. The dependencies of the bundled pip are the same as the dependencies of apt's pip (since they're both the same version), so they are already available in apt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415028 Title: virtualenv's included pip does not use system libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1415028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415028] Re: virtualenv's included pip does not use system libraries
Ah ok, my bad. I thought you were talking about pip's dependencies on your previous comment. Thanks for looking into this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415028 Title: virtualenv's included pip does not use system libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1415028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412545] Re: proxy isn't used after a dropped connection
After doing some more digging, it seems that while the above is enough to fix pip, requests and urllib3 it will not fix virtualenv. Virtualenv comes with its own version of pip which it installs in every virtualenv, regardless of the OS version of pip. The included version of pip is in /usr/share/python-virtualenv/pip-1.5debian1-py2.py3-none- any.whl. If you look inside the wheel (it's a zip archive), you can see that it has not been patched to use the apt installed packages. Instead it uses its vendored requests, which in turns uses its vendored urllib3 which still exhibits this bug. Should I raise this in virtualenv's tracker? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412545 Title: proxy isn't used after a dropped connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415028] [NEW] virtualenv's included pip does not use system libraries
Public bug reported: Ubuntu version: Ubuntu 14.04.1 LTS python-virtualenv version: 1.11.4-1 Normally, pip vendors a few python libraries under a _vendor directory in its source tree. When packaged for Ubuntu, pip is patched to use system installed of these libraries. python-virtualenv installs its own version of pip (found in /usr/share /python-virtualenv/pip-1.5debian1-py2.py3-none-any.whl) in every virtualenv it creates. Unfortunately, this version of pip is not patched and does not use the system wide python libraries. There is an open issue affecting urllib3 (https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545) that makes pip fail under certain circumstances. Patching virtualenv's pip would make it get the fix when urllib3 is updated, instead of requiring a separate fix. ** Affects: python-virtualenv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415028 Title: virtualenv's included pip does not use system libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1415028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413555] [NEW] init script fails with error code 0 when configuration test doesn't pass
Public bug reported: Ubuntu version: Ubuntu 14.04.1 LTS Nginx version: 1.4.6-1ubuntu3.1 Steps to reproduce: 1. install nginx 2. add a configuration error to nginx's configuration (echo error /etc/nginx/nginx.conf) 3. reload nginx and check its exit code (/etc/init.d/nginx reload; echo $?) What should happen: Nginx should fail to reload with a non zero exit code. What happens instead Nginx does not reload, but the init script's exit code is 0. This confuses certain configuration management tools that rely on init scripts' exit codes to determine success. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1413555 Title: init script fails with error code 0 when configuration test doesn't pass To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413555] [NEW] init script fails with error code 0 when configuration test doesn't pass
Public bug reported: Ubuntu version: Ubuntu 14.04.1 LTS Nginx version: 1.4.6-1ubuntu3.1 Steps to reproduce: 1. install nginx 2. add a configuration error to nginx's configuration (echo error /etc/nginx/nginx.conf) 3. reload nginx and check its exit code (/etc/init.d/nginx reload; echo $?) What should happen: Nginx should fail to reload with a non zero exit code. What happens instead Nginx does not reload, but the init script's exit code is 0. This confuses certain configuration management tools that rely on init scripts' exit codes to determine success. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413555 Title: init script fails with error code 0 when configuration test doesn't pass To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412545] [NEW] proxy isn't used after a dropped connection
Public bug reported: Ubuntu version: Ubuntu 14.04.1 LTS python-urllib3 version: 1.7.1-1build1 Steps to reproduce: 1. set up an http proxy 2. configure a ProxyManager to use said http proxy 3. make successive GET requests to https://pypi.python.org/ example script: https://gist.github.com/stratoukos/7545c5c909fa9b5d1cfb What happens: urllib3 stops using the http proxy after the connection is dropped (after 24 requests in my testing with pypi. other people have seen different numbers) What I expected to happen: urllib3 should always use the proxy Other Info: This has been fixed in commit 1c30a1f3 of urllib3 and included in its 1.8.3 release. This bug also affects pip and requests as reported here: https://github.com/pypa/pip/issues/1805 I really hope the bugfix will be backported, since pip is currently unusable behind an outgoing firewall on 14.04 ** Affects: python-urllib3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-urllib3 in Ubuntu. https://bugs.launchpad.net/bugs/1412545 Title: proxy isn't used after a dropped connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1412545] [NEW] proxy isn't used after a dropped connection
Public bug reported: Ubuntu version: Ubuntu 14.04.1 LTS python-urllib3 version: 1.7.1-1build1 Steps to reproduce: 1. set up an http proxy 2. configure a ProxyManager to use said http proxy 3. make successive GET requests to https://pypi.python.org/ example script: https://gist.github.com/stratoukos/7545c5c909fa9b5d1cfb What happens: urllib3 stops using the http proxy after the connection is dropped (after 24 requests in my testing with pypi. other people have seen different numbers) What I expected to happen: urllib3 should always use the proxy Other Info: This has been fixed in commit 1c30a1f3 of urllib3 and included in its 1.8.3 release. This bug also affects pip and requests as reported here: https://github.com/pypa/pip/issues/1805 I really hope the bugfix will be backported, since pip is currently unusable behind an outgoing firewall on 14.04 ** Affects: python-urllib3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412545 Title: proxy isn't used after a dropped connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
