Re: [gentoo-portage-dev] KeyError: 'ED' ?
On 09-06-2021 14:19:38 -0400, Mike Gilbert wrote: > On Thu, May 6, 2021 at 6:54 AM Joakim Tjernlund > wrote: > > > > On Wed, 2021-05-05 at 16:47 +, Joakim Tjernlund wrote: > > > I am upgrading an old portage(2.3.76) to 3.0.18 using qmerge(binary pkg) > > > and I get this: > > > qmerge -OK sys-apps/portage > > > [R] sys-apps/portage-3.0.18 > > > * Checking for suitable kernel configuration options... > > > [ ok ] > > > * Using python3.8 in global scope > > > FEATURES variable contains unknown value(s): disabled > > > Traceback (most recent call last): > > > File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main > > > return _run_code(code, main_globals, None, > > > File "/usr/lib/python3.8/runpy.py", line 87, in _run_code > > > exec(code, run_globals) > > > File > > > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > > > line 93, in > > > main() > > > File > > > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > > > line 63, in main > > > config_path = os.path.join(os.environ['ED'], > > > GLOBAL_CONFIG_PATH.lstrip(os.sep), 'make.globals') > > > File "/usr/lib/python3.8/os.py", line 675, in __getitem__ > > > raise KeyError(key) from None > > > KeyError: 'ED' > > > > > > so portage fails to install properly, I am guessin this is becuse I have > > > an old portage to begin with? > > > Can it be fixed? > > > > The error goes away when I do: ED=/ qmerge -OK sys-apps/portage > > Does that mean that it is qmerge(aka portage-utils) that needs to set ED > > during merge? which PHASES ? > > According to PMS, a package manager must define ED in src_install, > pkg_preinst, and pkg_postinst. Perhaps qmerge should use export for these vars. In any case this seems tracked in bug 792273. -- Fabian Groffen Gentoo on a different level signature.asc Description: PGP signature
Re: [gentoo-portage-dev] KeyError: 'ED' ?
On Thu, May 6, 2021 at 6:54 AM Joakim Tjernlund wrote: > > On Wed, 2021-05-05 at 16:47 +, Joakim Tjernlund wrote: > > I am upgrading an old portage(2.3.76) to 3.0.18 using qmerge(binary pkg) > > and I get this: > > qmerge -OK sys-apps/portage > > [R] sys-apps/portage-3.0.18 > > * Checking for suitable kernel configuration options... > > [ ok ] > > * Using python3.8 in global scope > > FEATURES variable contains unknown value(s): disabled > > Traceback (most recent call last): > > File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main > > return _run_code(code, main_globals, None, > > File "/usr/lib/python3.8/runpy.py", line 87, in _run_code > > exec(code, run_globals) > > File > > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > > line 93, in > > main() > > File > > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > > line 63, in main > > config_path = os.path.join(os.environ['ED'], > > GLOBAL_CONFIG_PATH.lstrip(os.sep), 'make.globals') > > File "/usr/lib/python3.8/os.py", line 675, in __getitem__ > > raise KeyError(key) from None > > KeyError: 'ED' > > > > so portage fails to install properly, I am guessin this is becuse I have an > > old portage to begin with? > > Can it be fixed? > > The error goes away when I do: ED=/ qmerge -OK sys-apps/portage > Does that mean that it is qmerge(aka portage-utils) that needs to set ED > during merge? which PHASES ? According to PMS, a package manager must define ED in src_install, pkg_preinst, and pkg_postinst.
Re: [gentoo-portage-dev] KeyError: 'ED' ?
On Wed, 2021-05-05 at 16:47 +, Joakim Tjernlund wrote: > I am upgrading an old portage(2.3.76) to 3.0.18 using qmerge(binary pkg) and > I get this: > qmerge -OK sys-apps/portage > [R] sys-apps/portage-3.0.18 > * Checking for suitable kernel configuration options... > [ ok ] > * Using python3.8 in global scope > FEATURES variable contains unknown value(s): disabled > Traceback (most recent call last): > File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main > return _run_code(code, main_globals, None, > File "/usr/lib/python3.8/runpy.py", line 87, in _run_code > exec(code, run_globals) > File > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > line 93, in > main() > File > "/var/tmp/qmerge/sys-apps/portage-3.0.18/image/usr/lib/python3.8/site-packages/portage/_compat_upgrade/default_locations.py", > line 63, in main > config_path = os.path.join(os.environ['ED'], > GLOBAL_CONFIG_PATH.lstrip(os.sep), 'make.globals') > File "/usr/lib/python3.8/os.py", line 675, in __getitem__ > raise KeyError(key) from None > KeyError: 'ED' > > so portage fails to install properly, I am guessin this is becuse I have an > old portage to begin with? > Can it be fixed? The error goes away when I do: ED=/ qmerge -OK sys-apps/portage Does that mean that it is qmerge(aka portage-utils) that needs to set ED during merge? which PHASES ? Jocke
