| View previous topic :: View next topic |
| Author |
Message |
tsigarid
n00b
Joined: 27 Mar 2010
Posts: 11
|
 Posted: Sun Dec 22, 2024 8:45 pm Post subject: Where has x11-libs/libXp gone? |
 |
|
[Administrator note: this post and only this post, was originally attached to the solved topic Where has x11-libs/libXp gone? [SOLVED]. This post was off-topic there, and was likely to be missed since the thread was already solved, so I split it out. -Hu]
Reviving this old thread, because after an update I now get the following:
| Code: | * ERROR: x11-libs/libXp-1.0.3::local failed (depend phase):
* xorg-3: EAPI 7 not supported
*
* Call stack:
* ebuild.sh, line 632: Called source '/var/db/repos/local/x11-libs/libXp/libXp-1.0.3.ebuild'
* libXp-1.0.3.ebuild, line 7: Called inherit 'xorg-3'
* ebuild.sh, line 312: Called __qa_source '/var/db/repos/gentoo/eclass/xorg-3.eclass'
* ebuild.sh, line 123: Called source '/var/db/repos/gentoo/eclass/xorg-3.eclass'
* xorg-3.eclass, line 27: Called die
* The specific snippet of code:
* *) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
*
* If you need support, post the output of `emerge --info '=x11-libs/libXp-1.0.3::local'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libXp-1.0.3::local'`.
* Working directory: '/usr/lib/python3.12/site-packages'
* S: '/var/tmp/portage/x11-libs/libXp-1.0.3/work/libXp-1.0.3'
* ERROR: x11-base/printproto-1.0.5-r1::local failed (depend phase):
* xorg-3: EAPI 7 not supported
*
* Call stack:
* ebuild.sh, line 632: Called source '/var/db/repos/local/x11-base/printproto/printproto-1.0.5-r1.ebuild'
* printproto-1.0.5-r1.ebuild, line 7: Called inherit 'xorg-3'
* ebuild.sh, line 312: Called __qa_source '/var/db/repos/gentoo/eclass/xorg-3.eclass'
* ebuild.sh, line 123: Called source '/var/db/repos/gentoo/eclass/xorg-3.eclass'
* xorg-3.eclass, line 27: Called die
* The specific snippet of code:
* *) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
*
* If you need support, post the output of `emerge --info '=x11-base/printproto-1.0.5-r1::local'`,
* the complete build log and the output of `emerge -pqv '=x11-base/printproto-1.0.5-r1::local'`.
* Working directory: '/usr/lib/python3.12/site-packages'
* S: '/var/tmp/portage/x11-base/printproto-1.0.5-r1/work/printproto-1.0.5' |
IDL still works, but I can't decode this message. Is it that some dependency requires libXp and/or printproto to recompile, but years after they have been abandoned, this is not any more possible because said dependencies have moved away from some legacy code that they require? Most importantly, am I understanding right that I will be getting this error message after every emerge moving forward, but I can ignore it?
Thanks |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22865
|
| Posted: Sun Dec 22, 2024 11:04 pm Post subject: Re: Where has x11-libs/libXp gone? |
|
|
| tsigarid wrote: | | Reviving this old thread, because after an update I now get the following: |
I think reviving the old thread was incorrect. The old thread dealt with the absence of a specific DSO. Your issue is that Portage is rejecting an ebuild. They are tangentially connected in that you probably have the ebuild because you were trying to work around the absence of the DSO, but the solution in that thread will not help you here. Additionally, posting new problems in previously solved threads risks that the problem will be missed by new helpers.
| tsigarid wrote: | | Code: | * ERROR: x11-libs/libXp-1.0.3::local failed (depend phase):
* xorg-3: EAPI 7 not supported |
IDL still works, but I can't decode this message. Is it that some dependency requires libXp and/or printproto to recompile, but years after they have been abandoned, this is not any more possible because said dependencies have moved away from some legacy code that they require? Most importantly, am I understanding right that I will be getting this error message after every emerge moving forward, but I can ignore it? |
The maintainer of the overlay ::local needs to update this ebuild to a supported EAPI. You will not be able to rebuild this ebuild until that is done. You will continue to get errors from Portage until the ebuild is removed from the system or updated.
The inability to use this ebuild will not impact the files it previously installed, so anything depending on these obsolete files can continue to work. On principle, I recommend against ignoring errors like this. That habit makes it easy to ignore important errors that need immediate attention, when they are lost amid the errors you are intentionally ignoring and not fixing. |
|
| 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
