| Git Clone URL: | https://aur.archlinux.org/python2-urllib3.git (read-only, click to copy) |
|---|---|
| Package Base: | python2-urllib3 |
| Description: | HTTP library with thread-safe connection pooling and file post support |
| Upstream URL: | https://pypi.org/project/urllib3/1.26.15 |
| Licenses: | MIT |
| Submitter: | MarsSeed |
| Maintainer: | tallero (truocolo) |
| Last Packager: | truocolo |
| Votes: | 4 |
| Popularity: | 0.016123 |
| First Submitted: | 2022-06-12 22:15 (UTC) |
| Last Updated: | 2024-02-02 16:26 (UTC) |
EDIT Just tested it on arch, all ok.
Hm, that is strange... I don't have a clue why would a Manjaro stable have issues vs the current Arch. Because most of the packages involved are from AUR, which are the same source for both systems.
Meanwhile I've pushed an update to python2-pysocks, which is deprecated and has a few unreleased patches on GitHub (I've added three of them).
It seems that the PySocks module has the freezing issue on your Manjaro.
Yes, I know the feeling... don't worry about it!
I am now at a different system, stil manjaro stable...
Here is the log
Just tested it on arch, all ok...
Sorry, I've screwed up pytest-freezegun 0.4.1 checksum.
But I've now pushed the latest version of that, 0.4.2.
(Versions after 3.0 don't officially support Python 2, so I've sifted through every change commit and tested locally every new version bump. That's when I forgot to update the checksum, between 0.4.0 and 0.4.1.)
pytest-freezegun output..
==> Validating source files with b2sums...
pytest-freezegun-0.4.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
100 260k 0 260k 0 0 259k 0 --:--:-- 0:00:01 --:--:-- 1134k
==> Validating source files with b2sums...
urllib3-1.26.9.tar.gz ... Passed
-> error downloading sources: python2-pytest-freezegun
context: error downloading sources: python2-pytest-freezegun
context: exit status 1
I gotta go run some errands...
I'll check it out in 30-45 min...
I've been waiting on this one for more than 5 minutes... at 61%...
test/contrib/test_socks.py::TestSocks5Proxy::test_proxy_rejection
Both with and without using LANG=en_US.utf8 gives the same result
ok, these are the commands... still waiting for the tests to complete...
$ LC_ALL=en_US python2 -c 'import sys; print("default: " + sys.getdefaultencoding()); print("filesystem: " + sys.getfilesystemencoding())'
default: ascii
filesystem: ANSI_X3.4-1968
$ LC_ALL=C python2 -c 'import sys; print("default: " + sys.getdefaultencoding()); print("filesystem: " + sys.getfilesystemencoding())'
default: ascii
filesystem: ANSI_X3.4-1968
In that latest update, I've added a needed test addon (python2-pytest-freezegun), and also made the test output more verbose, which might help in tracking down where exactly your testing execution gets frozen.
Also, I would like to know roughly how long do you wait before hitting Ctrl+C. :) For me, one test hangs for 30-60 seconds and then succeeds.
Also I've pushed the new 1.26.9-6 version. So I'd really appreciate if you tried the build again. :)
(And using one of the existing English locales on your system, i.e. either C.UTF-8 or en_US.utf8.)
And in the interim: a recommendation.
When you want to produce non-Greek output for a build, please choose one of the locales that are present in the output of locale --all-locales (locale -a for short).
So in case of the system that generated the outputs in your last comment, I recommend you either use C.UTF-8 or en_US.utf8. These exist as generated locales on your system. Whereas en_US per se does not. So using the latter might lead to strange and hard-to-track errors during a build.
Thanks, I'll look into all the things you've sent. :)
Meanwhile just another small request: please also share the output of the following command:
LC_ALL=en_US python2 -c 'import sys; print("default: " + sys.getdefaultencoding()); print("filesystem: " + sys.getfilesystemencoding())'
LC_ALL=C python2 -c 'import sys; print("default: " + sys.getdefaultencoding()); print("filesystem: " + sys.getfilesystemencoding())'
Pinned Comments
tallero commented on 2024-01-29 07:04 (UTC) (edited on 2024-01-29 07:05 (UTC) by tallero)
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?