On Tue, Oct 21, 2008 at 11:25, raecarrow <amanda.r.carrow_at_lmco.com> wrote:
>
> 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?
Did they commit the deletion before performing the update?
> 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?
I just ran into this yesterday. Unfortunately, WC cleanups aren't
successful as frequently as one might hope. I just deleted (locally,
not SVN Delete) that subdirectory of my WC that got locked and into a
"can't clean up" state, and re-updated the parent to restore it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-21 17:29:35 CEST