Exception trying to use bzr fast-import on an .fi created by bzr-fast-export-from-hg

[Jan Hülsbergen]

I'm using bzr 2.1.1-1 and bzr-fastimport 0.9.0~bzr261-1 both from the lucid repositories on amd64.

I did:

bzr fast-export-from-hg myproject myproject.fi
mv myproject myproject.hg
bzr fast-import myproject.fi myproject

and received the following output from the last command:

Creating destination repository ...
Shared repository with trees (format: 2a)
Location:
  shared repository: irclog
21:34:12 Collecting statistics ...
21:34:13 Starting import of 261 commits ...
ABORT: exception occurred processing commit :1
bzr: ERROR: exceptions.IndexError: list index out of range

If I can provide any additional information to help you solve this issue, please let me know.

[Jan Hülsbergen (jan-afoo)]

I just tried some more of my current mercurial repositories and I get the same error with all of them.

[Ian Clatworthy (ian-clatworthy)]

On 22/04/10 13:30, Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
>
> I'm using bzr 2.1.1-1 and bzr-fastimport 0.9.0~bzr261-1 both from the
> lucid repositories on amd64.

It looks like it's falling over quickly so I'm hoping the bug is
obvious. Can you try the trunk version of fastimport please? To grab this:

   bzr lp:bzr-fastimport ~/.bazaar/plugins/fastimport

Does the import still fail with that?

Ian C.

[Jan Hülsbergen (jan-afoo)]

I'm not at home on my lucid machine so I thought I'd give it a quick try on my karmic machine at work (using 2.1.1-1~bazaar2~karmic from the bzr ppa, repository was the same as with the first try on lucid) and I got a new/different bug this time:

15:01:00 Collecting statistics ...
15:01:01 Starting import of 261 commits ...
bzr: ERROR: exceptions.NotImplementedError: <bound method HgLocalRepository.all_revision_ids of HgLocalRepository('file:///home/jan/')>

A wild guess would be that this is an entirley differnt issue related to me using mercurial
1.5.1-0ppa1~karmic1 from the mercurial team's ppa and not the version that originally comes with karmic.

(On this karmic machine, I get the same error when using bzr-fastimport from the repos as well)

Should I report a new bug for this separate issue?

I'll try the bzr checkout of fastimport on my lucid machine this evening (CEST)

[Jan Hülsbergen (jan-afoo)]

Using the code from lp:bzr-fastimport indeed fixed the problem for me on lucid.

[CME Team1 (nmneira)]

Take me off list for bugs

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Jan Hülsbergen
Sent: Thursday, April 22, 2010 3:25 PM
To: <email address hidden>
Subject: [Bug 568049] Re: Exception trying to use bzr fast-import on an .fi created by bzr-fast-export-from-hg

Using the code from lp:bzr-fastimport indeed fixed the problem for me on
lucid.

--
Exception trying to use bzr fast-import on an .fi created by bzr-fast-export-from-hg
https://bugs.launchpad.net/bugs/568049
You received this bug notification because you are a member of Bzr-
fastimport, which is the registrant for Bazaar Fast Import.

Status in Bazaar Fast Import Plugin: New

Bug description:
I'm using bzr 2.1.1-1 and bzr-fastimport 0.9.0~bzr261-1 both from the lucid repositories on amd64.

I did:

bzr fast-export-from-hg myproject myproject.fi
mv myproject myproject.hg
bzr fast-import myproject.fi myproject

and received the following output from the last command:

Creating destination repository ...
Shared repository with trees (format: 2a)
Location:
  shared repository: irclog
21:34:12 Collecting statistics ...
21:34:13 Starting import of 261 commits ...
ABORT: exception occurred processing commit :1
bzr: ERROR: exceptions.IndexError: list index out of range

If I can provide any additional information to help you solve this issue, please let me know.

[a (tuomasjjrasanen)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 590367, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.