From: "Peter A. Bigot" <pab@pabigot.com>
To: Khem Raj <raj.khem@gmail.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: patchwork client problems
Date: Sat, 06 Sep 2014 05:41:36 -0500 [thread overview]
Message-ID: <540AE4E0.3080209@pabigot.com> (raw)
In-Reply-To: <CAMKF1spYXbaKdjQhAYM3SEL8RjqfTeOwmXpsOXNOS0YaXZJzLg@mail.gmail.com>
On 09/06/2014 05:03 AM, Khem Raj wrote:
> On Fri, Sep 5, 2014 at 7:40 AM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> On Friday, September 5, 2014, Burton, Ross <ross.burton@intel.com> wrote:
>>> On 4 August 2014 21:16, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>>>> 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
>>>> I have same error; I am adding Khem who I know has access to the
>>>> server and can know more about it.
>>> Khem - have you been able to look at this? I was hoping to use
>>> patchwork to merge patches from the list but obviously this is a bit
>>> of a blocker.
>>
>> Ok I haven't but over this weekend I can try
> This issue should be fixed now. Please download pwclient from
> http://patchwork.openembedded.org/pwclient/
> once again and, it should update your .pwclientrc but there may be
> gotchas so make sure it is of this form
Thanks. The new version works for me. Note that you need to add (e.g.)
-p oe-core to some commands to select the non-default project, and that
the username and password can also be placed in the project sections of
.pwclientrc to allow for different login information for different servers.
Peter
>
> [options]
> default = oe
>
> username: <yyyy>
> password: <xxxx>
>
> [glibc]
> url = http://patchwork.sourceware.org/xmlrpc/
>
> [oe]
> url = http://patchwork.openembedded.org/xmlrpc/
next prev parent reply other threads:[~2014-09-06 10:41 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
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 [this message]
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=540AE4E0.3080209@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox