Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Sun, Jul 3, 2016 at 7:35 PM, leif  wrote:
> Erik Bray wrote:
>> git and trac should both be back up again.
>>
>> [...]
>>
>> Please let me know via e-mail, and also CC
>> sagemath-adm...@googlegroups.com if you notice something amiss.
>
> Not that important, so I'm posting here:
>
> What happened to our Trac WikiProcessors [1] (aka syntax highlighting)?
>
> I recall there was some issue displaying /git/ diffs which is fixed now,
> but while '#!diff' works on trac pages, e.g. '#!sh' and '#!python' do no
> longer work.

It may be necessary to install Pygments.  I thought that was installed
but I will double-check.

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Travis Scrimshaw]

On Friday, June 24, 2016 at 2:52:21 PM UTC-5, Dima Pasechnik wrote:
>
>
>
> On Friday, June 24, 2016 at 6:23:12 PM UTC+1, Volker Braun wrote:
>>
>> 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)
>>
>> I have just applied this patch by hand, and it has fixed things for me - 
> so I can push, no error messages, the commit gets updated on the trac page 
> (see https://trac.sagemath.org/ticket/20659)
>
>
Thank you,
Travis

 

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Dima Pasechnik]

On Friday, June 24, 2016 at 6:23:12 PM UTC+1, Volker Braun wrote:
>
> 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)
>
> I have just applied this patch by hand, and it has fixed things for me - 
so I can push, no error messages, the commit gets updated on the trac page 
(see https://trac.sagemath.org/ticket/20659)

Hopefully it's also fixed git-trac.

Enjoy,
Dima

 

>
>
> 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 
>> 
>> 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  
>> 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  
 wrote: 
 > On Jun 23, 2016 11:10, "Volker Braun"  wrote: 
 >> 
 >> I'm still getting authentication errors: 
 >> 
 >> xmlrpclib.Fault: >>> 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  
 wrote: 
 >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  

 >>> > 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 

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Volker Braun]

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 
> 
> 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  > 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  wrote: 
>>> > On Jun 23, 2016 11:10, "Volker Braun"  wrote: 
>>> >> 
>>> >> I'm still getting authentication errors: 
>>> >> 
>>> >> xmlrpclib.Fault: >> 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  
>>> wrote: 
>>> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  
>>>
>>> >>> > 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 

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Dima Pasechnik]

Erik, 
indeed, it is not working right:
commit does not get changed, and I get

$ git commit -a -m "test"
[m2fix 22d0952] test
 1 file changed, 1 insertion(+), 1 deletion(-)
clpc171[/home/scratch/dimpase/sage/sage/src/sage/interfaces]$ git push trac 
HEAD:u/dimpase/m2fix
X11 forwarding request failed on channel 0
Counting objects: 6, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 485 bytes | 0 bytes/s, done.
Total 6 (delta 5), reused 0 (delta 0)
remote: Traceback (most recent call last):
remote:   File "./hooks/post-receive.d/01-trac_branch", line 180, in 

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
   0c1f89f..22d0952  HEAD -> u/dimpase/m2fix

It appears that git/trac interaction is half-broken.
Specifically I am testing https://trac.sagemath.org/ticket/20659

Dima

On Friday, June 24, 2016 at 3:54:51 PM UTC+1, Travis Scrimshaw wrote:
>
>
>
> On Friday, June 24, 2016 at 3:03:24 AM UTC-5, Dima Pasechnik wrote:
>>
>>
>>
>> On Friday, June 24, 2016 at 3:06:22 AM UTC+1, 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 
>>> 
>>> 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?
>>>
>>  
>> needless to say, probably, but "git the hard way 
>> "
>>  
>> works:
>>
>> git  push trac HEAD:u/roed/p_adic_floating_point_rings
>>
>> That does not work for me, both before and after: I am still getting the 
> remote issues. Although the branch is being synced on the trac server. 
> However, it does not update the ticket (i.e., the commit field) when I 
> push. I really would like to get an e-mail when I (or anyone else) pushes 
> something to a ticket. My remote for "trac" is setup as in the Git The Hard 
> Way.
>
> Best,
> Travis
>
>  
>  
>

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Travis Scrimshaw]

