On Fri, 15 Nov 2013 21:53:02 +0100 Stephan Beal <[email protected]> wrote:
> On Fri, Nov 15, 2013 at 9:47 PM, <[email protected]>wrote: > > > I'm suddenly seeing "not authorized to write" on attempting to push > > to a newly created and cloned repository. Is there some way to get > > either the server or the client to give more information? I've created > > and cloned this repository the same way as the other 44 repositories > > here, and have never seen this problem before! > > > > > When i've seen this before it's been a genuine problem/mishap in my setup > of the user's permissions. Make sure the user has (or inherits) the 'i' > permission. In the normal case this is inherited from the 'developer' ('v') > permission, so make sure that the 'developer' special user has the 'i' > permission. > > There was one particular case where i saw this intermittently on a > particular repo, but a second or third attempt to push succeeded. Seems that I have the correct capabilities: $ fossil user capabilities developer -R examples.fossil dei $ fossil user capabilities m0 -R examples.fossil si I've even nuked the repository, created a new one, cloned it, and had the same problem again... M _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
