| 1 |
On 04/26/11 10:31, Dan Cowsill wrote: |
| 2 |
> |
| 3 |
> Why I love this list in one thread. |
| 4 |
> |
| 5 |
> Anyway, just an update on the situation. As far as I can tell, this |
| 6 |
> 'you have no world file' error only shows up when i'm doing a |
| 7 |
> --depclean. Also, it is intermittent. Right now, -pcv works just fine |
| 8 |
> and reports the correct number of packages to be removed (zero). I'm |
| 9 |
> not sure what breaks this, or if it will be broken in the future. |
| 10 |
> |
| 11 |
> At this point, I'm not terribly worried about the whole thing, but I am |
| 12 |
> rather curious. |
| 13 |
> |
| 14 |
|
| 15 |
Well, the "You have no world" message only shows up in one place. |
| 16 |
|
| 17 |
/usr/lib/portage/pym/_emerge/actions.py: |
| 18 |
|
| 19 |
psets = root_config.setconfig.psets |
| 20 |
... |
| 21 |
selected_set = psets['selected'] |
| 22 |
... |
| 23 |
if not selected_set: |
| 24 |
writemsg_level("!!! You have no world file.\n", |
| 25 |
level=logging.WARNING, noiselevel=-1) |
| 26 |
|
| 27 |
|
| 28 |
The 'psets' variable gets set in /usr/lib/portage/pym/_emerge/main.py: |
| 29 |
|
| 30 |
setconfig.psets['selected'] = |
| 31 |
WorldSelectedSet(root_config.settings['EROOT']) |
| 32 |
|
| 33 |
and that WorldSelectedSet class is defined in, |
| 34 |
|
| 35 |
/usr/lib/portage/pym/portage/_sets/files.py |
| 36 |
|
| 37 |
|
| 38 |
If you *really* want to know what's going on, you could throw some debug |
| 39 |
statements in main.py whenever the 'psets' variable gets set. That way |
| 40 |
you can at least see which file it's looking for. |
| 41 |
|
| 42 |
I'm not a doctor but it's probably perfectly safe. |
Archives