server error on creating project that exists in file system already

[Guy K. Kloss]

When creating a project that already exists in the file system, Sloecode returns with a "system error". This should be handled more gracefully. Although, this is *not* really a common use case, but can happen in case something goes wrong somewhere. This is what the Apache error log shows:

[Thu Jan 05 16:50:56 2012] [error] [client 156.62.70.135] Error - <class 'bzrlib.errors.FileExists'>: File exists: u'/srv/sloecode/bzr-repos/project/dms717287/.bzr': [Errno 17] File exists: '/srv/sloecode/bzr-repos/project/dms717287/.bzr'

In contrary, when the (also) not so common use case occurs that a user should be created that exists in the file system already, Sloecode handles the issue more gracefully, and *only* the error log contains a warning:

[Thu Jan 05 16:48:03 2012] [error] Warning: path '/srv/sloecode/bzr-repos/person/gkloss' already exists, not creating repository for user 'gkloss'