The error is from the remote side and only echo'ed locally; This is not git-trac's fault but the fault of our git post-receive hook.
Eric, is the post-receive hook still the same as in https://github.com/sagemath/trac-githooks/blob/master/post-receive.d/digest_transport.py? That file needs to have http->https fixed as in diff --git a/git_trac/digest_transport_py2.py b/git_trac/digest_transport_py2.py index 28a8520..c030432 100644 --- a/git_trac/digest_transport_py2.py +++ b/git_trac/digest_transport_py2.py @@ -121,7 +121,7 @@ class DigestTransport(object, SafeTransport): try: import urlparse req = urllib2.Request( - urlparse.urlunparse(('http', host, handler, '', '', '')), + urlparse.urlunparse(('https', host, handler, '', '', '')), request_body, {'Content-Type': 'text/xml', 'User-Agent': self.user_agent}) response = self.opener.open(req) On Friday, June 24, 2016 at 4:06:22 AM UTC+2, David Roe wrote: > > I just updated git-trac-command and tried "git trac push", and got > > remote: Traceback (most recent call last): > remote: File "./hooks/post-receive.d/01-trac_branch", line 180, in > <module> > remote: for number, ticket in trac.ticket_iter(branch): > remote: File "./hooks/post-receive.d/01-trac_branch", line 75, in > ticket_iter > remote: for result in self.rpc.search.branch(branch): > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__ > > remote: return self.__send(self.__name, args) > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request > > remote: verbose=self.__verbose > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request > > remote: return self.single_request(host, handler, request_body, > verbose) > remote: File > "/srv/git/repositories/sage.git/hooks/post-receive.d/digest_transport.py", > line 154, in single_request > remote: return self.parse_response(response) > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in > parse_response > remote: return u.close() > remote: File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close > > remote: raise ResponseError() > remote: xmlrpclib.ResponseError: ResponseError() > To g...@trac.sagemath.org:sage.git > * [new branch] HEAD -> u/roed/p_adic_floating_point_rings > > Any suggestions? > David > > On Thu, Jun 23, 2016 at 11:46 AM, Volker Braun <vbrau...@gmail.com > <javascript:>> 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+...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> 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.
