[patch] Patch to fix command validation warnings

0001-portageq-envvar-preserve-PATH-to-avoid-command-valid.patch (text/plain), 1.25 KB, created by Lucio Sauer on 2024-05-10 13:06:08 UTC

From 4f5d0871450a16d0ac00886e2306ef6f05a0367e Mon Sep 17 00:00:00 2001
From: Lucio Sauer <[e-mail]>
Date: Fri, 10 May 2024 13:59:16 +0200
Subject: [PATCH 1/2] portageq envvar: preserve PATH to avoid command
 validation warnings

Some of Portage's environment variables undergo command validation.
When one is set to a relative value, Portage relies on PATH to find the
binary.
We need to preserve it after purging the environment (`env -i`) if we
want to avoid "<key> is invalid: <value>" warnings.

For Portage 3.0.63, this affects
PORTAGE_{B{,UN}ZIP2_COMMAND,LOG_FILTER_FILE_CMD}.

Bug: https://bugs.gentoo.org/588642
Signed-off-by: Lucio Sauer <[e-mail]>
---
 completions/portageq | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/completions/portageq b/completions/portageq
index 7922e59..a8a113b 100644
--- a/completions/portageq
+++ b/completions/portageq
@@ -47,7 +47,7 @@ _portageq() {
 
     # this also isn't the fastest, but I welcome an alternative method
     envvar)
-        COMPREPLY=($(compgen -W "$(env -i emerge -v --info | \
+        COMPREPLY=($(compgen -W "$(env -i PATH="${PATH}" emerge -v --info | \
                 sed -n -e '/^[[:upper:]].*=".*"/s/^\(.*\)=".*$/\1/p')" -- ${cur}))
         ;;
 
-- 
2.43.2