Issue 147: 'mtn ls dbs' will sometimes display managed databases with their full path

Reported by Richard Levitte, Feb 22, 2011

Steps to reproduce the problem:
-------------------------------

1. Make sure to have a database made with an older monotone (say, 
0.99.1)
2. Upgrade to a newer monotone (say, 1.0dev)
3. do 'mtn ls dbs'

Expected result:
----------------

...
mtn: warning: database :richard.levitte.org:snapshots.mtn is laid 
out according to an old schema
mtn: warning: try 'mtn db migrate' to upgrade
mtn: warning: (this is irreversible; you may want to make a backup 
copy first)
mtn: warning: ignoring database ':richard.levitte.org:snapshots.mtn'
...

Actual results:
---------------

...
mtn: warning: database 
/home/levitte/.monotone/databases/richard.levitte.org:snapshots.mtn 
is laid out according to an old schema
mtn: warning: try 'mtn db migrate' to upgrade
mtn: warning: (this is irreversible; you may want to make a backup 
copy first)
mtn: warning: ignoring database 
'/home/levitte/.monotone/databases/richard.levitte.org:snapshots.mtn'

...

Output of `mtn version --full`:
-------------------------------

: ; mtn version --full
monotone 1.0dev (base revision: 
3bf5cb27637aab8b76b1e64278ab35365b5efdcf)
Running on          : Linux 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 
UTC 2011 i686
C++ compiler        : GNU C++ version 4.4.5
C++ standard library: GNU libstdc++ version 20110215
Boost version       : 1_42
SQLite version      : 3.7.4 (compiled against 3.7.4)
Lua version         : Lua 5.1
PCRE version        : 8.12 2011-01-15 (compiled against 8.12)
Botan version       : 1.8.11 (compiled against 1.8.11)
Changes since base revision:
format_version "1"

new_manifest [11f5cef84295e4f09ee35de992769358aebe6021]

old_revision [3bf5cb27637aab8b76b1e64278ab35365b5efdcf]

patch "Makefile.am"
 from [afb4061158473f26fc5e1b809cc27d3cdd6077a1]
   to [649016eb8a3f32c966f29a03e1afc219be6d1858]

  Generated from data cached in the distribution;
  further changes may have been made.

Comment 1 by Thomas Keller, Feb 23, 2011

This is a general problem - as soon as we resolved the alias to a 
physical path, we use that for diagnostic and error messages, and 
not the aliased name.

Comment 2 by Stephen Leake, Feb 23, 2011

That's not a problem, it's a feature! Error messages should always 
be as clear as possible. The user can easily be confused by search 
paths. 

What's wrong with using the full path in error messages?

Comment 3 by Richard Levitte, Feb 23, 2011

In this particular case, the normal output from 'mtn ls dbs' is 
database aliases.  It would be more consistent if the error messages 
did the same.