>No, he meant your working copy is corrupted and you need to check out >another. The working copy upgrade process cannot handle certain types >of working copy corruption.
I tried it, I checked out my project again (several gigabytes!) and I encountered problems again. A colleague did the same migration but his project doesn't have externals while mine has tons of 'em. I think there may be an issue with the updating of directories from 1.6.x to 1.7.1 especially in the handling of the externals references. Anyway I went back to 1.6.x and everything's fine for me. -- View this message in context: http://old.nabble.com/workqueue.c-line-672%3A-assertion-failed-%28checksum-%21%3DNULL%29-tp32690129p32875469.html Sent from the Subversion Users mailing list archive at Nabble.com.