On Friday, June 24, 2016 at 3:03:24 AM UTC-5, Dima Pasechnik wrote:
>
>
>
> On Friday, June 24, 2016 at 3:06:22 AM UTC+1, 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 
>> 
>> 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?
>>
>  
> needless to say, probably, but "git the hard way 
> " 
> works:
>
> git  push trac HEAD:u/roed/p_adic_floating_point_rings
>
> That does not work for me, both before and after: I am still getting the 
remote issues. Although the branch is being synced on the trac server. 
However, it does not update the ticket (i.e., the commit field) when I 
push. I really would like to get an e-mail when I (or anyone else) pushes 
something to a ticket. My remote for "trac" is setup as in the Git The Hard 
Way.

Best,
Travis

 
 

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Dima Pasechnik]

On Friday, June 24, 2016 at 3:06:22 AM UTC+1, 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 
> 
> 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?
>
 
needless to say, probably, but "git the hard way 
" 
works:

git  push trac HEAD:u/roed/p_adic_floating_point_rings

David
>
> On Thu, Jun 23, 2016 at 11:46 AM, Volker Braun  > 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  wrote: 
>>> > On Jun 23, 2016 11:10, "Volker Braun"  wrote: 
>>> >> 
>>> >> I'm still getting authentication errors: 
>>> >> 
>>> >> xmlrpclib.Fault: >> 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  
>>> wrote: 
>>> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  
>>>
>>> >>> > 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 .
>> To post to this group, send email to sage-...@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, 

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Jun 24, 2016 9:22 AM, "David Roe"  wrote:
>
>
>
> On Fri, Jun 24, 2016 at 12:16 AM, Erik Bray  wrote:
>>
>> On Jun 24, 2016 04:06, "David Roe"  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.
>
>
> Are you referring to Volker's patch to git_trac/digest_transport_py2.py?
That seems to have been pushed to the git-trac repository and I have it; I
ran "python setup.py install" after pulling.  Is there something else I'm
missing?

It's possible the patch is missing something. I haven't looked at git_trac
myself but from what I've seen there are inconsistencies in the URLs it
uses to connect.

I noticed some code in the patchbot uses a global variable hard-coded in
sage.env called TRAC_SERVER_URL. I forget off the top of my head (I'm on my
phone right now) if that includes the 'http' or not. But if so any code
that uses TRAC_SERVER_URL should be fixed as well.

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[David Roe]

On Fri, Jun 24, 2016 at 12:16 AM, Erik Bray  wrote:

> On Jun 24, 2016 04:06, "David Roe"  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.
>

Are you referring to Volker's patch to git_trac/digest_transport_py2.py?
That seems to have been pushed to the git-trac repository and I have it; I
ran "python setup.py install" after pulling.  Is there something else I'm
missing?
David

> 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 
> 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 
> wrote:
> >>> > On Jun 23, 2016 11:10, "Volker Braun"  wrote:
> >>> >>
> >>> >> I'm still getting authentication errors:
> >>> >>
> >>> >> xmlrpclib.Fault:  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 
> 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.
>

-- 
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 

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Jun 24, 2016 04:06, "David Roe"  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 
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  wrote:
>>> > On Jun 23, 2016 11:10, "Volker Braun"  wrote:
>>> >>
>>> >> I'm still getting authentication errors:
>>> >>
>>> >> xmlrpclib.Fault: >> >> 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 
wrote:
>>> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun 

>>> >>> > 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[David Roe]

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

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 
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  wrote:
>> > On Jun 23, 2016 11:10, "Volker Braun"  wrote:
>> >>
>> >> I'm still getting authentication errors:
>> >>
>> >> xmlrpclib.Fault: > >> 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 
>> wrote:
>> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun 
>> >>> > 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Volker Braun]

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  > wrote: 
> > On Jun 23, 2016 11:10, "Volker Braun"  
> wrote: 
> >> 
> >> I'm still getting authentication errors: 
> >> 
> >> xmlrpclib.Fault:  >> 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  
> wrote: 
> >>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  
> >>> > 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Johan S . H . Rosenkilde]

Seems like a similar patch needs to be applied to
git_trac/digest_transport.py when your system defaults to Python 3.

Best,
Johan



Volker Braun writes:

