On 27/08/06, Ryan Schmidt <subversion-2006c@ryandesign.com> wrote:
>
> On Aug 27, 2006, at 16:40, mal content wrote:
>
> > Well, either I'm going completely senile or something has gone
> > seriously wrong with my repository:
>
> I don't see anything wrong with your *repository*. I see things wrong
> with your *working copy*.
>
> > $ ls branches/
> > redes2
>
> You have the entire branches directory checked out? Most people
> usually check out only the specific branch they're working on.
>
Not sure what you mean here. There are two branches in this
project, I only have the redes2 branch checked out here on this
machine (I am the only developer though).
>
> > $ svn status
> > ? branches/redes2
> > $ svn add branches/redes2
> > svn: warning: 'branches/redes2' is already under version control
> > $ svn status
> > ? branches/redes2
> >
> > So it's both under version control and not under version control?
>
> Only you know whether it is in fact under version control (which you
> can verify by using "svn ls" against the repository URL where it's
> supposed to be). It just looks like the .svn directory in the
> branches directory has been corrupted or removed. Check out a new
> working copy and avoid whatever behavior hosed the .svn directory.
Ah, making progress here. The redes2 branch is not listed in
the repository:
$ svn ls file:///source/cpj/branches/
redes3_0806/
Whether it ever was is another matter (I've not ruled out the possibility
that I have gone totally senile).
So it seems to be a matter of convincing the working copy that it really
isn't checked in, and then checking it in.
MC
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 28 05:41:42 2006