I see now that they have removed the "recursive flag recommendation". When I did this, I added the properties "recursively". But it SHOULD work, shouldn't it? Perhaps I should remove them and add them again, to only a subset of the folders?
Regards Carl On Mon, Dec 29, 2008 at 10:48 PM, Carl Gustafsson <[email protected] > wrote: > Hi! > > I followed the steps in the procedure for setting up Subversion with > FogBugz (the issue tracker we use): > > http://www.fogcreek.com/FogBugz/docs/60/topics/sourcecontrol/setup/TortoiseSVN.html > > After adding the properties, as specified in the above document, it worked > fine in the developers' sandboxes, but the managements' checkouts could not > be properly UPDATE:d after this. > > The "developers" group has full access to all repositories, while the > "management" group (which now has troubles) only has access to one of the > subfolders of each repos. > > Regards > Carl > > > On Mon, Dec 29, 2008 at 10:05 PM, VisualSVN Support <[email protected] > > wrote: > >> Hi! >> >> >I think it started when I added a property to the root folder and >> chose to make it recursively through the folder tree. >> >> >Thus, when I made a property change to the root (recursively through >> all folders), and the marketing department later made an UPDATE of >> their subfolder, they got this error. >> >> Could you clarify what property have you changed and how ? >> >> Could you also give us a detailed example? >> >> Thank you! >> On Wed, Dec 17, 2008 at 10:48 AM, CGU75 <[email protected]> >> wrote: >> > >> > Thank you for the suggestion. Have not tried it yet though. The >> > problem seems to come back occasionally. >> > >> > I think it started when I added a property to the root folder and >> > chose to make it recursively through the folder tree. >> > The situation is like this: >> > The developers here have access to the entire folder structure, that >> > is, from the root and down. >> > Then there is the marketing department that have access only to a >> > certain subfolder in the root. >> > Thus, when I made a property change to the root (recursively through >> > all folders), and the marketing department later made an UPDATE of >> > their subfolder, they got this error. Apparently, SVN tried to access >> > the root or some other folder to which marketing does not have access. >> > It sounds like a bug to me... >> > >> > Regards >> > Carl >> > >> > On 16 Dec, 20:24, SamS <[email protected]> wrote: >> >> I just posted that we've been stumped here as well, but I found >> >> something that worked for us. My original problem was when using a >> >> saved username/password with the Tortoise gui, so I tried on the >> >> command line and manually specified my username/password (svn update -- >> >> username asdf --password asdf) and it worked. So, tried clearing the >> >> Tortoise saved login info, and it ended up working once I was >> >> prompted. >> >> >> >> Sorry I can't provide a root cause, but hopefully this helps someone - >> >> >> >> Sam >> >> >> >> On Dec 15, 9:48 am, CGU75 <[email protected]> wrote: >> >> >> >> > We have also problems with this. Some of our coworkers can not >> UPDATE. >> >> > The only solution we have come up with is to CHECKOUT the entire >> repos >> >> > again, which is not a good solution... >> >> >> >> > I am also interested in a solution to this. Bugfix? >> >> >> >> > Regards >> >> > Carl >> >> >> >> > On 26 Nov, 20:32, [email protected] wrote: >> >> >> >> > > I am getting the same error . Is this a known bug. >> >> > > I am using 1.5 .3 Version on SVN and When I try to commit to >> >> > > repository it throws Commit failed. >> >> > > Server sent Unexpected return value (403 Forbidden ) in respons to >> >> > > MKACTIVITY >> >> >> >> > > Please provide a resolution. >> >> >> >> > > On Nov 26, 7:19 am, [email protected] wrote: >> >> >> >> > > > Hi all. >> >> >> >> > > > I was trying to browse via repo-browser, and I got error message >> >> > > > when I wrote the URL:https://vm03.timetoknow.local:8443/svn >> >> > > > I got the error: "server sent unexpected return value (405 method >> not >> >> > > > allowed) in response to PROPFIND request for svn." >> >> >> >> > > > So I tried to checkout files from the repository >> >> > > > I wrote the command: >> >> > > > svn >> cohttps://vm03.timetoknow.local:8443/svn/dev/LMS/branch/v2.3/2.3 >> >> >> >> > > > And I got the following error: >> >> > > > svn: Server sent unexpected return value (403 Forbidden) in >> response >> >> > > > to OPTIONS >> >> > > > request for ' >> https://vm03.timetoknow.local:8443/svn/dev/LMS/branch/ >> >> > > > v2.3/2.3' >> >> >> >> > > > I was working with SVN 1.4.5 without Apache, and then I moved the >> >> > > > folders to another server, installed the VisualSVN working with >> >> > > > Apache. I added the repository, so I can see it with the >> visualSVN, >> >> > > > and I can browse there but I can't work remotely. >> >> >> >> > > > Why am I getting those errors ? >> > >> >> >> >> -- >> Olga Dolidze >> VisualSVN Support >> > >
