Re: svn_load_dirs.pl bug when specifying a tag that already exists, and other bugs that led to it

Ryan Schmidt wrote:
> I have used svn_load_dirs.pl for years now and have run into a minor but
> unfortunate problem which occurs if you specify a tag name that already
> exists in the repository. I ran it like this [1]:
>
> $ svn_load_dirs.pl -t 1.2.3 $REPO/vendor/foo current ./foo-1.2.3
>
> The problem arose because the tag 1.2.3 already existed in
> $REPO/vendor/foo. svn_load_dirs apparently does not check for this, and
> just executes its svn cp command anyway. The result was that the 1.2.3
> tag in the repository now contains a "current" directory with another
> copy of the code, which is not desired. The script should instead print
> an error message and exit if the specified tag already exists. A
> complete reproduction recipe is below [3].
>
> I could not see an issue in the issue tracker about this, and would like
> to report it.

Hi Ryan,

Yes, it would be good for the script to check for it.

If you put a patch together, I can review and shepherd it through and commit it.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org