Summary: | sys-apps/elfix-0.9.5 should use python-single-r1.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | atoth, hardened, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 803152 |
Description
Anton Bolshakov
2020-02-08 03:25:20 UTC
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=71b0725e2b295f383bdbe98571545aaf705c5a03 commit 71b0725e2b295f383bdbe98571545aaf705c5a03 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-02-08 20:23:27 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-02-08 21:34:20 +0000 dev-qt/qtwebengine: pax_kernel is dead Closes: https://bugs.gentoo.org/708676 Package-Manager: Portage-2.3.87, Repoman-2.3.20 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> .../qtwebengine-5.11.2-paxmark-mksnapshot.patch | 41 ---------------------- dev-qt/qtwebengine/metadata.xml | 1 - dev-qt/qtwebengine/qtwebengine-5.12.3.ebuild | 11 ++---- dev-qt/qtwebengine/qtwebengine-5.13.2.ebuild | 11 ++---- dev-qt/qtwebengine/qtwebengine-5.14.1.ebuild | 11 ++---- 5 files changed, 9 insertions(+), 66 deletions(-) Real problem is actually in sys-apps/elfix. sys-apps/elfix needs to use python-single-r1.eclass properly. sys-apps/elfix installs: /usr/sbin/migrate-pax /usr/sbin/pypaxctl /usr/sbin/revdep-pax These 3 files are Python scripts which import pax module. Shebangs in these scripts need to be updated (using eclass functionality) from '#!/usr/bin/env python' to use Python interpreter selected using PYTHON_SINGLE_TARGET. ~dev-python/pypax-${PV}[ptpax=,xtpax=] dependency should be: $(python_gen_cond_dep '~dev-python/pypax-${PV}[ptpax=,xtpax=,${PYTHON_MULTI_USEDEP}]') (In reply to Arfrever Frehtes Taifersar Arahesis from comment #2) > /usr/sbin/migrate-pax > /usr/sbin/pypaxctl > /usr/sbin/revdep-pax > These 3 files are Python scripts which import pax module. > Shebangs in these scripts need to be updated (using eclass functionality) > from '#!/usr/bin/env python' to use Python interpreter selected using > PYTHON_SINGLE_TARGET. Arfrever, what needs to change? Should I just change the shebang to '#!/usr/bin/python' ? (In reply to Anthony Basile from comment #3) > (In reply to Arfrever Frehtes Taifersar Arahesis from comment #2) > > > /usr/sbin/migrate-pax > > /usr/sbin/pypaxctl > > /usr/sbin/revdep-pax > > These 3 files are Python scripts which import pax module. > > Shebangs in these scripts need to be updated (using eclass functionality) > > from '#!/usr/bin/env python' to use Python interpreter selected using > > PYTHON_SINGLE_TARGET. > > Arfrever, what needs to change? Should I just change the shebang to > '#!/usr/bin/python' ? Use python_fix_shebang function. Changes are needed in sys-apps/elfix, not dev-python/pypax. (In reply to Arfrever Frehtes Taifersar Arahesis from comment #5) > Changes are needed in sys-apps/elfix, not dev-python/pypax. Are there anything I may help to solve this issue I also ran into? Thx: Dw. (In reply to Anthony Basile from comment #3) > (In reply to Arfrever Frehtes Taifersar Arahesis from comment #2) > > > /usr/sbin/migrate-pax > > /usr/sbin/pypaxctl > > /usr/sbin/revdep-pax > > These 3 files are Python scripts which import pax module. > > Shebangs in these scripts need to be updated (using eclass functionality) > > from '#!/usr/bin/env python' to use Python interpreter selected using > > PYTHON_SINGLE_TARGET. > > Arfrever, what needs to change? Should I just change the shebang to > '#!/usr/bin/python' ? OK, listen to this one, gentelmen! A couple of days ago, python2 support has been removed from pypax: 2020-02-05 20:53:19 +0100 dev-python/pypax: Remove py2 Signed-off-by: Michał Górny <mgorny@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-python/pypax?id=f700592b09cd09657f5ecaa2db0ffd0d23848772 The root of the problem in my opinion is, that qtwebengine and many other builds often still use python2, often their own compile-time internal instance (thunderbird, firefox for eg.). No matter what shebang I sat the script misses the pax module and that's because it is looking for the python2 egg, IMHO. After reintroducing 2_7 python compatibility to pypax, the compilation goes on flawlessly! Additionally - to my disappointment - pax_kernel has been announced to be dead: 020-02-08 21:23:27 +0100 dev-qt/qtwebengine: pax_kernel is dead Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-qt/qtwebengine?id=71b0725e2b295f383bdbe98571545aaf705c5a03 I have a zombie in my hands, so I have to maintain another personal ebuild, because it needs those markings. Blueness: I'm happy to share, if you are interested. BR: Dwokfur Since sys-apps/elfix does not use any Python eclass, it is unknown which Python versions it supports. If sys-apps/elfix does not yet support Python 3, then, in addition to starting to use proper eclass, sys-apps/elfix needs to be ported to Python 3 quickly, or sys-apps/elfix will be removed from the tree. looks like this hits migrate-pax on new tarballs as well (In reply to Arfrever Frehtes Taifersar Arahesis from comment #8) > Since sys-apps/elfix does not use any Python eclass, it is unknown which > Python versions it supports. > If sys-apps/elfix does not yet support Python 3, then, in addition to > starting to use proper eclass, sys-apps/elfix needs to be ported to Python 3 > quickly, or sys-apps/elfix will be removed from the tree. Taking a look at on the source code, it considers both Python 2 and 3. Ping: blueness |