On Jun 24, 2016 04:06, "David Roe" <roed.m...@gmail.com> wrote: > > I just updated git-trac-command and tried "git trac push", and got > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
> > remote: raise ResponseError() > remote: xmlrpclib.ResponseError: ResponseError() > > Any suggestions? See previous posts on this thread concerning HTTPS. I think someone already posted the fix to this. It seems xmlrpclib doesn't follow redirects by default, I guess. At least certainly not from HTTP to HTTPS > On Thu, Jun 23, 2016 at 11:46 AM, Volker Braun <vbraun.n...@gmail.com> wrote: >> >> Thanks, everything is working now! >> >> >> On Thursday, June 23, 2016 at 1:58:27 PM UTC+2, Erik Bray wrote: >>> >>> On Thu, Jun 23, 2016 at 11:14 AM, Erik Bray <erik....@gmail.com> wrote: >>> > On Jun 23, 2016 11:10, "Volker Braun" <vbrau...@gmail.com> wrote: >>> >> >>> >> I'm still getting authentication errors: >>> >> >>> >> xmlrpclib.Fault: <Fault 403: "TICKET_MODIFY privileges are required to >>> >> perform this operation on Ticket #20581. You don't have the required >>> >> permissions."> >>> >> >>> >> did you also add the >>> >> >>> >> [account-manager] >>> >> environ_auth_overwrite = false >>> > >>> > Yes. Let me make sure that's actually working though. Also make sure the >>> > requests are definitely going through /login/xmlrpc >>> > >>> >> On Thursday, June 23, 2016 at 11:05:11 AM UTC+2, Erik Bray wrote: >>> >>> >>> >>> On Thu, Jun 23, 2016 at 10:43 AM, Erik Bray <erik....@gmail.com> wrote: >>> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun <vbrau...@gmail.com> >>> >>> > wrote: >>> >>> >> On Wednesday, June 22, 2016 at 7:23:34 PM UTC+2, Erik Bray wrote: >>> >>> >>> >>> >>> >>> Conceivably it would not be hard to provide an alternative HTTP >>> >>> >>> digest >>> >>> >>> backend for login as well. >>> >>> >> >>> >>> >> >>> >>> >> That would be the easiest solution... can you set it up? >>> >>> > >>> >>> > Let me take a closer look at that documentation you pointed to >>> >>> > earlier. If I understand correctly, adding that option to the >>> >>> > AccountManagerPlugin will allow /login/xmlrpc to be handled by the web >>> >>> > server (where in turn I can enable htdigest authentication). >>> >>> >>> >>> Okay, I have re-enabled HTTP digest authentication on /login/xmlrpc as >>> >>> before. Please let me know if that fixes things. >>> >>> Sorry about that--I should have gone with my first instinct on it. >>> >>> Indeed it looks like there's some inconsistency in URLs that the >>> patchbot is using for RPC calls. For example I see some attempts in >>> the logs to POST to /login/rpc instead of /login/xmlrpc. Granted the >>> former definitely should work as well, so I will loosen the rule to >>> allow /login/rpc (as well /login/jsonrpc which technically should be >>> allowed to work even if we're not using it currently). >> >> -- >> You received this message because you are subscribed to the Google Groups "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-devel@googlegroups.com. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
