Comment 2 for bug 1025848

About "No version file found". User has no clue why such error is printed on his/her screen, how serious problem it is, and what should be done to fix it, especially since the version number is printed there. I don't have any idea either, so I don't know how to fix it, but as version information seems to be very nicely found despite of this error message, I can only assume that the error message can be just removed. If removing is not possible, the error message can perhaps be improved to answer (some of) these questions.

"This is Widelands-bzr6413[trunk](Release)" E.g. Firefox shows following information in nightly builds "15.0a1 (2012-04-25)". This tells me that this is an alpha release for something that will be Firefox 15 once released. It also tells me that the build is several months old. Providing the bzr revision does no harm as it probably makes bug reporting much easier. Even small improvements (e.g. the date) would be great.

To give exact answer to your question, I would be happy to see something like this "Widelands-build-18-alpha-bzr6413 (2012-04-25)". [trunk](Release) can be there also, thought the "Release" made me think that it was actually official release, but version number was just not printed correctly because of the above error message.