start-commit bug?

I came across what I think is a bug with the start-commit hook. Have not found evidence that this is a know bug.
Submitting here before I post to the dev list.

I am running ver. 1.5.0 of the server and client.
I have authentication on for select users with write access
I have a start-commit hook that checks the capabilities parameter for the 'mergeinfo' string.
This hook script rejects the commit and throws an error if this string does not exist.

Everything works fine if you are already authenticated but if you need to authenticate then
the capabilities parameter is empty and the start-hook an error.

Steps to reproduce:
using ver. 1.5.0 of the client and server:
   1. create a start-commit hook script (see attachments)
   2. checkout some project from your repository and make some changes
   3. delete ~/.subversion/auth directory
   4. commit changes to your repository (should ask for your username/password)
   5. authenticate yourself

expected results:
   1. should allow you commit your changes

actual results:
   1. rejects commit and spews out error message from the hook script.

Is this a known bug and can anybody else verify this?

Thanks,

Jay

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org