> On Mon, Aug 3, 2009 at 5:19 PM, michael <cs_at_networkingnewsletter.org.uk
> > wrote:
> Hi. I've confused myself. A while ago I believe I did a
> svn copy trunk branches/WP1a_cleanup
> (I don't think I did a REP->REP copy since there's nothing
> suggestive in
> the log)
> and now I'd editted some files, moved some, but when I try and
> commit I
> get an error that I can't work out what to do about or how to diagnose
> so your expert help would be highly appreciated. Ta, Michael
> svn commit -m 'partially completed WP1a - details to follow or see
> removing included files and adding replacement module files (eg
> svn: Commit failed (details follow):
> svn: Commit item
> branches/WP1a_cleanup/psstart.f' has copy flag but no copyfrom URL
> On 4 Aug 2009, at 01:29, David Weintraub wrote:
>> I found this in the archives. Hope it helps:
>> Quoth Rob Wilkerson:
>> > I'm trying to commit a few changes, but I keep getting this error
>> > Commit item 'path/to/a/directory' has copy flag but no copyfrom
>> > What does that mean and how can I get rid of it? If the icons are
>> > accurate then everything is exactly as I expect it to be. The
>> > exclamation point overlays only exist on the files that have been
>> > changed (and their ancestor directories, of course).
>> It sounds like the working copy metadata for 'path/to/a/directory'
>> gotten confused somehow.
>> Presumably this is a file that you've copied/moved from somewhere
>> If so, try this procedure:
>> 1. using regular Explorer (not SVN) make a copy of the file (as a
>> 2. SVN Revert the file; it should become unversioned. Delete it.
>> 3. Perform the SVN Copy again (if it was a move, you'll have to go to
>> the folder where it was moved from, pick Check For Modifications, and
>> revert the Delete using the context menu to get the original file
>> 4. with regular Explorer delete the newly created file and rename the
>> backup file to the same name.
>> This should fix up the metadata while retaining any local
>> you've made, if you follow it precisely.
>> Of course, this assumes that 'path/to/a/directory' really was a file,
>> not a folder. If it's a folder, then it becomes more complicated,
>> still has the same basic pattern.
> David Weintraub
That looks horrid. I think it's more than messing up a file since if I
look in .svn/entries most of the files have
but don't have a
entry. I'm guessing this is partly related to SVN's quick 'svn copy'
but maybe not?
If I do a clean
svn copy fromURL toNewDir
then I see still see this behaviour BUT editing a file then doing a
commit appears to work. Indeed copying all my mods from the previous
non-working dir to toNewDir and then commiting worked a treat
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-04 12:55:04 CEST