When rhg.on-unsupported is configured to fallback and an unsupported
feature is encountered, the previous default was to look for an hg
executable in $PATH.
This default was fragile since it was easy to end up accidentally using
an older version of Mercurial installed system-wide,
when a local (perhaps patched) installation was intended.
Instead, it is now an error to have rhg.on-unsupported=fallback
without also configuring an explicit path or the fallback executable.
That message in a bit long, what about:
to get < 80 char ?