bzr lp-propose is broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
When trying to use bzr lp-propose, I get the following error:
bzr: ERROR: lazr.restfulcli
Response headers:
---
content-length: 97
content-type: text/plain
date: Fri, 04 Feb 2011 11:11:58 GMT
server: zope.server.http (HTTP)
status: 404
via: 1.1 wildcard.
x-lazr-oopsid: OOPS-1861A1008
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---
Object: <canonical.
---
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
reviews, staging, approve=approve)
File "/usr/lib/
self.launchpad = lp_api.
File "/usr/lib/
proxy_
File "/usr/lib/
timeout=
File "/usr/lib/
credentials, service_root, cache, timeout, proxy_info, version)
File "/usr/lib/
self._wadl = self._browser.
File "/usr/lib/
response, content = self._request(url, media_type=
File "/usr/lib/
raise HTTPError(response, content)
HTTPError: HTTP Error 404: Not Found
Response headers:
---
content-length: 97
content-type: text/plain
date: Fri, 04 Feb 2011 11:11:58 GMT
server: zope.server.http (HTTP)
status: 404
via: 1.1 wildcard.
x-lazr-oopsid: OOPS-1861A1008
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---
Object: <canonical.
---
bzr 2.2.3 on python 2.6.6 (Linux-
arguments: ['/usr/bin/bzr', 'lp-propose']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
bash_completion /usr/lib/
bzrcommitmessage /home/bjorn/
bzrtools /home/bjorn/
email /usr/lib/
launchpad /usr/lib/
lpreview /home/bjorn/
lsreview /home/bjorn/
netrc_
news_merge /usr/lib/
pipeline /home/bjorn/
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.