Re: nested copies broken on trunk

Philip Martin writes: > Stefan Sperling writes: > >> + svn cp nested-copy/trunk/gamma nested-copy/trunk/gamma.copied >> A nested-copy/trunk/gamma.copied >> + svn mv nested-copy/trunk/gamma.copied/delta >> nested-copy/trunk/gamma.copied/delta.copied >> A nested-copy/trunk

Re: nested copies broken on trunk

Greg Stein writes: > the node functions are considered transient. It would be best to implement > something more direct against wc_db I'm not sure it's the right solution -- it might just be working round a bug. The problem only occurs when the deleted file is a direct child of a copied directo

Re: nested copies broken on trunk

the node functions are considered transient. It would be best to implement something more direct against wc_db On Jan 28, 2010 11:11 AM, "Philip Martin" wrote: Stefan Sperling writes: > + svn cp nested-copy/trunk/gamma nested-copy/trunk/gamm... workqueue.c:run_deletion_postcommit calls svn_wc_

Re: nested copies broken on trunk

Noorul Islam K M writes: > By any chance after this commit does the test case "reverse_merge_move" > in copy_test.py pass? $ ../../../../src/subversion/tests/cmdline/copy_tests.py 80 XPASS: copy_tests.py 80: reverse merge move It does, but I need to understand the base node behaviour better bef

Re: nested copies broken on trunk

Philip Martin writes: > workqueue.c:run_deletion_postcommit calls svn_wc__db_scan_base_repos > assuming that the deleted file has a base_node entry, but it doesn't > because it was copied. copy_tests.py 8 tests this and it passes. It turns out that it matters whether the deleted file is an imme

Re: nested copies broken on trunk

Stefan Sperling writes: > + svn cp nested-copy/trunk/gamma nested-copy/trunk/gamma.copied > A nested-copy/trunk/gamma.copied > + svn mv nested-copy/trunk/gamma.copied/delta > nested-copy/trunk/gamma.copied/delta.copied > A nested-copy/trunk/gamma.copied/delta.copied > D