[Bug-gnu-arch] [bug #17626] tla update deletes directories and files

[Alan Grover]

URL:
  <http://savannah.gnu.org/bugs/?17626>

                 Summary: tla update deletes directories and files
                 Project: GNU arch -- a revision control system
            Submitted by: awgrover
            Submitted on: Wednesday 09/06/2006 at 13:37
                Category: tla
                Severity: 3 - Normal
              Item Group: bug
                  Status: None
                 Privacy: Public
             Open/Closed: Open
                 Release: 1.3.5 tla--atai--1.3--patch-72,
           Fixed Release: 
          Merge Request?: None
       Your Archive Name: 
   Your Archive Location: 
             Assigned to: None

    _______________________________________________________

Details:

"tla update" will delete directories (and files) if they have been added, but
not yet committed. Even worse, apparently a directory will be deleted if it
contains even one un-added file. A work-around is to use "tla star-merge" or
"tla replay."

Colin Fox gives this recipe:
1. Create a directory in an already arch-controlled tree
2. tla add the dir
3. Put a file in to the dir, without an arch-tag.
4. Do a "tla update", updating your tree from someone else's changes
5. tla actually DELETES the directory, rather than just moving it off to a
safe place. 
---
Matthieu Moy explains it as:
update does roughly

undo
replay (or apply-delta)
redo

You'd probably get the same behavior with

$ tla undo && tla redo

undo means compute the changeset, and apply it in reverse to the local tree.
The changeset will say "this directory has been added". So, the reversed
changeset will say "this directory has to be deleted". In this case, I
believe tla does "rm -fr" on the directory. 
---

See the short discussion at
http://www.nabble.com/TLA-Replay-nastiness-t522947.html

That discussion notes "That's a known issue (Aaron reported this a while
ago), but it seems that none of baz and tla fixed it." But, I did not find a
bug listed.







    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?17626>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/