David Weintraub wrote:
> On Thu, May 28, 2009 at 8:00 PM, Nick Hasser <nick.hasser_at_gmail.com> wrote:
>> Tried that...no changes:
>>
>> mbp:branches nick$ pwd
>> /Users/nick/kofc/newsletter/branches
>> mbp:branches nick$ svn up
>> At revision 369.
>> mbp:branches nick$
>
> So, "svn st" nor "svn up" show any issues. Yet, you're getting that a
> branch you don't have in your Subversion working directory doesn't
> exist when you try a commit. Since all the files are under the 200906
> directory, can you switch to the 200906 directory and try your commit
> under there?
I tried that as well, with the same error about the file in 200905. In
fact, if I tried to commit anything under branches/ I got that error.
> I'm thinking that the .svn directory under the parent working
> directory contains a reference to the 200905 directory.
That may have been the case. A number of files were svn copied from the
200905 directory.
>
> Then again, why does Subversion fail when it is processing
> 200906/draft.pdf for commit and complaining about
> 200905/Newsletter.sla? Is there a property on 200906/draft.pdf that's
> referring to this particular file? You might get that with an
> svn:external, but that's only for directories and not individual
> files.
There shouldn't be any properties set there. I'm the only user of the
repo, and only have three directories with properties (all svn:external)
set, one of which is a higher level directory of these files, but
nothing this low in the directory structure.
> Maybe that's your best course of action: Check the properties on both
> 200906 and 200906/draft.pdf to see if there's anything on them.
I would guess that it's not 200906/draft.pdf, because the error always
indicated a problem committing the last file in the svn st listing,
which at times was before draft.pdf existed.
> I take it you're using the standard Subversion client. I also see this
> is on Mac OS X because of the .DS_Store file.
svn 1.6.2 installed via fink on 10.5.7.
> Otherwise, I really can't say what's going on.
>
I don't know exactly what fixed it, but the problem has disappeared. I
tagged the branches/200906 directory as tags/pk200906 with some
difficulty as I couldn't just svn mv or svn cp it. I ended up just
copying the 200906 directory to tags/pk200906, which wasn't the correct
way to do it as the URL for the tags/pk200906 directory was still under
the branches tree. Then I svn moved it to a temporary location under the
tags directory and then back to tags/pk200906, fixing the URL location.
After some work on the branches and branches/200906 directories, I
managed to get svn to allow me to delete the branches/200906 directory
(since it had been tagged). Once that commit was successful, I haven't
had errors committing the branches directory.
Thanks for all the suggestions!
Nick
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2357272
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-31 17:00:01 CEST