bugmonotone - Bugs: bug #7220, [NEED TEST] Monotone handles...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #7220: [NEED TEST] Monotone handles deleted files very ungracefully

Submitted by:  Nathaniel Smith <njs>
Submitted on:  Tue 13 Jan 2004 10:32:22 AM UTC  
 
Category: working copySeverity: 3 - Normal
Item Group: crashStatus: None
Privacy: PublicAssigned to: Stephen Leake <stephen_leake>
Open/Closed: Closed
mtn version --full: 

Sat 08 May 2010 06:19:34 PM UTC, comment #4:

since it is not a problem with 0.47, we can just close it.

Stephen Leake <stephen_leake>
Project MemberIn charge of this item.
Tue 27 Apr 2010 01:16:44 PM UTC, comment #3:

This seems to behave as it should in 0.47:

(motoko ~/test)$ rm -f foo
(motoko ~/test)$ mtn stat .
mtn: warning: missing file 'foo'
mtn: misuse: 1 missing items; use 'mtn ls missing' to view
mtn: misuse: To restore consistency, on each missing item run either
mtn: misuse: 'mtn drop ITEM' to remove it permanently, or
mtn: misuse: 'mtn revert ITEM' to restore it.
mtn: misuse: To handle all at once, simply use
mtn: misuse: 'mtn drop --missing' or

And dropping a file that was previously deleted is also handled nicely.

Jack Lloyd <randombit>
Project Member
Mon 21 Feb 2005 11:47:43 PM UTC, comment #2:

This bug needs a (possibly XFAILed) test written.

Nathaniel Smith <njs>
Project Member
Tue 13 Jan 2004 11:12:37 AM UTC, comment #1:

An especially rude form of this is:
$ monotone add foo
$ monotone commit 'blah'
$ rm -f foo
$ monotone drop foo
<crashes>

Nathaniel Smith <njs>
Project Member
Tue 13 Jan 2004 10:32:22 AM UTC, original submission:

$ mkdir test
$ cd test
$ echo foo > foo
$ monotone db init --db=test.db
$ monotone --db=test.db add foo
monotone: adding foo to working copy add set
$ monotone status
Old manifest: da39a3ee5e6b4b0d3255bfef95601890afd80709
New manifest: e61621c74656cb80da9680bf6f9cdc7b15ec0085
Summary of changes:
add foo as f1d2d2f924e986ac86fdf7b36c94bcdf32beec15
$ rm -f foo
$ monotone status
<debug log>

      • Error: std::exception: FileStore: error opening file for reading: foo
        • error return code 205
                    • errors detected; see standard output for details ***********

diff gives the same error (as does commit and probably some other commands, but there it's at least somewhat defensible.)

That foo is only added in the working copy is irrelevant; the same problem occurs if one inserts a "monotone commit" before deleting foo.

Nathaniel Smith <njs>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by stephen_leake (Posted a comment)
  • -unavailable- added by randombit (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 10 May 2010 11:02:37 AM UTCstephen_leakeOpen/ClosedIn Test=>Closed
    Sat 08 May 2010 06:19:34 PM UTCstephen_leakeAssigned toNone=>stephen_leake
      Open/ClosedOpen=>In Test
    Mon 21 Feb 2005 11:47:43 PM UTCnjsSummaryMonotone handles deleted files very ungracefully=>[NEED TEST] Monotone handles deleted files very ungracefully

    Back to the top


    Powered by Savane 3.1-cleanup1