On Fri, Sep 13, 2024 at 3:27 PM Jörg Dalkolmo <joerg.dalko...@gmx.net> wrote: > > Hello Johan, > > Thanx a lot for your annotations. > Unfortunately I am not allowed, and for us there is no colleague available to > check the configuration on the SVN server if there are any path-based > authorization settings, and if yes, if they affect our part of the repository. > > Are there any other scenarios thinkable than failed authorization, which > could lead to the ‚server-excluded‘ entry in the presence column? Perhaps > interrupted connection from client to server, or something else?
Well, in theory there could be other reasons (all the client knows for sure is that the server excluded this node). But in practice, as far as I know, failed path-based authorization is the only reason for server-exclusion that has been implemented in the standard SVN server. Specifically, an interrupted connection cannot cause 'server-excluded' nodes. Those would get a 'not-present' (for files) or 'incomplete' (for directories) status in the wc.db, as far as I remember. -- Johan
