[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tricky problem revisited..

From: Rick Moore <ricmoore_at_sonalysts.com>
Date: 2004-09-01 15:04:35 CEST

On 31 Aug 2004 at 17:29, Michael Boeni wrote:

> Hello users,
>
> I have followed the advice given but have not been able to resolve the
> problem:
>
> 1. I removed the dynamically created dirs from the repository
> 2. I marked the directory 'classes' with the ingore flag
>
> Still, when I want to commit the parent directory, I get an error
> stating that ...'classes' is not locket...
>
> What is wrong here?

I'm going to guess: you have a directory above the classes directory
with a (hidden on Windows) directory called .svn. In that .svn
folder are files with entries indicating that the classes folder
should be "locked", but it's not because it's no longer in the
repository. Have you tried checking out the project from the
repository into a completely different/new location, then make a
trivial change (so you'll have something to check in), build
(generate the classes hierarchy), tell set svn:ignore on classes &
then commit? If that works, then you could check in any actual
changes you've made from your parent directory, then start over with
a new working copy (i'e', delete the workiing copy folder & check the
project out again).

Hope this helps.

>
> --
> Best regards,
> Michael mailto:mbo@shift-think.net
>
>

--
Rick
Sufficiently advanced political correctness is indistinguishable
from irony.
  -- Erik Naggum
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 1 15:05:17 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.