> Thats because of https, you need to do the analog change that I just did on 
> the git-trac script:
>
> 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 Wednesday, June 22, 2016 at 7:15:01 PM UTC+2, Frédéric Chapoton wrote:
>>
>> Here are 2 distinct problems, that look similar.
>>
>> (1) The new trac seems to have broken the patchbots, with the following 
>> traceback. Maybe just because of https, but not sure.
>>
>> Traceback (most recent call last):
>>   File "sage_patchbot/patchbot.py", line 997, in test_a_ticket
>>   File "sage_patchbot/trac.py", line 297, in pull_from_trac
>>   File "sage_patchbot/trac.py", line 116, in scrape
>>   File "sage_patchbot/trac.py", line 376, in load
>>   File "sage_patchbot/trac_ticket.py", line 160, in TracTicket
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
>> return self.__send(self.__name, args)
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request
>> verbose=self.__verbose
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request
>> return self.single_request(host, handler, request_body, verbose)
>>   File "sage_patchbot/digest_transport_py2.py", line 116, in single_request
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in parse_response
>> return u.close()
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
>> raise ResponseError()
>> ResponseError: ResponseError()
>> 2016-06-22 17:12:01
>> 2 seconds
>> [2016-06-22 17:12:03] #20629 raises an exception: ResponseError()
>> Traceback (most recent call last):
>>   File "sage_patchbot/patchbot.py", line 997, in test_a_ticket
>>   File "sage_patchbot/trac.py", line 297, in pull_from_trac
>>   File "sage_patchbot/trac.py", line 116, in scrape
>>   File "sage_patchbot/trac.py", line 376, in load
>>   File "sage_patchbot/trac_ticket.py", line 160, in TracTicket
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
>> return self.__send(self.__name, args)
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request
>> verbose=self.__verbose
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request
>> return self.single_request(host, handler, request_body, verbose)
>>   File "sage_patchbot/digest_transport_py2.py", line 116, in single_request
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in parse_response
>> return u.close()
>>   File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
>> raise ResponseError()
>> ResponseError: ResponseError()
>>


-- 

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Travis Scrimshaw]

Hey Erik,
   Thank you for all your work on this. However, I liked it when there 
would be a post on trac, and the subsequent e-mail, when there was a push 
to a branch on a ticket (also useful for setting the commit field 
automatically).

Best,
Travis

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Thu, Jun 23, 2016 at 11:14 AM, Erik Bray  wrote:
> On Jun 23, 2016 11:10, "Volker Braun"  wrote:
>>
>> I'm still getting authentication errors:
>>
>> xmlrpclib.Fault: > 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  wrote:
>>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun 
>>> > 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Jun 23, 2016 11:10, "Volker Braun"  wrote:
>
> I'm still getting authentication errors:
>
> xmlrpclib.Fault: 
>
> 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  wrote:
>> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun 
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.
>>
>> Erik
>
> --
> 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Volker Braun]

I'm still getting authentication errors:

xmlrpclib.Fault: 

did you also add the 

[account-manager]
environ_auth_overwrite = false

?

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  > wrote: 
> > On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  > 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. 
>
> Erik 
>

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Thu, Jun 23, 2016 at 10:43 AM, Erik Bray  wrote:
> On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  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.

Erik

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Wed, Jun 22, 2016 at 7:48 PM, Volker Braun  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).

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Volker Braun]

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?

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Jun 22, 2016 19:12, "Volker Braun"  wrote:
>
> The authentication changed, we used to have http digest (browser popup
window, with realm) and now its the trac builtin one. This breaks the
git-trac script as it tries to authenticate over http digest. I can fix it
up but first let me ask: Is that going to stay?

This was a requested feature.

I did worry that it could break any script that was relying on HTTP
authentication but nobody indicated as much. It should be possible to login
over xmlrpc or by posting to /login and storing the resulting session
cookie.

Conceivably it would not be hard to provide an alternative HTTP digest
backend for login as well.

