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

Re: Cleaning Up A Mess

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-06-05 03:16:27 CEST

On 6/4/07, Rich Shepard <rshepard@appl-ecosys.com> wrote:
> On Mon, 4 Jun 2007, Andy Levy wrote:
> > If svn st is a "new" command to you, I suggest you read further in your
> > book. It's a pretty important one to know & use.
> Andy,
> Had not needed it before with the one project. That's worked just fine
> since I set up the repository and installed that project in it.
> > For whatever reason, your WC thinks that schema.sql isn't in the
> > repository. If svn add schema.sql doesn't let you add it, something's
> > seriously hosed. What do you get when you try it?
> It tells me that it already exists and cannot be added:
> [rshepard@salmo /data1/permitwatch]$ svn add schema.sql
> A schema.sql
> [rshepard@salmo /data1/permitwatch]$ svn update
> svn: Failed to add file 'schema.sql': object of the same name already exists
> Yes, it is seriously hosed. That's why I ask for help.

Is it possible that you had a version of the WC, created your own
schema.sql in it, then updated?

The repository clearly thinks that there's already a schema.sql that
should be there. What if you rename the one you have (not via svn,
just mv schema.sql myschema.sql) and then update?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 5 03:16:51 2007

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.