lp-open not working in windows

[Vincent Ladeuil]

Bazaar 2.0.0, installed via bzr-2.0.0-2-setup.exe running on WinXP. Bundled Launchpad plugin is v2.0.0

'launchpad-open' appears not to work as expected. Referring to branches for well-known plugins results in " bzr: ERROR: <<target>> is not registered on Launchpad."

For example -
C:\Documents and Settings\David>bzr lp-open bzr-extmerge --dry-run
bzr: ERROR: bzr-extmerge is not registered on Launchpad.

C:\Documents and Settings\David>bzr lp-open bzr-explorer --dry-run
bzr: ERROR: bzr-explorer is not registered on Launchpad.

C:\Documents and Settings\David>bzr lp-open bzr.webdav --dry-run
bzr: ERROR: bzr.webdav is not registered on Launchpad.

Bug, or misunderstanding? Is it platform dependent?

Thanks -

DJ

[Vincent Ladeuil (vila)]

I suspect a proxy related problem, can you look at bug #186920 and confirm your problem is a duplicate ?

[David Roberts (smartgpx)]

Not a proxy problem as far as I am aware. Reproduced on 2 PCs with independent network connections with different ISPs. No browser proxy set. So I'm resisting 'duplicate' for now.

'bzr branch lp:<projectname>' succeeds for all 3 projects listed.

Here is a .bzr.log extract for the failure -

Mon 2009-10-12 15:30:07 +0100
0.032 bzr arguments: [u'lp-open', u'bzr-extmerge', u'--dry-run']
0.047 looking for plugins in C:/Documents and Settings/djr/Application Data/bazaar/2.0/plugins
0.047 looking for plugins in C:/localapp/Program Files/Bazaar/plugins
0.125 encoding stdout as sys.stdout encoding 'cp850'
0.172 Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 842, in exception_to_return_code
  File "bzrlib\commands.pyo", line 1037, in run_bzr
  File "bzrlib\commands.pyo", line 654, in run_argv_aliases
  File "\plugins\launchpad\__init__.py", line 194, in run
  File "\plugins\launchpad\__init__.py", line 189, in _get_web_url
NotLaunchpadBranch: bzr-extmerge is not registered on Launchpad.

[Vincent Ladeuil (vila)]

Hmm, just noticing that you don't specify the prefix !
You need to do:

   bzr lp-open lp:bzr-extmerge

[David Roberts (smartgpx)]

OK. Happy to write down to 'misunderstanding'. Tiny bit of user-interface duplication perhaps - if it's an 'lp-xxx' command, I assumed it was implicit that the branch was hosted on lp! [but that's not really the topic of this bug, and I accept the closure.]

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Roberts wrote:
> OK. Happy to write down to 'misunderstanding'. Tiny bit of user-
> interface duplication perhaps - if it's an 'lp-xxx' command, I assumed
> it was implicit that the branch was hosted on lp! [but that's not really
> the topic of this bug, and I accept the closure.]
>

You can also do "bzr lp-open ../my-branch" and it will lookup the public
location for your branch and open it's Launchpad page.

I actually use that rather often, since that is easier for me to type
(and my shell does auto-completion) versus doing:

  "bzr lp-open lp:~jameinel/$PROJECT/$BRANCH"

That said, it seems like it would be a reasonable fallback, that if "bzr
lp-open $FOO" does not find $FOO as a branch, it could try lp:$FOO.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrTV1cACgkQJdeBCYSNAAPs7wCgmYjWHpHBpH6cgIv/nRlMjgtA
Yl4AoLVOmXBMvbLnO+Xu1y2y5GqLtWtf
=tXG6
-----END PGP SIGNATURE-----