| View previous topic :: View next topic |
| Author |
Message |
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
 Posted: Sat Jun 19, 2021 5:43 pm Post subject: Trying to clean old python but EAPI is too old |
 |
|
Hello,
Trying to update my main system, I got lot of dependancies that are needing Python 3.9 as single target.
So I thought it was time to remove python2_7 python3_6 python3_7.
I kept only 3.8 and 3.9
But now, I'm failing to with lot of Unsupported EAPI=? (too old) for python-any-r1
The full output is :
| Code: | Calculating dependencies | * ERROR: sys-process/runit-2.1.2-r2::bar failed (depend phase):
* flag-o-matic.eclass: EAPI 3 is too old.
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/sys-process/runit/runit-2.1.2-r2.ebuild'
* runit-2.1.2-r2.ebuild, line 19: Called inherit 'eutils' 'toolchain-funcs' 'flag-o-matic'
* ebuild.sh, line 314: Called __qa_source '/usr/portage/eclass/flag-o-matic.eclass'
* ebuild.sh, line 112: Called source '/usr/portage/eclass/flag-o-matic.eclass'
* flag-o-matic.eclass, line 14: Called die
* The specific snippet of code:
* 0|1|2|3|4) die "flag-o-matic.eclass: EAPI ${EAPI} is too old." ;;
*
* If you need support, post the output of `emerge --info '=sys-process/runit-2.1.2-r2::bar'`,
* the complete build log and the output of `emerge -pqv '=sys-process/runit-2.1.2-r2::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/sys-process/runit-2.1.2-r2/work/runit-2.1.2'
\ * ERROR: dev-libs/sord-0.16.0::bar failed (depend phase):
* Unsupported EAPI=5 (too old) for python-any-r1
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/dev-libs/sord/sord-0.16.0.ebuild'
* sord-0.16.0.ebuild, line 21: Called inherit 'python-any-r1' 'waf-utils' 'multilib-minimal'
* ebuild.sh, line 314: Called __qa_source '/usr/portage/eclass/python-any-r1.eclass'
* ebuild.sh, line 112: Called source '/usr/portage/eclass/python-any-r1.eclass'
* python-any-r1.eclass, line 41: Called die
* The specific snippet of code:
* [0-5]) die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}" ;;
*
* If you need support, post the output of `emerge --info '=dev-libs/sord-0.16.0::bar'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/sord-0.16.0::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/dev-libs/sord-0.16.0/work/sord-0.16.0'
| * ERROR: dev-libs/sord-0.14.0::bar failed (depend phase):
* Unsupported EAPI=5 (too old) for python-any-r1
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/dev-libs/sord/sord-0.14.0.ebuild'
* sord-0.14.0.ebuild, line 21: Called inherit 'python-any-r1' 'waf-utils' 'multilib-minimal'
* ebuild.sh, line 314: Called __qa_source '/usr/portage/eclass/python-any-r1.eclass'
/ * ebuild.sh, line 112: Called source '/usr/portage/eclass/python-any-r1.eclass'
* python-any-r1.eclass, line 41: Called die
* The specific snippet of code:
* [0-5]) die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}" ;;
*
* If you need support, post the output of `emerge --info '=dev-libs/sord-0.14.0::bar'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/sord-0.14.0::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/dev-libs/sord-0.14.0/work/sord-0.14.0'
| * ERROR: media-libs/suil-0.10.0::bar failed (depend phase):
* Unsupported EAPI=5 (too old) for python-any-r1
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/suil/suil-0.10.0.ebuild'
* suil-0.10.0.ebuild, line 21: Called inherit 'python-any-r1' 'waf-utils' 'multilib-minimal'
* ebuild.sh, line 314: Called __qa_source '/usr/portage/eclass/python-any-r1.eclass'
* ebuild.sh, line 112: Called source '/usr/portage/eclass/python-any-r1.eclass'
* python-any-r1.eclass, line 41: Called die
* The specific snippet of code:
* [0-5]) die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}" ;;
*
* If you need support, post the output of `emerge --info '=media-libs/suil-0.10.0::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/suil-0.10.0::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/suil-0.10.0/work/suil-0.10.0'
\ * ERROR: media-libs/mesa-18.1.9999::bar failed (depend phase):
* autotools-multilib.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/mesa/mesa-18.1.9999.ebuild'
* mesa-18.1.9999.ebuild, line 8: Called inherit 'llvm' 'autotools-multilib' 'flag-o-matic' 'python-any-r1' 'pax-utils'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=media-libs/mesa-18.1.9999::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/mesa-18.1.9999::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/mesa-18.1.9999/work/mesa-18.1.9999'
- * ERROR: media-libs/mesa-18.0.9999::bar failed (depend phase):
* autotools-multilib.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/mesa/mesa-18.0.9999.ebuild'
* mesa-18.0.9999.ebuild, line 8: Called inherit 'llvm' 'autotools-multilib' 'flag-o-matic' 'python-any-r1' 'pax-utils'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
\ * [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=media-libs/mesa-18.0.9999::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/mesa-18.0.9999::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/mesa-18.0.9999/work/mesa-18.0.9999'
| * ERROR: media-libs/mesa-17.3.9999::bar failed (depend phase):
* autotools-multilib.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/mesa/mesa-17.3.9999.ebuild'
* mesa-17.3.9999.ebuild, line 8: Called inherit 'llvm' 'autotools-multilib' 'flag-o-matic' 'python-any-r1' 'pax-utils'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=media-libs/mesa-17.3.9999::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/mesa-17.3.9999::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/mesa-17.3.9999/work/mesa-17.3.9999'
- * ERROR: media-libs/lilv-0.24.2::bar failed (depend phase):
* base.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/lilv/lilv-0.24.2.ebuild'
* lilv-0.24.2.ebuild, line 21: Called inherit 'base' 'python-any-r1' 'waf-utils' 'bash-completion-r1'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=media-libs/lilv-0.24.2::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/lilv-0.24.2::bar'`.
* Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/lilv-0.24.2/work/lilv-0.24.2'
/ * ERROR: media-libs/lilv-0.22.0::bar failed (depend phase):
* base.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/lib/layman/bar/media-libs/lilv/lilv-0.22.0.ebuild'
* lilv-0.22.0.ebuild, line 21: Called inherit 'base' 'python-any-r1' 'waf-utils' 'bash-completion-r1'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=media-libs/lilv-0.22.0::bar'`,
* the complete build log and the output of `emerge -pqv '=media-libs/lilv-0.22.0::bar'`.
\ * Working directory: '/usr/lib/python3.8/site-packages'
* S: '/var/tmp/portage/media-libs/lilv-0.22.0/work/lilv-0.22.0' |
Thanks for your help.
Laurent |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sat Jun 19, 2021 6:18 pm Post subject: |
|
|
| It looks like those are all from the layman overlay bar. Can you update that overlay? Can it be temporarily disabled? |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sat Jun 19, 2021 6:41 pm Post subject: |
|
|
It seems it is already up to date (or disappeared, not clear to me).
| Code: |
# layman -S
* Fetching remote list...
* Fetch Ok
* Syncing selected overlay(s)...
* Running Git... # ( cd /var/lib/layman/bar && /usr/bin/git pull )
Déjà à jour.
*
* Succeeded:
* ------
* Successfully synchronized overlay "bar".
*
*
* Warnings:
* ------
* Overlay "bar" could not be found in the remote lists.
* Please check if it has been renamed and re-add if necessary.
*
|
Frankly speaking, I don't remind why I had added it. Is it a way to know which element of my World file is needing it ? |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sat Jun 19, 2021 6:57 pm Post subject: |
|
|
| You could look at what installed package(s) (if any) were installed from it. It looks to me like you have the latest version of that overlay, and that version is still too old. This could happen if the maintainer abandoned it, which could also explain why it is not in the layman list of remote overlays. |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Sat Jun 19, 2021 9:08 pm Post subject: |
|
|
| And you can try using emerge --pretend --emptytree --verbose @world | grep ::bar to produce a list of packages that were installed (or are going to be installed if updates are available) from that repository. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sat Jun 19, 2021 11:23 pm Post subject: |
|
|
So it doesn't list any package.
So I tried to disable it but it's falling :
| Code: | # layman -D bar
* Disabling selected overlay(s),...
* Exception: Overlay "bar" does not exist.
* CLI: Errors occurred processing action disable
* Exception: Overlay "bar" does not exist.
|
|
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sun Jun 20, 2021 8:30 pm Post subject: |
|
|
I checked based on packages :
| Code: | # equery depends sys-process/runit
* These packages depend on sys-process/runit:
virtual/service-manager-1 (kernel_linux ? sys-process/runit)
equery depends dev-libs/sord
* These packages depend on dev-libs/sord:
media-libs/lilv-0.24.12 (dev-libs/sord[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
media-libs/sratom-0.6.8 (dev-libs/sord)
media-sound/audacity-2.4.2-r1 (lv2 ? dev-libs/sord)
# equery depends media-libs/suil
* These packages depend on media-libs/suil:
media-sound/audacity-2.4.2-r1 (lv2 ? media-libs/suil)
equery depends media-libs/mesa
* These packages depend on media-libs/mesa:
app-office/libreoffice-6.4.7.2 (media-libs/mesa[egl])
dev-qt/qtgui-5.15.2-r1 (egl ? media-libs/mesa[egl])
(eglfs ? media-libs/mesa[gbm])
(gles2-only ? media-libs/mesa[gles2])
media-libs/gst-plugins-base-1.16.3 (gles2 ? >=media-libs/mesa-9.0[egl?,gbm?,gles2?,wayland?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
(opengl ? >=media-libs/mesa-9.0[egl?,gbm?,gles2?,wayland?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
media-libs/libepoxy-1.5.5 (egl ? media-libs/mesa[egl,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
media-libs/libsdl2-2.0.14-r1 (gles2 ? >=media-libs/mesa-9.1.6[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?,gles2])
(kms ? >=media-libs/mesa-9.0.0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?,gbm])
(wayland ? >=media-libs/mesa-9.1.6[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?,egl,gles2,wayland])
media-video/movit-1.6.2 (media-libs/mesa[X(+)])
virtual/opengl-7.0-r2 (>=media-libs/mesa-9.1.6[X(+),abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
www-client/firefox-88.0.1 (>=media-libs/mesa-10.2)
x11-base/xorg-server-1.20.11 (!minimal ? >=media-libs/mesa-18[X(+),egl,gbm])
x11-libs/cairo-1.16.0-r4 (gles2-only ? >=media-libs/mesa-9.1.6[gles2,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
(opengl ? >=media-libs/mesa-9.1.6[egl,X(+),abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
x11-libs/gtk+-3.24.29 (wayland ? media-libs/mesa[wayland,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
(X ? media-libs/mesa[X(+),abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
equery depends media-libs/lilv
* These packages depend on media-libs/lilv:
media-sound/audacity-2.4.2-r1 (lv2 ? >=media-libs/lilv-0.24.6-r2)
media-video/ffmpeg-4.4 (lv2 ? media-libs/lilv[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
|
So it seems ::bar is not used by any of my explicitly emerge but created a mess on dependancies of my system.
All in all, it's not anymore used, but is it a safe way to reinstall all these stuff without braking my system ? |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sun Jun 20, 2021 10:04 pm Post subject: |
|
|
| You should be completely safe to change Portage to stop using that overlay. That will eliminate the eclass errors. If you had something installed from that overlay, you would switch back to the main tree when next rebuilding that package, not when changing the overlay configuration. For such an outdated overlay, I doubt you have anything critical installed from it. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Mon Jun 28, 2021 5:24 pm Post subject: |
|
|
So my system is now updated.
Thanks a lot for your help  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
