Fuzzy finders triggers for invalid package dependencies and set elements

[dleverton]

For example, a user had media-libs/gst-plugins installed, but it was removed from the tree a while ago:

Building target list... 
Building dependency list...
Query error:
  * In program paludis -ip everything --dl-installed-deps-pre pre:
  * When performing install action from command line:
  * When executing install task:
  * When building dependency list:
  * When adding PackageDepSpec 'media-libs/gst-plugins':
  * No versions of 'media-libs/gst-plugins' are available. Looking for suggestions:
No suggestions found.

The "suggestions" message at the end is confusing, as it may look as though it's complaining about "everything"; in any case, it's not likely to find anything except by coincidence. It could still be useful to search if the DepSpec? comes from a user-defined set, but that might be harder to implement.

It also triggers if, say, an ebuild contains "foo/bar" in DEPEND - there's probably nothing the user can do about that, so no point in looking for suggestions.

[ferdy]

In r4100