"Invalid url supplied to transport" error message for lightweight checkout

[Andrew Johnson]

A colleague tells me is getting the following error message every time he brings up Bazaar Explorer in a bzr checkout of lp:epics-base although it doesn't affect his subsequent ability to use the tool:

Invalid url supplied to transport: "file:///home/phoebus3/ANJ/epics/base/export/base.bzr/trunk/": Win32 file urls start with file:///x:/, where x is a valid drive letter

The error message is correct in what it says, but that url is actually the original parent branch of the lp:epics-base branch and I don't think it has any relevance to the actual checkout area on his machine. You can see where it's coming from with a "bzr info lp:epics-base" command. I would be quite happy to change (delete) the information about the parent branch if I could find out how to do that on an lp branch, but I suspect that Explorer shouldn't be doing this check on the lp repo's parent anyhow.

Since this is a checkout and not a branch, the Settings --> Configuration --> Branch Configuration option is grayed out so he can't use this to clear the problem.

Converted from Question #105650 to a bug on request from Ian Clatworthy.

[Alexander Belchenko (bialix)]

Please, show the output of `bzr info` in that checkout.

[Alexander Belchenko (bialix)]

Also I need the relevant part of .bzr.log related to this error.

[Alexander Belchenko (bialix)]

Or steps to reproduce.
Thank you.

[Andrew Johnson (anj)]

We worked around that problem quite a while back by converting his checkout to a branch, but if the bug is still present it should still be possible to reproduce it since the parent branch that it's complaining about still has the same parent branch URL:

tux% bzr info lp:epics-base
Repository branch (format: unnamed)
Location:
  shared repository: bzr+ssh://bazaar.launchpad.net/~epics-core/epics-base/3.14/
  repository branch: bzr+ssh://bazaar.launchpad.net/~epics-core/epics-base/3.14/

Related branches:
  parent branch: /home/phoebus3/ANJ/epics/base/export/base.bzr/trunk

I believe all he did was 'bzr checkout lp:epics-base' then use Bazaar Explorer (on Windows) to examine that working tree.

Note that other LP projects won't necessarily have the same kind of parent branch URL, so I think you will need to use lp:epics-base (which is about a 9MB working tree). I have not tried this myself though since I don't have a Windows box; if it does *not* reproduce the problem I will go back and ask him to try again.

Explorer probably shouldn't be trying to pass the parent branch's URL to the transport layer for a checkout anyway, since I believe it could be set to any URL that was valid on the machine that pushed the original branch to LP, but that URL won't necessarily be valid on the checkout machine as in this case.

[Alexander Belchenko (bialix)]

I'm able to get similar error when I'm creating lightweight checkout from lp:epics-base, e.g.:

C:\Temp>bzr checkout lp:epics-base --lightweight epics-base-co
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.

C:\Temp\epics-base-co>bzr explore .
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
Using parent branch file:///home/phoebus3/ANJ/epics/base/export/base.bzr/trunk/
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.

And then I see error message in left bottom box (there explorer tries to show missing revisions relative to parent branch).

Andrew, can you confirm that I have the same error as you reported? See screenshot.

[Alexander Belchenko (bialix)]

This behavior is harmless, though ugly.

[Andrew Johnson (anj)]

Yes, that's what he was getting. As you say this is harmless but ugly, especially for someone completely new to Bazaar as he was.