Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qubes-core-qrexec-4.1.32 build fails in qubes 4.1 with "portageq is not allowed in ebuild scope" #19

Closed
colons opened this issue Nov 21, 2023 · 4 comments

Comments

@colons
Copy link

colons commented Nov 21, 2023

sorry if you're already tracking this. probably related: https://bugs.gentoo.org/916296

>>> Preparing source in /var/tmp/portage/app-emulation/qubes-core-qrexec-4.1.23/work/qubes-core-qrexec-4.1.23 ...
 * ERROR: app-emulation/qubes-core-qrexec-4.1.23::qubes failed (prepare phase):
 *   portageq is not allowed in ebuild scope
 * 
 * Call stack:
 *          ebuild.sh, line  136:  Called src_prepare
 *        environment, line 4555:  Called qubes_verify_sources_git 'v4.1.23'
 *        environment, line 4430:  Called portageq 'get_repo_path' '/' 'qubes'
 *   phase-helpers.sh, line 1010:  Called die
 * The specific snippet of code:
 *   	die "portageq is not allowed in ebuild scope"

you can work around this by replacing the portageq invocation in eclass/qubes.eclass with a hard-coded path to your qubes repo, but that's not ideal for a number of reasons (and the build still fails due to the _FORTIFY_SOURCE redefinition talked about in #12, which requires additional patching)

@lubellier
Copy link

lubellier commented Dec 15, 2023

I saw the same issue today.
A new xorg update activated a qubes-gui-agent re-build which raised the above error message.
Portageq is deprecated in the eclass scope. I'm searching how to replace the portageq usage in qubes.eclass...

@lubellier
Copy link

I'm searching how to replace the portageq usage in qubes.eclass...

I only found hacks:

  1. hardcoded absolute path (i.e. : QUBES_OVERLAY_DIR="/var/db/repos/qubes"), see
  2. portageq full path (i.e. : QUBES_OVERLAY_DIR="$(/usr/bin/portageq get_repo_path / qubes)"), see

and the least-worst solution :

  1. a default path with an available override, see the gentooLTO workaround

Someone with a better solution ?

Resources:

  1. Portageq depreciated, causes warnings while building anything InBetweenNames/gentooLTO#883

@lubellier
Copy link

@colons could you test the now updated repository? And if solved, close this issue.

@colons
Copy link
Author

colons commented Dec 20, 2023

stuff still doesn't build (due to #12), but yes this issue appears to be solved. thank you

@colons colons closed this as completed Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants