[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-gnu-arch] [bug #5251] |tla undo -o mychanges| barfs badly
From: |
nobody |
Subject: |
[Bug-gnu-arch] [bug #5251] |tla undo -o mychanges| barfs badly |
Date: |
Fri, 12 Sep 2003 19:25:33 -0400 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en; rv:1.4.1) Gecko/20030911 Beonex/0.9.0.0-stable |
=================== BUG #5251: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5251&group_id=4899
Submitted by: benb Project: GNU arch -- a revision control
system
Submitted on: Fri 09/12/2003 at 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.
No Followups Have Been Posted
CC list is empty
No files currently attached
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/