From: "Peter A. Bigot" <pab@pabigot.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: patchwork client problems
Date: Fri, 01 Aug 2014 20:07:42 -0500 [thread overview]
Message-ID: <53DC39DE.5020105@pabigot.com> (raw)
In-Reply-To: <53C3A130.4000900@pabigot.com>
On 07/14/2014 04:21 AM, Peter A. Bigot wrote:
> I'm finding attempts to use pwclient on
> http://patches.openembedded.org/xmlrpc/ produce an ExpatError because
> the returned document is always empty (per a wireshark trace of the
> transaction). Can somebody confirm that the server for the
> command-line client is working properly? Thanks.
>
> Peter
>
I've downloaded a fresh copy of pwclient from
http://patches.openembedded.org/help/pwclient/
I've verified my .pwclientrc is exactly what the project info tells me
it should be:
[base]
url: http://patches.openembedded.org/xmlrpc/
project: oe-core
I've verified that pwclient works with other servers.
And I still get empty documents back from the OE patchwork server for
every pwclient command I try.
Anybody have any idea what's going wrong?
Thanks.
Peter
llc[40]$ /tmp/pwclient projects
Traceback (most recent call last):
File "/tmp/pwclient", line 500, in <module>
main()
File "/tmp/pwclient", line 439, in main
action_projects(rpc)
File "/tmp/pwclient", line 213, in action_projects
projects = rpc.project_list("", 0)
File "/usr/lib/python2.7/xmlrpclib.py", line 1224, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.7/xmlrpclib.py", line 1578, in __request
verbose=self.__verbose
File "/usr/lib/python2.7/xmlrpclib.py", line 1264, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib/python2.7/xmlrpclib.py", line 1297, in single_request
return self.parse_response(response)
File "/usr/lib/python2.7/xmlrpclib.py", line 1471, in parse_response
p.close()
File "/usr/lib/python2.7/xmlrpclib.py", line 560, in close
self._parser.Parse("", 1) # end of data
xml.parsers.expat.ExpatError: no element found: line 1, column 0
next prev parent reply other threads:[~2014-08-02 1:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:21 patchwork client problems Peter A. Bigot
2014-08-02 1:07 ` Peter A. Bigot [this message]
2014-08-04 20:16 ` Otavio Salvador
2014-08-07 9:52 ` Peter A. Bigot
2014-08-07 10:17 ` Martin Jansa
2014-09-05 14:31 ` Burton, Ross
2014-09-05 14:40 ` Khem Raj
2014-09-05 14:48 ` Burton, Ross
2014-09-06 10:03 ` Khem Raj
2014-09-06 10:41 ` Peter A. Bigot
2014-09-06 15:38 ` Khem Raj
2014-09-06 16:03 ` Peter A. Bigot
2014-09-06 17:23 ` Khem Raj
2014-09-06 13:32 ` Burton, Ross
2014-09-06 15:32 ` Khem Raj
2014-09-06 17:25 ` Khem Raj
2014-09-08 12:07 ` Burton, Ross
2014-09-08 12:35 ` Bernhard Reutner-Fischer
2014-09-08 16:52 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53DC39DE.5020105@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.