'svn' n'est pas reconnu en tant que commande interne ou externe, un programme executable ou un fichier de commandes.
Tout à fait normal
Error: failed retrieving version information.
Dingue!
The solution to this riddle is easy: You are using the Windows-moronised form of TortoiseSVN
Unluckily, making it work for you requires you to install the commandline
svn client for now.
To explain:
autorevision tries to get the revision information from
svn (which is the canonical way of doing it). If that fails, it will open the file
./.svn/entries and parse that. It's a nasty thing, but it does the job.
TortoiseSVN does not come with
svn.exe, so this will certainly fail. Strange enough, opening the
entries file fails, too. You wonder why.
This problem is a good example why you should never do things like parsing something if you can use a canonical tool for it (and that's why
autorevision first tries to query
svn).
Now here is the problem: Some versions of Windows are too darn stupid to work with a directory called
.svn. As a nasty workaround hack, TortoiseSVN released a special moronised version for Windows that would use
_svn instead of
.svn. Unluckily, this actually worked out so fine (apart from being non-standard) that it was made an official feature. Subversion can now store its files in either
.svn or
_svn, and you have no way of knowing which one, except if you manually parse the config file or if you test both locations...
I shall add a "fix" for this to autorevision one day (i.e. check both possible locations).
Until then, sorry for the inconvenience, but you have to install the commandline client too (and have to put it into
PATH).
