Modified roundup-admin so that it stops when it sees a property error.
If run non-interactively it exits status 1 to make it more useful in 
shell scripts.

rev 6393:51a1a9b0f567

Still would like to put this check in Tracker::__init__. But that is 
not called until the tracker web or email interfaces are triggered.
If you set the Tracker object's self.schema_hook(self, **env) you get 
access to env['db'].security.role which can be used to validate
the permissions.

However this never gets called at daemon startup using roundup-demo.
It is only called on the first connection to the web interface.

I assume it similarly is never called in other modes until the first
web or email gateway request comes in.

So I think this is as fixed as it is going to get. I think any
attempt to validate at startup the way we do config.ini is going
to need some extensive surgery.

I added info about this change to upgrading.txt.