error about null revision not present pushing to server

Bug #317654 reported by Ross Light
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
High
Andrew Bennetts

Bug Description

With my 0.2 release branch of my progtools project (located at ~quartz25/progtools/release-0.2), I am unable to commit any new revisions. I deleted the branch and repushed it, but it continues to give me this error:

bzr: ERROR: Revision {set([('null:',)])} not present in "KnitVersionedFiles(_KnitGraphIndex(CombinedGraphIndex(GraphIndex('file:///home/ross/src/Python/Projects/progtools/.bzr/repository/indices/eb5b6af505e3e4e0aa5bf51290c94afa.iix'), GraphIndex('file:///home/ross/src/Python/Projects/progtools/.bzr/repository/indices/21098a6d85463cdd6ece4305f34b9479.iix'), GraphIndex('file:///home/ross/src/Python/Projects/progtools/.bzr/repository/indices/18a6c1f50eb47ba227fc7fc9a8a469b8.iix'), GraphIndex('file:///home/ross/src/Python/Projects/progtools/.bzr/repository/indices/1782561d38eac87b29fb8c135f3dddca.iix'), GraphIndex('file:///home/ross/src/Python/Projects/progtools/.bzr/repository/indices/107c4f625c5b89416f942dc32248aaed.iix'))), <bzrlib.knit._DirectPackAccess object at 0x885114c>)".

I am using bzr 1.10 with Python 2.5 on Ubuntu Intrepid. Running "bzr info -v" gets me this output:

***
Repository tree (format: 1.6)
Location:
  shared repository: /home/ross/src/Python/Projects/progtools
  repository branch: .

Related branches:
  push branch: bzr+ssh://bazaar.launchpad.net/%7Equartz25/progtools/release-0.2/

Format:
       control: Meta directory format 1
  working tree: Working tree format 4
        branch: Branch format 7
    repository: Packs 5 (adds stacking support, requires bzr 1.6)

In the working tree:
        12 unchanged
         0 modified
         0 added
         0 removed
         0 renamed
         0 unknown
         0 ignored
         1 versioned subdirectory

Branch history:
        19 revisions
         1 committer
        12 days old
   first revision: Fri 2008-12-05 16:12:33 -0800
  latest revision: Wed 2008-12-17 16:44:51 -0800

Repository:
        50 revisions
***

Revision history for this message
Ross Light (quartz25) wrote :

Here is the "bad" repository that I'm using.

description: updated
Revision history for this message
Martin Pool (mbp) wrote :

John and myself have hit this too recently, I think.

Changed in bzr:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Martin Pool (mbp) wrote :

lifeless: spiv: stacked branches shouldn't reach null: though
lifeless: spiv: perhaps, its *non* stacked new branches with old servers?
spiv: lifeless: I've got a reproduction with a non-stacked branch, current server
spiv: Possibly due to a non-lefthand null: parent in the history.
spiv: pushing bzr-svn -r100 reproduces it.
lifeless: that would make sense
spiv: If I add parents_of_found.discard(revision.NULL_REVISION) to _do_query in the searcher, it works.

Revision history for this message
Robert Collins (lifeless) wrote :

This is possibly bug 334666, but this dates from mid jan, whereas 334666 seems to have been a regression in bzr.dev; I'm not sure they are related. Lets fix 334666 which we have a definite root cause for then look at this.

Revision history for this message
Martin Pool (mbp) wrote :

I can reproduce the same error with bzr.1.10 against launchpad.

I'm not sure why this was not more widely seen before though.

Revision history for this message
Ivan Zorin (iaz) wrote :

If someone have clashed with this or similar bug, then take a look here:
https://bugs.launchpad.net/bzr/+bug/334666/comments/1
Maybe it will be useful for bzr users, and be helpful for bzr developers to find out where the problem exactly is.

Revision history for this message
Andrew Bennetts (spiv) wrote :

A fix that I believe should resolve this has been submitted to bzr.dev.

Changed in bzr:
assignee: nobody → spiv
status: Confirmed → Fix Committed
Vincent Ladeuil (vila)
Changed in bzr:
milestone: none → 1.13rc1
Revision history for this message
Andrew Bennetts (spiv) wrote :

This fix is now in bzr.dev, and it does seem to fix the problem.

Changed in bzr:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.