Package Details: python2-urllib3 1.26.15-1

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: None
Last Packager: truocolo
Votes: 4
Popularity: 0.008754
First Submitted: 2022-06-12 22:15 (UTC)
Last Updated: 2024-02-02 16:26 (UTC)

Dependencies (14)

Sources (1)

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?

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

MarsSeed commented on 2022-07-02 08:06 (UTC)

Btw, just out of curiosity... What do you use python2-urllib3 for? I mean, which application?

You can check for yourself (or for me) with this command:

pactree -r python2-urllib3

MarsSeed commented on 2022-07-02 07:53 (UTC)

I've pushed 1.26.9-9, disabling 18 test cases for python2-pysocks. Please try the build again.

sng commented on 2022-07-02 07:27 (UTC)

No, I do not

MarsSeed commented on 2022-07-02 07:26 (UTC)

I think I will remove python2-pysocks from the checkdepends array. It seems to be unreliable. Between the test runs, it seems different subtests for it failed or froze each time.

Do you use a SOCKS proxy at all? (I guess that most people don't.)

sng commented on 2022-07-02 07:24 (UTC)

This is what I get

==> Extracting sources...
  -> Extracting urllib3-1.26.9.tar.gz with bsdtar
==> Starting prepare()...
Fixing hardcoded urllib3.connection.RECENT_DATE field - it's expired if earlier than two years
==> Sources are ready.
==> Making package: python2-urllib3 1.26.9-8 (Sat 02 Jul 2022 10:20:21 AM EEST)

The thing with the locale was only when LANG=en_US

sng commented on 2022-07-02 07:16 (UTC)

No nothing strange there...

$ sudo grep -v '^#' /etc/locale.gen 
el_GR.UTF-8 UTF-8
en_US.UTF-8 UTF-8

$ grep C.U /etc/locale.gen
#en_SC.UTF-8 UTF-8  
#es_EC.UTF-8 UTF-8

But just in case..

$ sudo locale-gen
Generating locales...
  el_GR.UTF-8... done
  en_US.UTF-8... done
Generation complete.

Still no joy...

MarsSeed commented on 2022-07-02 07:09 (UTC)

In the build logs of both Manjaro systems, is this present at the beginning of the build?

==> Extracting sources...
  -> Extracting urllib3-1.26.9.tar.gz with bsdtar
bsdtar: Failed to set default locale

MarsSeed commented on 2022-07-02 07:07 (UTC)

(On my Manjaro system, when I installed glibc 2.35-6, Manjaro's package install script has restored a bad locale.gen from an earlier .pacsave. So I had to edit my locale.gen and regenerate the locales. This install script was a custom Manjaro one, so they might have created errors that are not present on vanilla Arch.)

MarsSeed commented on 2022-07-02 07:02 (UTC)

Another idea, coming from this forum thread relating to locale:

Could you please check if there is an unmerged .pacnew, or a leftover .pacsave file for your /etc/locale.gen?

Would you verify which locales are enabled? (Enabled: lines not starting with #. Disabled: starting with #.)

If you find any discrepancies that don't match what locales you want on your system, please edit the locale.gen file to enable all the locales that you need.

Also please make sure there is no line starting with C.UTF-8 or #C.UTF-8. Because that is built into glibc since 2.35-6, built on 2022-06-06. Should not be generated on the installed system.

Then after editing and saving /etc/locale.gen, please run sudo locale-gen, and restart your system.

Maybe after all this, you can try the build again and hopefully see a better outcome. :)

sng commented on 2022-07-02 07:02 (UTC) (edited on 2022-07-02 07:03 (UTC) by sng)

IDK

Also tested it on a mabox linux box (based on manjaro stable, with openbox) and stil the same...

Updated python2-pysocks too, but no joy...

So, now we have two manjaro stable boxes and mabox box nok, but arch ok...

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »