bzr ls --unknown isn't a very good detective

[Paul Hummer]

So, here's the process I went through to find this bug:

I merged trunk into my branch to resolve conflicts. It didn't remove a directory from the merge because it was not empty. I did bzr resolve <dir> because I just wanted it to go away. I then resolved the actual conflict. Then I tried to commit --strict (I have it aliased). It complained that there were unknown files in the tree. I then did "bzr status" and it scrolled a TON of files through, showing deletions, additions, changes, and unknowns. The unknown file was difficult to scan through with all those files (possible another bug). I complained about this to abentley. He told me to shut up and use "bzr ls --unknown" Upon doing this, I received no output (as if there were no unknowns). However, commit --strict still said there were no unknowns.

I suspect it's because of this part of the bzr status output:

-D lib/lp/registry/utilities/
? lib/lp/registry/utilities/

[Vincent Ladeuil (vila)]

Looks like a nice edge case ;)
Can you confirm that all the unknowns where below lib/lp/registry/utilities/ ?