Solved Subversion/TortoiseSVN help

[Golden]

Do we have any Subversion and/or TortoiseSVN guru's onboard?

I have a few queries relating to file commits/updates to repositories using RepoBrowser ?

Thanks,
Golden

 

[Alejandro85]

Far from a guru, but I use it daily at work and know it reasonably well. What's the matter?

 

[Golden]

Thanks Alejandro. My query is related to replacing files already committed to a repository using RepoBrowser.

Using the TortoiseSVN interface from Windows Explorer, I can update an existing file into a checked-out repository by simply adding the file, then committing it. No problems with that at all.

However, if I try to do that using the SVN RepoBrowser, I get an error message. Unfortunately I'm not at work at the moment so can't recall the exact error message (when I'm back at work on Monday I'll screen capture the error message and post it here). I've had a look at the SVN help but couldn't find an answer to the issue.

In summary, committing new files via RepoBrowser is straightforward and not an issue, but updating existing files is the issue.

Thanks,
Golden

 

[Alejandro85]

I rarely use the repo-browser directly to do anything, but can't reproduce the problem, maybe the exact error message helps.

But anyway, I did a quick and dirty test. If I right-click => edit on the browser, it opens the file, and after saving I'm offered to commit, so far it works great. The rare behavior is that it doesn't uses the working copy, it downloads a brand new copy from the repository, edit that in a temp folder, and upload it back, the working copy is not affected in anything. So maybe it creates conflicts with it if you've edited it in both places.

I'm using TSVN 1.8.5, if that matters. It might be a bug with an older version too.
Found this in the change log, not sure if it matters:

Version 1.8.2
(....)
- BUG: Issue #528: Abort when editing
file from repo browser. (Stefan)

Maybe you're affected by this bug and just need to update?

 

[Golden]

I think thats it. Im using version 1.6.11.....unfortunately Im in a corporate environment where change is very slow. I'll have to see if it can be updated.