I'm using 2.2_rc33. I have a reference to a no-longer valid set, the "@kde", in my world set file. When I try to run `emerge -av kde-meta:4.2`, I get absolutely misleading error message:
velbloud ~ # emerge -1av kde-meta:4.2
These are the packages that would be merged, in order:
Calculating dependencies |emerge: There are no sets to satisfy 'kde'. The following sets exist:
Followed by a list of known sets. It should be also noted that this behavior is not completely consistent -- sometimes I get a list of packages that would be merged, if there wasn't a blocker (I'm not discussing the blocker here, that's irrelevant for this bugreport), sometimes I get just the error message.
Anyway, I firmly believe that having an invalid set name in the world file should not stop Portage from working.