Comment 7 for bug 831313

Dear Stefano,

First of all, the earlier mentioned line where I change the if statement, should be line 316, not 318. At 318 the command line spits out the error, since 'bundlename' is empty.

I've made a storyboard/walkthrough in console to reproduce this. All information should be there, maybe you could reproduce it like this as well. I think the bugreporter & me only encounter this problem, when we try to do a local transplant. (as source)

Quick index of what I do:
- dpkg -l | grep mercurial
  List the mercurial packages, which are not installed

- apt-cache showpkg mercurial mercurial-common
  List mercurial packages available + origin & MD5. In advance, the come from oneiric universe, 1.9.1-1

- apt-get install mercurial mercurial-common
  Install mercurial

- dpkg -l|grep mercurial
  Show current install (status)

- mkdir tmp && cd tmp && hg clone ../Sources/Project && cd Project
  Create tmp folder, and clone another locally available repository, change dir to cloned repository

- sed -n '316p' /usr/lib/python2.7/dist-packages/mercurial/bundlerepo.py
  print the line of if statement

- hg transplant -s ../../Sources/Project 6cb94353bc49
  Transplant a change and show bundlerepo.py error

- sudo vim /usr/lib/python2.7/dist-packages/mercurial/bundlerepo.py
  Edit bundlerepo & edit line 316 where I add the earlier mentioned 'and bundlename'

- sed -n '316p' /usr/lib/python2.7/dist-packages/mercurial/bundlerepo.py
  Double check

- hg transplant -s ../../Sources/Project 6cb94353bc49
  Transplant that went pretty fine. Though I have merge conflicts, the mercurial transplant itself behaved like it should.

Hope this narrowed down the report and makes it easier to confirm & fix.

Cheers,

Gideon