I have 2 text files. I want to copy the change from one to the other. I have one file checked out from the repository and one file on my hard drive. Neither one is read-only, but from the diff screen, it lists that both are read-only.
I just installed version 3 of the server and the client.
Any ideas?
Diff shows files as read only ... cannot copy change
Moderator: SourceGear
Diff shows files as read only ... cannot copy change
- Attachments
-
- diff vault.GIF (16.22 KiB) Viewed 5734 times
-
SteveSchumacher
"Target readonly" issue not resolved
We removed the /r01 and /r02 arguments from both diff and merge tried that fix but it still reports the same error. Any further ideas? It is a trial version.dan wrote:By default, the diff tool brings up both files in a read-only state, so you can't apply changes from one file to the other. To change this, you would need to go to the Vault client Tools->Options->Diff/Merge, and take out the /ro1 and /ro2 arguments, which make the file read-only.
I'm stumped on this - can you re-verify that taking out the /ro(x) command flags actually happened correctly? Perhaps they were taken out, but the cancel button was accidently hit instead of OK?
Also, try invoking sgdm.exe from the command line with typed in paths to the files. Does it behave differently? In that case, it should respect the read-write status of the files.
Also, try invoking sgdm.exe from the command line with typed in paths to the files. Does it behave differently? In that case, it should respect the read-write status of the files.
-
Guest
The /RO options were removed correctly. SGDM merges files on my local disk okay, but note that the 'target is readonly' comes up only when you are merging against the current state of the repository. I am just getting up to speed on Vault and just realized that it still works reasonably even with the readonly target because we are diffing against the current repository contents which would logically be readonly and changeable only via a checkin. The diff/merge when you do it against the current state of the repository basically allows you to get differences in the repository and merge them down into your local copy which you can then check in. One thing I notice with the Trial version -- or maybe the way our installed Vault server is configured -- is that I appear to be stuck in the VSS checkin/checkout mode, so that may be why you cannot merge up to the current repository contents like you would with CVS. Is that correct?
Yes, that would make sense - in those cases, the local file would be read-only, and therefore the diff tool would not allow you to overwrite it.
You can change the options in Tools->Options to not require a checkout before a checkin, and to get files with a read-write status, so they can be immediately written to, and Vault will put them in the pending change set as the files are edited.
You can change the options in Tools->Options to not require a checkout before a checkin, and to get files with a read-write status, so they can be immediately written to, and Vault will put them in the pending change set as the files are edited.
-
Guest
Is this is the Concurrent Development Style panel's "Require Checkout before Checkin" checkbox you are referring to?dan wrote:You can change the options in Tools->Options to not require a checkout before a checkin,
Is this is the Concurrent Development Style panel's "Make Writeable" dropdown list you are referring to?dan wrote:and to get files with a read-write status, so they can be immediately written to, and Vault will put them in the pending change set as the files are edited.
