bugGNU arch -- a revision control system - Bugs: bug #5251, |tla undo -o mychanges| barfs badly

 
 

bug #5251: |tla undo -o mychanges| barfs badly

Submitter:  Ben Bucksch <benb>
Submitted:  Fri 12 Sep 2003 11:25:33 PM UTC
   
 
Category:  tla Severity:  3 - Normal
Item Group:  bug Status:  None
Privacy:  Public Open/Closed:  Open
Release:  1.1pre5
Fixed Release: 
Merge Request?:  None
Your Archive Name: 
Your Archive Location: 
Assigned to:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 03 May 2008 09:47:52 AM UTC, comment #3: 

It's probably irrelevant to the fix, but the changed (not added) files seem to be untouched in the working dir. xenical, levitra,
clomid, buy viagra

Anonymous
Wed 24 Sep 2003 05:45:07 PM UTC, comment #2: 

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.

Samuel Tardieu <tardieu>
Fri 12 Sep 2003 11:31:16 PM UTC, comment #1: 

It's probably irrelevant to the fix, but the changed (not added) files seem to be untouched in the working dir.

Ben Bucksch <benb>
Fri 12 Sep 2003 11:25:33 PM UTC, 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.

Ben Bucksch <benb>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

No changes have been made to this item

Back to the top

Powered by Savane 3.13-02a9.
Corresponding source code