patchwork client problems

patchwork client problems

[Peter A. Bigot]

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

Re: patchwork client problems

[Peter A. Bigot]

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

Re: patchwork client problems

[Otavio Salvador]

On Fri, Aug 1, 2014 at 10:07 PM, Peter A. Bigot <pab@pabigot.com> wrote:
> 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

I have same error; I am adding Khem who I know has access to the
server and can know more about it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: patchwork client problems

[Peter A. Bigot]

On 08/04/2014 03:16 PM, Otavio Salvador wrote:
> On Fri, Aug 1, 2014 at 10:07 PM, Peter A. Bigot <pab@pabigot.com> wrote:
>> 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
> I have same error; I am adding Khem who I know has access to the
> server and can know more about it.

Thanks for confirming this isn't just me.

It's a bit of a problem, since without a working pwclient I can't tell 
if there's already a patch that does what I need.  If there's a way to 
search through the browser interface I haven't figured it out.

Khem, if I can help with diagnosis please let me know.

Peter

Re: patchwork client problems

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 2806 bytes --]

On Thu, Aug 07, 2014 at 04:52:23AM -0500, Peter A. Bigot wrote:
> On 08/04/2014 03:16 PM, Otavio Salvador wrote:
> > On Fri, Aug 1, 2014 at 10:07 PM, Peter A. Bigot <pab@pabigot.com> wrote:
> >> 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
> > I have same error; I am adding Khem who I know has access to the
> > server and can know more about it.
> 
> Thanks for confirming this isn't just me.
> 
> It's a bit of a problem, since without a working pwclient I can't tell 
> if there's already a patch that does what I need.  If there's a way to 
> search through the browser interface I haven't figured it out.

Click on "Filter" link in top left corner of the table.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

Re: patchwork client problems

[Burton, Ross]

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.

Cheers,
Ross

Re: patchwork client problems

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

On Friday, September 5, 2014, Burton, Ross <ross.burton@intel.com> wrote:

> On 4 August 2014 21:16, Otavio Salvador <otavio@ossystems.com.br
> <javascript:;>> 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

>
> Cheers,
> Ross
>

