[Bug-gnu-arch] [bug #5251] |tla undo -o mychanges| barfs badly

[nobody]

=================== BUG #5251: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5251&group_id=4899

Changes by: Samuel Tardieu <address@hidden>
Date: mer 24.09.2003 à 17:45 (GMT)

------------------ Additional Follow-up Comments ----------------------------
It looks like the bug occurs when "mychanges" (as in

"tla undo -o mychanges") is located in the working directory

itself, as tla will try to "undo" it.



A proper solution would be to use a temporary name in any

case, then move the result in the proper place.



=================== BUG #5251: FULL BUG SNAPSHOT ===================


Signalé par: benb                     Projet: GNU arch -- a revision control 
system
Signalé le: ven 12.09.2003 à 23:25
Category:  tla                        Severity:  5 - Major                  
Bug Group:  bug                       Resolution:  None                     
Status:  Open                         Release:  1.1pre5                     
Fixed Release:                        Merge Request?:  None                 
Your Archive Name:                    Your Archive Location:                
Assigned to:  None                    

Summary:  |tla undo -o mychanges| barfs badly

Original Submission:  Reproduction:

1. cd into your working tree

2. Make changes to your source. Change files and add files.

3. tla undo -o mychanges (really "mychanges", not ",,mychanges")



Expected result:

Clean working tree (as in archive), plus a changeset dir called "mychanges"



Actual result:

Seems like tla undo records mychanges as "change/addition" of the working dir 
and in the end decides to delete it. Duh.



Symptoms:

- tla barfs with

Error calling `vu_stat' for 
"/path/to/working/tree/mychanges/patches/./path/to/changed.file.patch" (No such 
file or directory)

- Your added files have already been deleted.

- There is no "mychanges" dir

- There are 2 dirs, called ,,tmp-*. One of them contains lots of numerical 
dirs. The dir "0" contained the changeset (complete, it seemed), at least in my 
case. So, it seems that no data was actually lost, just hard to find.

Follow-up Comments
*******************

-------------------------------------------------------
Date: mer 24.09.2003 à 17:45        By: tardieu
It looks like the bug occurs when "mychanges" (as in

"tla undo -o mychanges") is located in the working directory

itself, as tla will try to "undo" it.



A proper solution would be to use a temporary name in any

case, then move the result in the proper place.

-------------------------------------------------------
Date: ven 12.09.2003 à 23:31        By: benb
It's probably irrelevant to the fix, but the changed (not added) files seem to 
be untouched in the working dir.


La liste CC est vide


Il n'y a aucun fichier attaché actuellement


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5251&group_id=4899

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