Bug 475778 – sys-apps/portage-2.1.12.11: emerge --info with ROOT: No such file or directory: '/var/db/pkg/...'

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Bertrand Jacquin 2013-07-04 22:45:52 UTC]

When running to (wrong) given command, portage output an error :

MAKEOPTS=-j1 ARCH=x86 i686-w64-mingw32-emerge -vat openssl --info > /tmp/info.log

In this case, stdout from emerge is correct and /tmp/info.log is fine

Traceback (most recent call last):
  File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 661, in aux_get
    mydir_stat = os.stat(mydir)
  File "/usr/lib64/portage/pym/portage/__init__.py", line 259, in __call__
    rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory: '/var/db/pkg/dev-libs/openssl-1.0.0j'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/emerge", line 50, in <module>
    retval = emerge_main()
  File "/usr/lib64/portage/pym/_emerge/main.py", line 1065, in emerge_main
    return run_action(emerge_config)
  File "/usr/lib64/portage/pym/_emerge/actions.py", line 3944, in run_action
    emerge_config.trees, emerge_config.opts, valid_atoms)
  File "/usr/lib64/portage/pym/_emerge/actions.py", line 1710, in action_info
    metadata = dict(zip(auxkeys, vardb.aux_get(cpv, auxkeys)))
  File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 665, in aux_get
    raise KeyError(mycpv)
KeyError: 'dev-libs/openssl-1.0.0j'

Full output attached

Reproducible: Always

[Comment 1 Bertrand Jacquin 2013-07-04 22:46:17 UTC]

Created attachment 352632 [details]
emerge --info

[Comment 2 Bertrand Jacquin 2013-07-04 22:46:41 UTC]

Created attachment 352634 [details]
emerge --info stderr

[Comment 3 Zac Medico 2013-07-05 05:36:01 UTC]

This is fixed in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=541539c8bd89e4ee82ddfa250aa5bc82a0a167d0

[Comment 4 Zac Medico 2013-07-07 21:00:25 UTC]

This is fixed in 2.1.12.12 and 2.2.0_alpha187.

[Comment 5 Bertrand Jacquin 2013-07-07 21:27:29 UTC]

(In reply to Zac Medico from comment #4)
> This is fixed in 2.1.12.12 and 2.2.0_alpha187.

Thanks a lot Zac !