git-pw startup issues

[Bjorn Helgaas]

On Sat, Sep 21, 2019 at 1:37 PM Stephen Finucane <stephen at that.guru> wrote:
>
> On Sat, 2019-09-21 at 10:32 -0500, Bjorn Helgaas wrote:
> > Hello,
> >
> > I'm trying to get started with git-pw (or pwclient, but I have the
> > impression that's the old stuff, and I don't think it supports things
> > like delegating patches), but I feel like I'm banging my head against
> > the wall.  Maybe something isn't installed or configured right; I'd
> > appreciate any hints.
> >
> > Running latest git-pw (1a71697687e1 ("Handle integers too when
> > printing CSV")), I get annoying "Server version missing" messages when
> > I *do* supply the version, but the operation actually doesn't work:
> >
> >   $ git config -l | grep "^pw"
> >   pw.server=https://patchwork.ozlabs.org/api/2.1.3
> >   pw.project=linux-pci
> >   pw.token=<...>
>
> 2.1.3 is the Patchwork version, not the _API_ version. You want 1.1
> [1]. I should probably clarify that these are different things in the
> git-pw docs. Sorry for the confusion.

Ah, OK.  How do I find the API version?  The only thing I see on
https://patchwork.ozlabs.org/about/ is the 2.1.2 patchwork version.

I *assume* this is the API version supported by the server, so I have
to somehow ask the server what it supports?  Could git-pw potentially
ask the server itself so I would have to be bothered?

I must have seen 2.1.3 on patchwork.kernel.org, so I guess that was a
bit of a red herring.

> >   $ git-pw patch update --delegate "Bjorn Helgaas" 1164343
> >   ...
> >   {u'delegate': [u"User 'bhelgaas' is not a maintainer for project 'Linux PCI development'"]}
> >
> > Is this stuff that is supposed to work, or do I just need to wait?
>
> It should work, and the reason it doesn't is because of a bug. I've
> opened a report for this [3] and will have a patch available shortly,

Great, thanks!  Delegating via the web interface is quite onerous, so
I'm hopeful that git-pw is a path towards an easier way.

Bjorn