> I am the Point of Contact for TortoiseSVN problems in my group at my work
> site. I have one group who is experiencing problems in two different areas.
> Here is what I gathered from their descriptions of the problems.
> The first problem they are having is that they have a section of code that
> they do not want in the repository (the "bin" folder of a java program to be
> exact). When they were handed the project, certain folders (classes, bin,
> etc.) were already stored in the repository. They were able to remove all of
> the folders except for bin from the repository. They say that they did a
> "TortoiseSVN -> Delete" and committed the delete. They said that the committ
> dialog box said that the delete had been successful. However, when they did
> an Update. The bin folder was put back into their working copy by the
> repository. Is there any way that this folder can be perminently removed
> from the repository? What would cause this particular problem to happen?
* The bin folder, is it still versioned when you update?
* is the bin folder also visible in the repository browser?
> The second issue stems from the combination of locks, updates and clean up.
> They told me that sometimes when they update code, a message pops up saying
> that the update failed because of a lock and that they need to do a clean
> up. Then the clean up may fail, also because of a locked file. What is going
> on here? How can this be fixed?
This happens if a file is opened in another application. Subversion then
can't update that file.
Unfortunately, after such a failed update a 'cleanup' doesn't work as
well as one would expect. If the cleanup doesn't work, you'd have to
delete (not TSVN->delete, but a normal delete) the folder where the
locked file is in, then update again - that will restore the folder.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-10-21 20:37:47 CEST