Package Details: python2-setuptools 2:44.1.1-2

Git Clone URL: https://aur.archlinux.org/python2-setuptools.git (read-only, click to copy)
Package Base: python2-setuptools
Description: Easily download, build, install, upgrade, and uninstall Python packages
Upstream URL: https://pypi.org/project/setuptools
Licenses: PSF
Provides: python2-distribute
Replaces: python2-distribute
Submitter: jelly
Maintainer: tallero (truocolo)
Last Packager: truocolo
Votes: 28
Popularity: 0.55
First Submitted: 2022-09-22 16:43 (UTC)
Last Updated: 2024-01-27 13:32 (UTC)

Dependencies (2)

Required by (506)

Sources (1)

Latest Comments

1 2 3 Next › Last »

LaughingMan commented on 2023-12-26 14:03 (UTC) (edited on 2023-12-26 14:04 (UTC) by LaughingMan)

Does that mean the build issue Calimero and me have been seeing is solved in your local tree? Because if not, I should probably dig deeper seeing as MarsSeed surprisingly can't reproduce.

Something in the call to distutils.core.setup(...) goes wrong. The parameters are the same in the good and in the bad case, but it matters if setuptools.egg-info/entry_points.txt exists or not.

If the folder is missing, python2 bootstrap.py creates a dummy entry_points.txt and distutils tries and fails to open PKG-INFO.

If the folder already exists, python2 bootstrap.py skips creating the dummy and everything goes smoothly.

If the dummy file is manually replaced with the fully populated one, it still fails in the same way.

Full build log: https://pastebin.com/M72Jzbu3

Edit: Oh, and no hurry from my side. Just want to have it building eventually.

tallero commented on 2023-12-26 11:38 (UTC) (edited on 2023-12-26 12:10 (UTC) by tallero)

Okay so I think I've figured out what's happened.

All my updates to python2- packages from September to November (and probably even earlier) have never been pushed and they currently sit on my local tree on locked machines. This is because I usually do not push until all the deps tree builds successfully so since it never finished to build locally I have like 30 commits on 30 packages sitting on there.

So, as far as I remember this is at least the third time I rewrite this upgrade, every time from a new device from which I had not pushed. You can verify I am signing commits from a plethora of new keys as of recently.

I am still subject to some let's say 'infrastructure' issues from which should finally be relieved before the end of the year.

I hope you will have some patience as operations resume normally.

I have an unfinished gitlab continuous file published on arch gitlab for aur packages I've been working on as a workaround for the 'infrastructure' issue, if you would like to take a look at that we could even have some nice binary packages.

You can see I'm out of arch gitlab since August or September. I have many months of work on new packages to merge and push.

MarsSeed commented on 2023-12-26 01:28 (UTC)

It's strange, I've been doing rebuilds of this package many-many times during the past few months and never experienced the error reported by @Calimero.

Nevertheless, a maintainer's duty is to try to respond to users when they report issues. Maybe ask for more details about the build tools and build environment used, and the posting of a copy of the full build log to somewhere like pastebin.

LaughingMan commented on 2023-12-26 01:13 (UTC) (edited on 2023-12-26 06:02 (UTC) by LaughingMan)

Hi, truocolo. Merry xmas to you, too.

My apologies, I didn't realize this package has an active maintainer and when I filed the request you strangely weren't listed at all (only tallero). The problem report and the fix are just below in Calimero's comment from October. (Thanks for debugging btw, Calimero.)

Could you please apply that? I'm maintaining packages depending on python2-setuptools, which currently don't build if you don't have a previous installation around. Making a fork would of course be possible, but kind of silly as it would still leave several hundred packages from other maintainers unbuildable for many people.

Now to try and figure out how to close a request...

truocolo commented on 2023-12-25 23:58 (UTC)

Thanks LaughingMan!

Merry xmas to you and to your family!

I'm so happy you filed your request today!

Do you know you can publish a working fork with the ,fix' somewhere else, without having to request write access to this repo?

Or that you can gain co-maintainership by sending work over time and building a web of trust? Of course you do!

The 'orphan' request!

It's so weird to see all these people thinking my children have been orphaned!

[PRQ#52465] Orphan Request for python2-setuptools – LaughingMan [1] filed an orphan request for python2-setuptools [2]:

Package doesn't build anymore. A fix has been posted in the comments, but not applied in over two months. I'd like to take over and make it build again.

[1] https://aur.archlinux.org/account/LaughingMan/ [2] https://aur.archlinux.org/pkgbase/python2-setuptools/

Calimero commented on 2023-10-09 12:35 (UTC)

The build fails for me with:

ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /tmp/aur-python2-setuptools/src/setuptools-44.1.1/setuptools.egg-info/PKG-INFO", setuptools [unknown version] (/tmp/aur-python2-setuptools/src/setuptools-44.1.1))

A solution is to add this to the end of prepare():

mkdir setuptools.egg-info

Please do!

gnaggnoyil commented on 2022-12-03 07:58 (UTC)

@eclairevoyant I'm sure I'm using python2. I've also tried building in a clean chroot and the result was the same.

eclairevoyant commented on 2022-11-30 11:07 (UTC)

This package builds fine. Make sure you're using python2, not python2-bin, and ensure you're building in a clean chroot.

superyu1337 commented on 2022-11-19 00:25 (UTC)

@jbbjarnason after a lot of fiddling around yesterday night, i got it to work by using PYTHONHOME=/usr

I also had pyenv setup previously, which I removed.

jbbjarnason commented on 2022-11-18 10:13 (UTC)

I am getting similar error as @ak2021 and @superyu1337. Both on my laptop and workstation (both running vanilla arch).

Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Traceback (most recent call last):
  File "bootstrap.py", line 13, in <module>
    import subprocess
  File "/usr/lib/python2.7/subprocess.py", line 72, in <module>
    import select
ImportError: No module named select
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python2-setuptools