On Fri, 2008-06-13 at 10:22 +0000, James Westby wrote: > On Mon, 2008-06-02 at 14:44 +0000, John A Meinel wrote: > > Did you try something like 'bzr status' to see if it notices the file is > > removed. Or maybe explicitly informing it via "bzr rm foo" ? > > > > Hi, > > I've just looked in to this a little more. > > The problem is running "rm foo" but not "bzr rm foo". "bzr st" then > shows the file as removed, but the WorkingTree inventory still has > the file. > > The current failure is calling _read_tree_state() with the path, which > is done from inside builddeb. I can fix this to check > tree.has_filename() first, which does an lstat. However, the code > fails then inside the export, as that assumes that if the tree lists > the file it should be present (as it only works on revision trees in > bzr). > > So, I have a few questions: > > 1. Should the WorkingTree list the file if it has been removed?
Yes. > 2. Should I change the export code to not assume a file is present? exporting a working tree should handle a missing file like commit does - that is to elide it from the output. -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>. -- export doesn't handle files going missing from working tree https://bugs.launchpad.net/bugs/174539 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
