Bug 186960 – sys-apps/portage-2.1.3_rc9: traceback when ROOT dir does not exist

• Status: RESOLVED FIXED
• Product: Portage Development

[Description solar (RETIRED) 2007-07-29 06:00:36 UTC]

While helping another dev I noticed this new traceback.  
In the past portage always properly just created the ROOT directory.

ROOT=$PWD/beandog emerge -pvK busybox 
Traceback (most recent call last):
  File "/usr/bin/emerge", line 6357, in ?
    retval = emerge_main()
  File "/usr/bin/emerge", line 6058, in emerge_main
    settings, trees, mtimedb = load_emerge_config()
  File "/usr/bin/emerge", line 5943, in load_emerge_config
    trees = portage.create_trees(trees=trees, **kwargs)
  File "/usr/lib/portage/pym/portage.py", line 8621, in create_trees
    config_incrementals=portage_const.INCREMENTALS)
  File "/usr/lib/portage/pym/portage.py", line 1324, in __init__
    check_var_directory("ROOT", target_root)
  File "/usr/lib/portage/pym/portage.py", line 1059, in check_var_directory
    raise portage_exception.DirectoryNotFound(var)
portage_exception.DirectoryNotFound: /root/beandog/

uClibc ~ # qlist -U portage -ev
sys-apps/portage-2.1.3_rc9 (elibc_uclibc userland_GNU)

[Comment 1 Zac Medico 2007-07-30 07:55:03 UTC]

Thanks, this is fixed in svn r7517.

[Comment 2 Zac Medico 2007-07-31 22:39:29 UTC]

This has been released in 2.1.2.11.