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

Committing .svn dirs and your're toast?

From: Roland Besserer <roland_at_motorola.com>
Date: 2004-12-07 23:15:15 CET

I'm in the processing of fixing an svn database because a large
commit was mistakenly based on an earlier, modified svn checkout
located in a new directory. Because it was based on an earlier
svn checkout, the directory tree had all the original .svn directories
still in place. The .svn directories were not filtered out during
the commit and ended up in the repository.

Any attempts at checking out the new tree now aborts as soon as
svn encounters the first .svn directory in the repository and
refuses - naturally - to overwrite the .svn it created as part if the
'svn checkout' command.

I'm fixing this by removing the entire check-in via the svnadmin dump,
svndumpfilter, svnadmin load sequence. Tedious and pretty slow.

Doesn't this qualify as a bug? An svn commit should not allow reserved
file names (like .svn) to be committed to the repository.

What's the best way to prevent this from happening in the future?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 7 23:17:34 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.