No, we don't use path-based authorization. All developers (accounts) have the same permissions (even the merge user account). Regarding the mergeinfo questions: the branch entry is "<path-to-trunk>/9746-10001,10003-10205. The missing Rev 10002 was exactly the one that couldn't be merged due to the errors reported earlier. We merged the changes according to the description given here: http://blog.red-bean.com/sussman/?p=92
Michael -----Original Message----- From: Stefan Sperling [mailto:s...@elego.de] Sent: Montag, 6. September 2010 14:27 To: Ungruhe, Michael Cc: users@subversion.apache.org; Strucken, Andreas Subject: Re: Merge problem with different users On Mon, Sep 06, 2010 at 02:44:30AM -0700, Ungruhe, Michael wrote: > The "merge user" is just a user account. Since we noticed that the > problem described earlier only occurs when the merging is made by > different users (on different user accounts), we created a new user > account (called mergeuser) that all developers use for merging (and > reintegration). So the users itself are still different, but they use > the same account. Ok, but do you have answers to my questions regarding mergeinfo? I'm trying to figure out where your problem is coming from, and so far, it sounds like one or more of your developers are doing merges in a way that prevents mergeinfo from being recorded correctly, for whatever reason. Another question: Do you use path-based authorisation? Do the accounts involved in the merges all have the same set of permissions, or are there differences that might explain your problems? Stefan
