'bzr add --verbose' quietly ignores subdirs with their own .bzr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Jelmer Vernooij |
Bug Description
If you have a bzr tree within a bzr tree, 'bzr add' from top level of
the outermost tree will silently ignore the innermost tree. Even 'bzr
add --verbose' won't give any indication why the directory is being
ignored. If you're not the person who created this setup, it can be
very confusing.
$ mkdir foo; touch foo/{bar,baz}; cd foo
$ bzr init; bzr add; bzr commit -m "lol"
added bar
added baz
Committing to: /home/james/
added bar
added baz
Committed revision 1.
$ mkdir lala; cd lala; touch what ever
$ bzr init; bzr add; bzr commit -m "olo"
added ever
added what
Committing to: /home/james/
added ever
added what
Committed revision 1.
$ cd ..
$ bzr st
unknown:
lala
$ bzr add
$ bzr st
unknown:
lala
$ bzr add --verbose
$ bzr st
unknown:
lala
$
Related branches
- Vincent Ladeuil: Approve
- John A Meinel: Needs Information
-
Diff: 72 lines (+22/-3)3 files modifiedbzrlib/mutabletree.py (+3/-2)
bzrlib/tests/per_workingtree/test_smart_add.py (+16/-1)
doc/en/release-notes/bzr-2.5.txt (+3/-0)
Changed in bzr: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: add confusing-ui |
tags: | added: nested-trees |
Changed in bzr: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Confirmed → In Progress |
Changed in bzr: | |
status: | In Progress → Fix Released |
milestone: | none → 2.5b1 |
This also happens for dirs that contians a ".svn" dir, see stackoverflow. com/questions/ 2113112/ bzr-add- but-dirs- remain- unknown/
http://
Solution for me was to remove the .svn dirs and then the dirs could be bzr added.
I'm on Bazaar 2.0.3