Patrick Quirk <p.qu...@smt.com> writes: >>>> Is the sqlite3 utility readily available on Windows? If it is then run: >>>> sqlite3 .svn/wc.db "select * from work_queue" >>> >>> Yep, here's the output: >>> 79|(file-install X/MONSTER.FMX/MONSTER.FMX.csproj 1 0 1 1) >>> 80|(file-install X/MONSTER.FMX/Boxes/gbFMXDisplay.resx 1 0 1 1) >>> 81|(file-install X/MONSTER.FMX/Boxes/gbFMXDisplay.Designer.cs 1 0 1 1) >>> 82|(file-install X/MONSTER.FMX/Boxes/gbFMXDisplay.cs 1 0 1 1) >>> >>> These are files that were new from the repo and were the last to show up >>> before the assertion appeared. >> >> So now we want to see the nodes row for each of those four paths: >> >> sqlite3 .svn/wc.db "select * from nodes where >> local_relpath='X/MONSTER.FMX/MONSTER.FMX.csproj'" >> sqlite3 .svn/wc.db "select * from nodes where >> local_relpath='X/MONSTER.FMX/Boxes/gbFMXDisplay.resx'" >> sqlite3 .svn/wc.db "select * from nodes where >> local_relpath='X/MONSTER.FMX/Boxes/gbFMXDisplay.Designer.cs'" >> sqlite3 .svn/wc.db "select * from nodes where >> local_relpath='X/MONSTER.FMX/Boxes/gbFMXDisplay.cs'" > > I've attached the output since it's a little unreadable in 80 column format.
Thanks! So each file has an op-depth=0, presence=normal line that has a checksum. Can you verify that each checksum exists in pristine: sqlite3 .svn/wc.db "select * from pristine where checksum ='$sha1$a6fb31cbea18a2f670e5d1387b2a1b118f831f09'" sqlite3 .svn/wc.db "select * from pristine where checksum ='$sha1$9addd651cd4260ee52b26cf5eae2d2bfe798aba5'" sqlite3 .svn/wc.db "select * from pristine where checksum ='$sha1$041ffe70415ce290a4f14a770d869e2eb3b420e8'" sqlite3 .svn/wc.db "select * from pristine where checksum ='$sha1$ea6871c7f57dd63e0a74ac0fd19435232322e5ff'" What I don't yet understand is why each file also has an op-depth=1, presence=base-deleted row. That seems to imply that 'X' is deleted in the working copy, so we should see two lines here: sqlite3 .svn/wc.db "select op_depth, presence from nodes where local_relpath='X'" -- Philip