> On Monday, June 20, 2016 at 5:18:49 PM UTC+2, Erik Bray wrote:
>>
>> Hi all,
>>
>> As decided toward the end of another recent thread [1] I willl be
>> taking down the server at UW which hosts both trac.sagemath.org and
>> git.sagemath.org, starting around 8:00 A.M. CEST.  There are at least
>> three reasons for this:
>>
>> 1. Mitigate issues related to reliance upon university IT
>> infrastructure over which we have little control [2][3] or influence
>> 2. Move to tier 1 cloud-based hosting for greater ease of deployment
>> and (hopefully) better reliability
>> 3. Address current and ongoing preformance / access issues with the
>> Trac site, which are possibly related to 1
>>
>> An additional change to be aware of is that access to
>> trac.sagemath.org, as well as the git web interface at
>> git.sagemath.org will be switched to HTTPS *only*.  HTTP redirects
>> will be set up, but please update any URLs nonetheless.
>>
>> Other than that, with a little luck you should notice few or any
>> differences.  Please keep in mind though that the current Sage Trac
>> infrastructure has a layer of grime and mold over it, and it's
>> entirely possible I've missed a few spots while shining it up.  So if
>> anything isn't working after the migration please be patient and
>> cooperate by sending notice either to
>> sagemat...@googlegroups.com, or to me personally*.
>>
>> Best,
>> Erik
>>
>> * The offer to e-mail me personally about such issues expires some
>> indeterminate amount of time after the migration is completed.  I want
>> to be on-call for migration-related issues, but in general support
>> issues should be sent to one of the mailing lists where they can be
>> handled by the best personal available at the moment.
>>
>> [1] https://groups.google.com/d/msg/sage-devel/EKhgXsdKMhY/52fKpHDBAQAJ
>> [2] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/aeyT5TluDQAJ
>> [3] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/APzgctSUDQAJ
>
> --
> 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Wed, Jun 22, 2016 at 5:41 PM, Erik Bray  wrote:
> On Wed, Jun 22, 2016 at 5:35 PM, Andrew  wrote:
>> When I try to log in to the new trac server I get the error:
>>
>> Oops…
>>
>> Trac detected an internal error:
>>
>> AttributeError: 'FakeSession' object has no attribute 'authenticated'
>>
>> There was an internal error in Trac. It is recommended that you notify your
>> local Trac administrator with the information needed to reproduce the issue.
>>
>> To that end, you could
>>
>> a ticket.
>>
>> The action that triggered the error was:
>>
>> POST: /login
>>
>> TracGuide — The Trac User and Administration Guide
>>
>>
>> I have had this problem since Erik started setting up the new server, and no
>> one else seems to have this issue, so it must be something about my set up.
>> If any one has any idea what might be wrong please let me know.
>
> I think it's the "." in your username; Trac has decided that it does
> not like that (since when, I don't know...)
>
> I'll see what I can do about it.

The problem seems to be this: https://trac.edgewall.org/changeset/14121

It is not a terribly new change, but as I upgraded Trac while doing
the upgrade, it was still not an issue with the last version of Trac
that was in use.  I will hot-patch Trac for now so that you can log
in, and will follow up on this more properly ASAP (FWIW it should also
be possible to work around this with the sage_trac plugin without
needing to patch Trac.  This is not unprecedented--I used to maintain
a plugin that was nothing bug fixes for Trac bugs :)

>> Secondly, as trac is now served via a https connection all of the references
>> to http://trac.sagemath.org/ in the sage source and documentation need to be
>> updated. Has anyone touched this yet? If not then I guess I am volunteering
>> (if my connection issue to the trac serverer can be resolved, of course!).
>
> Have at it!
>
>> On Wednesday, 22 June 2016 13:50:15 UTC+2, Erik Bray wrote:
>>>
>>> On Wed, Jun 22, 2016 at 1:42 PM, Jeroen Demeyer 
>>> wrote:
>>> > Another issue: I no longer get e-mails from Trac. The last e-mail that I
>>> > received was on 06:25 CEST (i.e. Paris time). I received nothing more
>>> > after
>>> > that, even though some tickets were changed that I am active on (e.g.
>>> > #20852).
>>>
>>> Thanks.  This is probably related:
>>> https://cloud.google.com/compute/docs/tutorials/sending-mail/
>>>
>>> I'll get that patched up.
>>
>> --
>> 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Wed, Jun 22, 2016 at 5:35 PM, Andrew  wrote:
> When I try to log in to the new trac server I get the error:
>
> Oops…
>
> Trac detected an internal error:
>
> AttributeError: 'FakeSession' object has no attribute 'authenticated'
>
> There was an internal error in Trac. It is recommended that you notify your
> local Trac administrator with the information needed to reproduce the issue.
>
> To that end, you could
>
> a ticket.
>
> The action that triggered the error was:
>
> POST: /login
>
> TracGuide — The Trac User and Administration Guide
>
>
> I have had this problem since Erik started setting up the new server, and no
> one else seems to have this issue, so it must be something about my set up.
> If any one has any idea what might be wrong please let me know.

I think it's the "." in your username; Trac has decided that it does
not like that (since when, I don't know...)

I'll see what I can do about it.

> Secondly, as trac is now served via a https connection all of the references
> to http://trac.sagemath.org/ in the sage source and documentation need to be
> updated. Has anyone touched this yet? If not then I guess I am volunteering
> (if my connection issue to the trac serverer can be resolved, of course!).

Have at it!

> On Wednesday, 22 June 2016 13:50:15 UTC+2, Erik Bray wrote:
>>
>> On Wed, Jun 22, 2016 at 1:42 PM, Jeroen Demeyer 
>> wrote:
>> > Another issue: I no longer get e-mails from Trac. The last e-mail that I
>> > received was on 06:25 CEST (i.e. Paris time). I received nothing more
>> > after
>> > that, even though some tickets were changed that I am active on (e.g.
>> > #20852).
>>
>> Thanks.  This is probably related:
>> https://cloud.google.com/compute/docs/tutorials/sending-mail/
>>
>> I'll get that patched up.
>
> --
> 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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Andrew]

When I try to log in to the new trac server I get the error:
Oops…
*Trac detected an internal error:* 

AttributeError: 'FakeSession' object has no attribute 'authenticated'

There was an internal error in Trac. It is recommended that you notify your 
local Trac administrator with the information needed to reproduce the issue.

To that end, you could 

a ticket.

The action that triggered the error was:

POST: /login

TracGuide  — The Trac User and 
Administration Guide 

I have had this problem since Erik started setting up the new server, and 
no one else seems to have this issue, so it must be something about my set 
up. If any one has any idea what might be wrong please let me know.

Secondly, as trac is now served via a https connection all of the 
references to http://trac.sagemath.org/ in the sage source and 
documentation need to be updated. Has anyone touched this yet? If not then 
I guess I am volunteering (if my connection issue to the trac serverer can 
be resolved, of course!).

Andrew

On Wednesday, 22 June 2016 13:50:15 UTC+2, Erik Bray wrote:
>
> On Wed, Jun 22, 2016 at 1:42 PM, Jeroen Demeyer  > wrote: 
> > Another issue: I no longer get e-mails from Trac. The last e-mail that I 
> > received was on 06:25 CEST (i.e. Paris time). I received nothing more 
> after 
> > that, even though some tickets were changed that I am active on (e.g. 
> > #20852). 
>
> Thanks.  This is probably related: 
> https://cloud.google.com/compute/docs/tutorials/sending-mail/ 
>
> I'll get that patched up. 
>

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

On Wed, Jun 22, 2016 at 1:42 PM, Jeroen Demeyer  wrote:
> Another issue: I no longer get e-mails from Trac. The last e-mail that I
> received was on 06:25 CEST (i.e. Paris time). I received nothing more after
> that, even though some tickets were changed that I am active on (e.g.
> #20852).

Thanks.  This is probably related:
https://cloud.google.com/compute/docs/tutorials/sending-mail/

I'll get that patched up.

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Jeroen Demeyer]

Another issue: I no longer get e-mails from Trac. The last e-mail that I 
received was on 06:25 CEST (i.e. Paris time). I received nothing more 
after that, even though some tickets were changed that I am active on 
(e.g. #20852).


--
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Erik Bray]

Fixed.

On Wed, Jun 22, 2016 at 10:34 AM, Jeroen Demeyer  wrote:
> The "branch" and "dependencies" fields are no longer hyperlinked.
>
> On https://trac.sagemath.org/ticket/20767 for example, I should be able to
> click on the branch and the various dependencies.

-- 
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.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Jeroen Demeyer]

The "branch" and "dependencies" fields are no longer hyperlinked.

On https://trac.sagemath.org/ticket/20767 for example, I should be able 
to click on the branch and the various dependencies.


--
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.