Update: Re: bzr 0.6 commit problem: parent_id {blah} not in inventory

[John Arbash Meinel]

Andrew S. Townley wrote:
> In poking around the .bzr directory (and adding a print statement to
> inventory.py), it looks like in the inventory.weave file the parent_id
> on the file I moved is still set to the original parent (also, the hash
> and size are different than what it is now because I both changed it and
> moved it (are you not supposed to do that?).

Before you get too far, the inventory.weave file is for *committed*
revisions. So naturally it should still have the old value, because that
is the history.

> 
> My question now becomes, what happens if I hack the inventory.weave file
> to put in the correct values for the parent_id?  Will that fix it, or do
> I whack the .bzr directory and start over, losing my revision history? 

The one you have to worry about is .bzr/inventory (no .weave).
That is the file for the current working inventory.
But from what it sounds like, that file is already okay.

> This was a virginal 0.6 environment, so either:
> 
> a) you can't change and move without separate commits and/or
> b) you shouldn't move via relative paths

Both of these should work. What we need to figure out is what is the
actual state of your tree, and how do we get it out of that state.

> 
> Like I said, I'm looking for the lowest impact change (which, since I've
> only used bzr in this set of source for about 2 days worth of changes,
> wouldn't be that big of a loss, but I might wait for the next version
> before I try again. :)
> 
> I had been using 0.0.9 before and it seemed to give me less problems,
> but from only briefly skimming the list recently, I know there has been
> a lot of changes around the weave format, etc.  At the moment, I'm sorta
> stuck because I don't want to continue with the environment hosed.
> 
> Any/all suggestions welcome.

Can you meet on IRC? That is a faster turnaround than posting to the
mailing list and waiting for a reply.
#bzr or irc.freenode.net

In the meantime, can you go to the root directory, and just type:

bzr status

To see what it says. If it is happy, commit should be happy.

I'm wondering, are you trying to do a partial commit? Running something
like:
	bzr commit -m 'something' .
It might be that it is only grabbing half of the change, and missing the
rest.

John
=:->

> 
> Cheers,
> 
> ast
> 
> On Wed, 2005-11-02 at 16:44, Andrew S. Townley wrote:
> 
>>Hi folks,
>>
>>I've been working with bzr a bit now in "tentative" mode to see what it
>>was like.  It seemed reasonable enough, so I threw some real source code
>>at it to see what would happen.
>>
>>I'm trying to check in some changes where I wanted to remove one file,
>>move a file up a level and just generally do normal stuff.  Now, I'm
>>stuck with the following error:
>>
>>bzr: ERROR: parent_id {filter-20051030191347-68f7b855b693fa3d} not in
>>inventory
>>
>>Now, having googled this a bit, John asked someone if the offending
>>entry was in the .bzr/inventory file, so, yes, it is; on line 96:
>>
>>     96 <directory file_id="filter-20051030191347-68f7b855b693fa3d" name="filter" parent_id="mb-20051030191342-5b11a0b180ce3d5c" />
>>
>>Now, the filter directory used to have a file FilterContext.java in it,
>>which I moved using the following command:
>>
>>$ bzr mv filter/FilterContext.java .
>>src/java/blah/mb/filter/FilterContext.java => src/java/blah/mb/FilterContext.java
>>
>>So far, so good.  Check the status:
>>$ bzr status .
>>renamed:
>>  src/java/blah/mb/filter/FilterContext.java => src/java/blah/mb/FilterContext.java
>>modified:
>>  src/java/blah/mb/File1.java
>>unknown:
>>  src/java/blah/File2.java
>>
>>Then I went to check in the changes to File1.java using 'bzr commit -m
>>'comment' File1.java' and it went boom.  Based on typing this bug
>>report, I suspect it has something to do with my use of '.' in the bzr
>>mv command.
>>
>>My biggest problem now is that I'm not sure how to get out of this
>>state.  Any ideas?
>>
>>Cheers,
>>
>>ast
>>
>>***************************************************************************************************
>>The information in this email is confidential and may be legally privileged.  Access to this email by anyone other than the intended addressee is unauthorized.  If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful.  If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
>>***************************************************************************************************
>>
> 
> 
> ***************************************************************************************************
> The information in this email is confidential and may be legally privileged.  Access to this email by anyone other than the intended addressee is unauthorized.  If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful.  If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
> ***************************************************************************************************
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051102/b4c63caa/attachment.pgp