bzr mv --auto unversions old directory that still has other files in it

Bug #924245 reported by James Troup
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

| james@ornery:/tmp$ rm -fr wtf; mkdir wtf; cd wtf; bzr init
| Created a standalone tree (format: 2a)
| james@ornery:/tmp/wtf$ mkdir dir1; for i in foo bar baz bat; do echo ${i} > dir1/${i}; done; bzr add; bzr ci -m ""
| adding dir1
| adding dir1/bar
| adding dir1/bat
| adding dir1/baz
| adding dir1/foo
| Committing to: /tmp/wtf/
| added dir1
| added dir1/bar
| added dir1/bat
| added dir1/baz
| added dir1/foo
| Committed revision 1.
| james@ornery:/tmp/wtf$ mkdir dir2; mv dir1/b* dir2/; bzr mv --auto
| dir1 => dir2
| james@ornery:/tmp/wtf$ bzr st
| removed:
| dir1/foo
| renamed:
| dir1/ => dir2/
| unknown:
| dir1/
| james@ornery:/tmp/wtf$ ls -l dir2/
| total 12
| -rw-rw-r-- 1 james james 4 Jan 31 19:22 bar
| -rw-rw-r-- 1 james james 4 Jan 31 19:22 bat
| -rw-rw-r-- 1 james james 4 Jan 31 19:22 baz
| james@ornery:/tmp/wtf$ ls -l dir1/
| total 4
| -rw-rw-r-- 1 james james 4 Jan 31 19:22 foo
| james@ornery:/tmp/wtf$

If I move 'foo' instead of 'b*', the same thing happens. AFAICT any
move of a file from one directory to another will cause 'bzr mv
--auto' to incorrectly unversion the old directory and it's contents.

Martin Packman (gz)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.