Summary: | app-admin/python-updater-0.14 - make: ./python-updater: Command not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | mgorny, prefix |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 615252 | ||
Attachments: | python-updater.diff |
Description
Martin Mokrejš
2016-07-29 15:21:55 UTC
What version of dev-util/make? sys-devel/make-4.2.1 I just happened on another amd64 STABLE host with sys-devel/make-3.82-r4. BTW, the 0.14 installation is really broken (on two install host for me): # emerge -pv python-updater Calculating dependencies... done! [ebuild R ] app-admin/python-updater-0.14::gentoo 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB On one host I get: # emerge -pv bash [ebuild U ] app-shells/bash-4.3_p48-r1::gentoo [4.2_p45::gentoo] USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins (-vanilla%)" 8008 KiB while on the other: [ebuild R ] app-shells/bash-4.3_p48-r1::gentoo USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins" 0 KiB # emerge -pv portage [ebuild U ] sys-apps/portage-2.3.3::gentoo [2.2.26::gentoo] USE="(ipc) native-extensions%* xattr -build -doc -epydoc (-selinux)" LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-python3_5) (-python3_6) (-python3_3%)" 900 KiB and on the other: [ebuild R ] sys-apps/portage-2.3.3::gentoo USE="(ipc) native-extensions xattr -build -doc -epydoc (-selinux)" LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-python3_5) (-python3_6)" 0 KiB And I have this issue also on ~amd64: # python-updater Traceback (most recent call last): File "<string>", line 25, in <module> KeyError: 'python' * Starting Python Updater... * Main active version of Python: 2.7 * Active version of Python 2: 2.7 * Active version of Python 3: 3.5 * Globally supported Python ABIs in installed repositories: ^C # emerge -pv app-shells/bash sys-devel/make python-updater sys-apps/portage These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-shells/bash-4.4_p12::gentoo USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins" 0 KiB [ebuild R ] sys-devel/make-4.2.1::gentoo USE="nls -guile -static" 0 KiB [ebuild R ] sys-apps/portage-2.3.5::gentoo USE="(ipc) native-extensions xattr -build -doc -epydoc (-selinux)" LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_5 -pypy -python3_4 -python3_6" 0 KiB [ebuild R ] app-admin/python-updater-0.14::gentoo 0 KiB Total: 4 packages (4 reinstalls), Size of downloads: 0 KiB # Created attachment 469684 [details]
python-updater.diff
I think the EPREFIX-related replacements do not work. See the misplaced double-quotes.
I think we can really lastrite it now. (In reply to Michał Górny from comment #8) > I think we can really lastrite it now. Please no. I don't have a single installation where python is properly installed. See bug #615158, #615252 (python-updater-0.11). There is a bunch of portage blocks for python-exec versions and there is at the moment not a single tool to check and repair whatever went wrong. Fixing pthon-updater should be simple, probably replacing first sed -e 's#"@GENTOO_PORTAGE_EPREFIX@"##' sed -e "s#'@GENTOO_PORTAGE_EPREFIX@'##" and only then sed -e 's#@GENTOO_PORTAGE_EPREFIX@##' But I do not know where. In some eclass probably. ;( The double quotes aren't a problem actually, they just expand to the empty string. It's this bit from the Makefile: VERSION=$(shell ./python-updater -V) which obviously fails if make is run before python-updater is created... In any case, I don't think it's worth any effort to fix it. It's not used in any of the make rules relevant to the ebuild. (In reply to Martin Mokrejš from comment #9) > (In reply to Michał Górny from comment #8) > > I think we can really lastrite it now. > > Please no. I don't have a single installation where python is properly > installed. See bug #615158, #615252 (python-updater-0.11). There is a bunch > of portage blocks for python-exec versions and there is at the moment not a > single tool to check and repair whatever went wrong. Fixing pthon-updater > should be simple, probably replacing first I doubt python-updater will do anything useful but if you believe so... just let me know if it actually did anything useful, so we don't keep it forever just to have people shoot themselves in the feet by using it too much. removed from the tree |