dt commit weirdness with local issues

[Jose M. Moya]

dt commit renames the local issues before being sure that those ids
can be actually used.
If someone has added a new issue to the db, a commit of my local
issues without a previous update leaves my working copy in a very bad
state.

test case:

rm -rf /tmp/TEST
svnadmin create /tmp/TEST
dt-createdb file:///tmp/TEST issues wrk
svn add wrk/issues/format
whoami >> wrk/issues/etc/users
svn -m "created test issues db" commit wrk/issues
svn co file:///tmp/TEST wrk2
dt -d wrk/issues new
dt -d wrk2/issues new -n
dt -d wrk2/issues commit

after runing this test case, the issue database seems to be broken:

$ dt -d wrk2/issues update
svn: Failed to add directory 'data/i1': object of the same name already exists
Database update failed: 'svn update' didn't succeed

$ svn up wrk2/issues
svn: Failed to add directory 'wrk2/issues/data/i1': object of the same
name already exists

any clue?
regards,
josem

[Ivan Glushkov]

Hi.

Sorry for the so long reply, we have some sort of summer holidays now.
Yes, this is a bug, i've opened i#206 for this issue.
Thanks!

Ivan.

Post by Jose M. Moya
dt commit renames the local issues before being sure that those ids
can be actually used.
If someone has added a new issue to the db, a commit of my local
issues without a previous update leaves my working copy in a very bad
state.
rm -rf /tmp/TEST
svnadmin create /tmp/TEST
dt-createdb file:///tmp/TEST issues wrk
svn add wrk/issues/format
whoami >> wrk/issues/etc/users
svn -m "created test issues db" commit wrk/issues
svn co file:///tmp/TEST wrk2
dt -d wrk/issues new
dt -d wrk2/issues new -n
dt -d wrk2/issues commit
$ dt -d wrk2/issues update
svn: Failed to add directory 'data/i1': object of the same name already exists
Database update failed: 'svn update' didn't succeed
$ svn up wrk2/issues
svn: Failed to add directory 'wrk2/issues/data/i1': object of the same
name already exists
any clue?
regards,
josem
_______________________________________________
Dev mailing list
http://lists.ditrack.org/mailman/listinfo/dev

[Vlad Skvortsov]

Post by Ivan Glushkov
Hi.
Sorry for the so long reply, we have some sort of summer holidays now.
Yes, this is a bug, i've opened i#206 for this issue.
Thanks!

Yes, this is a known issue -- i#16; in fact, it's one of a "mustfix"
issues for DITrack 1.0. Unfortunately it's not that easy to fix properly
and we'll get to that only after 0.9 is released.

Thanks for the testcase, Jose!

Post by Ivan Glushkov
Ivan.

Post by Jose M. Moya
dt commit renames the local issues before being sure that those ids
can be actually used.
If someone has added a new issue to the db, a commit of my local
issues without a previous update leaves my working copy in a very bad
state.
rm -rf /tmp/TEST
svnadmin create /tmp/TEST
dt-createdb file:///tmp/TEST issues wrk
svn add wrk/issues/format
whoami >> wrk/issues/etc/users
svn -m "created test issues db" commit wrk/issues
svn co file:///tmp/TEST wrk2
dt -d wrk/issues new
dt -d wrk2/issues new -n
dt -d wrk2/issues commit
$ dt -d wrk2/issues update
svn: Failed to add directory 'data/i1': object of the same name already exists
Database update failed: 'svn update' didn't succeed
$ svn up wrk2/issues
svn: Failed to add directory 'wrk2/issues/data/i1': object of the same
name already exists
any clue?
regards,
josem
_______________________________________________
Dev mailing list
http://lists.ditrack.org/mailman/listinfo/dev

_______________________________________________
Dev mailing list
http://lists.ditrack.org/mailman/listinfo/dev