[-- Attachment #2: Type: text/html, Size: 2674 bytes --]

Re: patchwork client problems

[Burton, Ross]

On 5 September 2014 15:40, Khem Raj <raj.khem@gmail.com> wrote:
> Ok I haven't but over this weekend I can try

Thanks Khem, much appreciated.

Ross

Re: patchwork client problems

[Khem Raj]

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

[options]
default = oe

username: <yyyy>
password: <xxxx>

[glibc]
url = http://patchwork.sourceware.org/xmlrpc/

[oe]
url = http://patchwork.openembedded.org/xmlrpc/

Re: patchwork client problems

[Peter A. Bigot]

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/

Re: patchwork client problems

[Burton, Ross]

On 6 September 2014 11:03, Khem Raj <raj.khem@gmail.com> wrote:
> 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 Khem, much appreciated.

Presumably the hooks to auto-mark merged patches haven't been
activated because the git server and the patchwork server are on
different machines. Has there been previous discussion to get this
resolved?

Ross

Re: patchwork client problems

[Khem Raj]

On Sat, Sep 6, 2014 at 6:32 AM, Burton, Ross <ross.burton@intel.com> wrote:
> Thanks Khem, much appreciated.
>
> Presumably the hooks to auto-mark merged patches haven't been
> activated because the git server and the patchwork server are on
> different machines. Has there been previous discussion to get this
> resolved?

it has been activated and was working in past. Do you see it not happening now ?

Re: patchwork client problems

[Khem Raj]

On Sat, Sep 6, 2014 at 3:41 AM, Peter A. Bigot <pab@pabigot.com> wrote:
> 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.
>

can you add a working .pwclientrc to wiki

http://www.openembedded.org/wiki/Patchwork

Re: patchwork client problems

[Peter A. Bigot]

On 09/06/2014 10:38 AM, Khem Raj wrote:
> On Sat, Sep 6, 2014 at 3:41 AM, Peter A. Bigot<pab@pabigot.com>  wrote:
>> 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.
>>
> can you add a working .pwclientrc to wiki
>
> http://www.openembedded.org/wiki/Patchwork

Apparently not. I don't have an account, and while trying to figure out 
how to request one got to a situation where I get 502 Bad Gateway on 
every request to www.openembedded.org.

The help output from pwclient and the comments in your example (and the 
ones downloaded from each project) cover it pretty well, though.  Just 
wanted to highlight to the current readership that the new version 
supports multiple projects in one config file. (Breaking the way I've 
been doing it for the last couple years which figured out the right 
default based on context, but hey, progress, right?)

Peter

Re: patchwork client problems

[Khem Raj]

On Sat, Sep 6, 2014 at 9:03 AM, Peter A. Bigot <pab@pabigot.com> wrote:
> Apparently not. I don't have an account, and while trying to figure out how
> to request one got to a situation where I get 502 Bad Gateway on every
> request to www.openembedded.org.
>
> The help output from pwclient and the comments in your example (and the ones
> downloaded from each project) cover it pretty well, though.  Just wanted to
> highlight to the current readership that the new version supports multiple
> projects in one config file. (Breaking the way I've been doing it for the
> last couple years which figured out the right default based on context, but
> hey, progress, right?)

OK. I thought you have a improved version of .pwclientrc, just send it
here. I will update the wiki

Re: patchwork client problems

[Khem Raj]

On Sat, Sep 6, 2014 at 8:32 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Sat, Sep 6, 2014 at 6:32 AM, Burton, Ross <ross.burton@intel.com> wrote:
>> Thanks Khem, much appreciated.
>>
>> Presumably the hooks to auto-mark merged patches haven't been
>> activated because the git server and the patchwork server are on
>> different machines. Has there been previous discussion to get this
>> resolved?
>
> it has been activated and was working in past. Do you see it not happening now ?

update hooks were not working too since they use pwclient themselves
and pwclient
was not working thus far. So it should start working again. I have
updated the hooks
to reflect the latest changes from patchwork upstream as well

Re: patchwork client problems

[Burton, Ross]

Hi Khem,

On 6 September 2014 18:25, Khem Raj <raj.khem@gmail.com> wrote:
> update hooks were not working too since they use pwclient themselves
> and pwclient
> was not working thus far. So it should start working again. I have
> updated the hooks
> to reflect the latest changes from patchwork upstream as well

Fair enough.  Can you remind me privately of my username/password, and
would it be possible to get more rights so that I can go and work my
way through the old patches that have been merged and mark them as
such?

Cheers,
Ross

Re: patchwork client problems

[Bernhard Reutner-Fischer]

On 6 September 2014 19:25, Khem Raj <raj.khem@gmail.com> wrote:
> On Sat, Sep 6, 2014 at 8:32 AM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Sat, Sep 6, 2014 at 6:32 AM, Burton, Ross <ross.burton@intel.com> wrote:
>>> Thanks Khem, much appreciated.
>>>
>>> Presumably the hooks to auto-mark merged patches haven't been
>>> activated because the git server and the patchwork server are on
>>> different machines. Has there been previous discussion to get this
>>> resolved?
>>
>> it has been activated and was working in past. Do you see it not happening now ?
>
> update hooks were not working too since they use pwclient themselves
> and pwclient
> was not working thus far. So it should start working again. I have
> updated the hooks
> to reflect the latest changes from patchwork upstream as well

FYI, The current upstream pwclient can now operate on multiple IDs, e.g.:
pwclient view 1 3 4 9
pwclient get 2 5
and you can configure a per-project or global "signoff" option for
git-am (or on the command-line -- git-am -s 77):
[options]
default = my_project2
signoff = True
[proj1]
url = ...
signoff = True

cheers,

Re: patchwork client problems

[Khem Raj]

On Mon, Sep 8, 2014 at 5:35 AM, Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com> wrote:
> On 6 September 2014 19:25, Khem Raj <raj.khem@gmail.com> wrote:
>> On Sat, Sep 6, 2014 at 8:32 AM, Khem Raj <raj.khem@gmail.com> wrote:
>>> On Sat, Sep 6, 2014 at 6:32 AM, Burton, Ross <ross.burton@intel.com> wrote:
>>>> Thanks Khem, much appreciated.
>>>>
>>>> Presumably the hooks to auto-mark merged patches haven't been
>>>> activated because the git server and the patchwork server are on
>>>> different machines. Has there been previous discussion to get this
>>>> resolved?
>>>
>>> it has been activated and was working in past. Do you see it not happening now ?
>>
>> update hooks were not working too since they use pwclient themselves
>> and pwclient
>> was not working thus far. So it should start working again. I have
>> updated the hooks
>> to reflect the latest changes from patchwork upstream as well
>
> FYI, The current upstream pwclient can now operate on multiple IDs, e.g.:
> pwclient view 1 3 4 9
> pwclient get 2 5
> and you can configure a per-project or global "signoff" option for
> git-am (or on the command-line -- git-am -s 77):
> [options]
> default = my_project2
> signoff = True
> [proj1]
> url = ...
> signoff = True
>

Thanks Bernahrd for note. FWIW our patchwork is uptodate so this should work

> cheers,