| 1 |
On Thu, May 6, 2021 at 6:54 AM Joakim Tjernlund |
| 2 |
<Joakim.Tjernlund@××××××××.com> wrote: |
| 3 |
> |
| 4 |
> On Wed, 2021-05-05 at 16:47 +0000, Joakim Tjernlund wrote: |
| 5 |
> > I am upgrading an old portage(2.3.76) to 3.0.18 using qmerge(binary pkg) and I get this: |
| 6 |
> > qmerge -OK sys-apps/portage |
| 7 |
> > [R] sys-apps/portage-3.0.18 |
| 8 |
> > * Checking for suitable kernel configuration options... |
| 9 |
> > [ ok ] |
| 10 |
> > * Using python3.8 in global scope |
| 11 |
> > FEATURES variable contains unknown value(s): disabled |
| 12 |
> > Traceback (most recent call last): |
| 13 |
> > File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main |
| 14 |
> > return _run_code(code, main_globals, None, |
| 15 |
> > File "/usr/lib/python3.8/runpy.py", line 87, in _run_code |
| 16 |
> > exec(code, run_globals) |
| 17 |
> > 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 <module> |
| 18 |
> > main() |
| 19 |
> > 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 |
| 20 |
> > config_path = os.path.join(os.environ['ED'], GLOBAL_CONFIG_PATH.lstrip(os.sep), 'make.globals') |
| 21 |
> > File "/usr/lib/python3.8/os.py", line 675, in __getitem__ |
| 22 |
> > raise KeyError(key) from None |
| 23 |
> > KeyError: 'ED' |
| 24 |
> > |
| 25 |
> > so portage fails to install properly, I am guessin this is becuse I have an old portage to begin with? |
| 26 |
> > Can it be fixed? |
| 27 |
> |
| 28 |
> The error goes away when I do: ED=/ qmerge -OK sys-apps/portage |
| 29 |
> Does that mean that it is qmerge(aka portage-utils) that needs to set ED during merge? which PHASES ? |
| 30 |
|
| 31 |
According to PMS, a package manager must define ED in src_install, |
| 32 |
pkg_preinst, and pkg_postinst. |
Archives