Arch Linux User Repository

Am I the only person thinking a package submitter (cough cough) saying 'I have an update, give me ownership to receive it' to its current, active maintainer instead of simply posting/sending it is kinda hostile?

@politas, thank you for reporting this. Unfortunately I am unable to reproduce the error and the quoted log output does not provide sufficient information for me to even begin to think about where the problem can arise.

Still failing to build here, too.

IndexError: list index out of range
==> ERROR: A failure occurred in check().
    Aborting...

This package is still failing for me (w/ 8 tests failed!).

I'm running in vmware. I ended up building w/ --nocheck, so it's not super urgent for me. Details follow

ffrey in ~/Downloads/AUR/python2-urllib3/python2-urllib3 λ makepkg -sf | grep 'FAILED'
    urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382.tar.gz ... Passed
warning: no files found matching 'Makefile'
warning: no previously-included files matching '*' found under directory 'docs/_build'
No handlers could be found for logger "tornado.application"
Exception in thread Thread-37:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 134, in run
    self.server = self._start_server()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 130, in _start_server
    self.socket_handler(sock)
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/test/with_dummyserver/test_socketlevel.py", line 1202, in socket_handler
    ca_certs=DEFAULT_CA,
  File "/usr/lib/python2.7/ssl.py", line 931, in wrap_socket
    ciphers=ciphers)
  File "/usr/lib/python2.7/ssl.py", line 599, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 828, in do_handshake
    self._sslobj.do_handshake()
SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:727)

test/contrib/test_pyopenssl.py::TestSSL::test_ssl_read_timeout FAILED    [ 49%]
Exception in thread Thread-45:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 134, in run
    self.server = self._start_server()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 130, in _start_server
    self.socket_handler(sock)
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/test/with_dummyserver/test_socketlevel.py", line 1415, in socket_handler
    ca_certs=DEFAULT_CA,
  File "/usr/lib/python2.7/ssl.py", line 931, in wrap_socket
    ciphers=ciphers)
  File "/usr/lib/python2.7/ssl.py", line 599, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 828, in do_handshake
    self._sslobj.do_handshake()
error: [Errno 0] Error

test/with_dummyserver/test_connectionpool.py::TestConnectionPoolTimeouts::test_connect_timeout FAILED [ 62%]
test/with_dummyserver/test_connectionpool.py::TestConnectionPoolTimeouts::test_total_applies_connect FAILED [ 63%]
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test_forwarding_proxy_connect_timeout[http-http-False] FAILED [ 95%]
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test_forwarding_proxy_connect_timeout[https-http-False] FAILED [ 95%]
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test_tunneling_proxy_connect_timeout[http-https] FAILED [ 96%]
Exception in thread Thread-123:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 134, in run
    self.server = self._start_server()
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/dummyserver/server.py", line 130, in _start_server
    self.socket_handler(sock)
  File "/home/ffrey/Downloads/AUR/python2-urllib3/python2-urllib3/src/urllib3-37ba00248424ea3cdf556cc3e7aa81ce0bf40382/test/with_dummyserver/test_socketlevel.py", line 1202, in socket_handler
    ca_certs=DEFAULT_CA,
  File "/usr/lib/python2.7/ssl.py", line 931, in wrap_socket
    ciphers=ciphers)
  File "/usr/lib/python2.7/ssl.py", line 599, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 828, in do_handshake
    self._sslobj.do_handshake()
SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:727)

test/with_dummyserver/test_socketlevel.py::TestSSL::test_ssl_read_timeout FAILED [ 98%]
==> ERROR: A failure occurred in check().
    Aborting...
...
===End Flaky Test Report===
================== 8 failed, 1605 passed, 283 skipped, 56 deselected, 148 warnings in 44.79 seconds ==================
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: python2-urllib3

System details:

Linux Boa 4.19.248-1-MANJARO #1 SMP Thu Jun 16 12:35:56 UTC 2022 x86_64 GNU/Linux

makepkg (pacman) 6.0.1
Copyright (c) 2006-2021 Pacman Development Team <pacman-dev@archlinux.org>.
Copyright (C) 2002-2006 Judd Vinet <jvinet@zeroflux.org>.

This is free software; see the source for copying conditions.
There is NO WARRANTY, to the extent permitted by law.

Something I don't understand is why this freezegun package is being pulled in as a dependency now, when it wasn't one previously? I had a successful build a few days ago, but now this new freezegun checkdepends is failing.

XDD

Yes!

Yes, now it does build and install!

That is so great!

Thank you very much!

Pushed pkgrel=3. Disabled that one stubborn test. You are welcome to try again if you don't yet want to run away screaming. XDD

No, no joy...

Still produces an error...

Pushed the latest 1.26.x git branch version (unreleased tag). They have committed a small fix for IPv6. If you have the patience still, I'd be interested in any change in that last error with TestHTTPSProxyVerification::test_https_proxy_ipv6_san. :)

Yes, I see what you mean...

I still support it for my project but I find it hard to keep up...

The idea is to support it for as long as debian uses python2 as default (I think they still do).

Yes, they do, last stable release though: https://wiki.debian.org/Python/FAQ#Python_2_support

BTW, python2-requests works great, both from pip and from my project (contacting radio browser servers)...

So, the --nocheck is a godsent flag for me right now!

Btw now I am starting to understand why the overall majority of the projects dropped Python 2 support.

Even those that previously vowed to keep their code dual-compatible finally gave in. The reasons tended to be related to CI / cloud testing problems. I.e., executing the test suites even on standardized cloud instances of an Ubuntu LTS release started to produce more and more weird errors for the devs, so they felt they have to take the bitter pill and pull the plug on Py2. Pip/Tox/Pytest/Requests etc. all stopped testing and maintaining their code and fixing bugs for that legacy version of Python.

And I am not even a Python developer, I've learnt Java programming and have expertise in DevOps automation, but I don't have enough knowledge to devise a plan to fix your Manjaro machines' Python2 urllib3 testing issues. :/