> On 24.03.2010 14:41, Lucien Okkes wrote:
> >> On 11.03.2010 09:54, Lucien Okkes wrote:
> >>
> >>>
> >>> Stefan, thanks for your suggestions. We have tested the
> >>> replication of empty files and this works ok. The file that can't
> >>> be opened has an unique filename.
> >>>
> >>> We noticed that the missing file is located in the \.svn\
> >>> directory (see attachment in first post). The developers stated
> >>> that the error is always related to files in a .svn directory.
> >>> Does this ring a bell?
> >>
> >> The .svn dirs are marked as system folders and are therefore
> >> usually hidden. Maybe your replication has problems with those? Or
> >> the ACLs are not copied properly?
> >
> > The replication has no problems with hidden files, system directories
> > or ACLs.
> >
> > Today we encountered the same error. This time I have more detailed
> > information. Developer 1 and developer 2 both have a working copy of
> > the project. Developer 1 made some changes and commits. Developer 2
> > tries to update the working copy but walks into the "can't open file"
> > error (see attachment). The missing file is available in the working
> > copy of developer 1, but not in the working copy of developer 2.
>
> So, the replication didn't replicate that file?
> That means you have a problem with your replication, not SVN.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
Stefan, each developer has a subdirectory on a shared drive on the citrix server. The developers working copy is placed in his own subdirectory. This share including all subdirectories is replicated between the two citrix servers.
Schematically:
Citrix server A
- Shared drive E:
--- Subdirectory developer 1
----- Working copy developer 1
--- Subdirectory developer 2
----- Working copy developer 2
Citrix server B
- Shared drive E:
--- Subdirectory developer 1
----- Working copy developer 1
--- Subdirectory developer 2
----- Working copy developer 2
The problem is that the file is available in the working of developer 1 but not in the working copy of developer 2. The replicated working copies are identical. So I don't think this problem is related to replication.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2464725
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-25 08:26:31 CET