| Summary: | dev-python/gntp-1.0.1 fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | Current packages | Assignee: | Naohiro Aota <naota> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | bkohler, davydm, jstein, mgorny, treecleaner |
| Priority: | Normal | Keywords: | PMASKED |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Deadline: | 2020-09-05 | ||
| Attachments: |
build.log
emerge --info |
||
|
Description
Patrick Lauer
2014-06-30 02:52:48 UTC
dev-python/gntp $ ebuild gntp-1.0.1.ebuild clean compile
>>> Source compiled.
No idea how this came about.
the file scripts/gntp is not in the pypi tarball. It is however on github. If you have setuptools installed, you do not need scripts/gntp. If you don't have it installed, setup.py loads this file instead. So it seems like it comes down to three choices: 1. Depend on dev-python/setuptools 2. include scripts/gntp as an extra file (It's only three lines) 3. Download the source from github instead of pypi. Created attachment 508420 [details]
build.log
Created attachment 508422 [details]
emerge --info
This has reared again )': If I can furnish any more info, please ping me. *** Bug 640112 has been marked as a duplicate of this bug. *** Can you confirm that installing setuptools ahead of time makes it succeed? I have dev-python/setuptools installed:
emerge --search setuptools includes in the output:
* dev-python/setuptools
Latest version available: 34.0.2-r1
Latest version installed: 34.0.2-r1
Size of files: 604 KiB
Homepage: https://github.com/pypa/setuptools https://pypi.python.org/pypi/setuptools
Description: Collection of extensions to Distutils
License: MIT
So I think that's a "no"? I have had dev-python/setuptools installed since before gntp was updated from 1.0.0 -> 1.0.1, but this only fails now.
Perhaps there's something wrong with my setuptools / environment? If so, please let me know how I can furnish more information. Apologies -- linux user (Debian) for around 18 years -- but only the last year on Gentoo, so likely I've missed something.
Can you check "emerge -pvO setuptools" output and see if setuptools has been built for python3_5 yet? output from "emerge -pvO setuptools":
[ebuild R ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 0 KiB
So, to me, that *looks like* setuptools is built against python3_5; however, following your hunch, I simply rebuilt setuptools (vanilla old "emerge dev-python/gntp") after unmasking 1.0.1 again and it's built fine now -- no issues.
Not sure how this gets automagically fixed for others, but thanks for looking into it and giving me a direction to head in (:
btw, I regularly: emerge --sync && emerge --update --newuse --deep @world @preserved-rebuild @module-rebuild which I understand takes care of USE flag changes -- is there something I should add in there to deal with other flag changes (like PYTHON_TARGETS)? It looks (to me) like I originally had python2.x installed with setuptools and, some time later, got python3.5, without setuptools being rebuilt for that target -- or should the install of python3.5 have caused setuptools to be rebuilt anyway? Just trying to get a better understanding of the system. Ok just wanted to make sure you didnt have a pending setuptools change, which wouldn't be enforced since there is no dependency. It would seem that option #1 from comment #2 isn't working, so we'll need to dig deeper. I'm quite happy to assist in debugging this, if I can be of any assistance. Just shout (: I may not have the first clue about how an ebuild works, but I can follow instructions. Just for interest' sake, this has happened again. Thanks to https://forums.gentoo.org/viewtopic-t-1075062.html, I could "windows-fix" gntp: unmerge and then remerge, to get back to a working state. Once again, I offer my assistance (for what it's worth) in debugging this so it doesn't happen again. I'm no ebuild genius, but I can follow instructions. Removing. |