[sage-devel] git trac is down ?

[Frédéric Chapoton]

I have access failures to the git repo from trac :

chapoton@pc-chapoton:~/sage$ git pull trac 
u/mantepse/fricas_output_and_sage_conversion_bug
fatal: read error: Connexion ré-initialisée par le correspondant

Does anybody else suffers from that ?

Frederic

-- 
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] Patchbot failures metaticket

[Jeroen Demeyer]

On 2017-09-11 18:59, Maarten Derickx wrote:

I think that all patchbot failure tickets should automatically deserve
the status critical.


They should be blockers (unless the error comes from a broken patchbot).


p.s. Tips on how to search for tickets on trac are welcome!


Google

site:trac.sagemath.org elliptic curves

The only annoying thing with Google is that it tends to prefer old pages 
for bugs which are fixed long ago.


--
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] git trac is down ?

[Daniel Krenn]

On 2017-09-12 12:04, Frédéric Chapoton wrote:
> I have access failures to the git repo from trac :
> 
> chapoton@pc-chapoton:~/sage$ git pull trac
> u/mantepse/fricas_output_and_sage_conversion_bug
> fatal: read error: Connexion ré-initialisée par le correspondant
> 
> Does anybody else suffers from that ?

Yes, same here (since this some hours at least).

Daniel

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

[sage-devel] Re: git trac is down ?

[Dima Pasechnik]

works for me... (from UK)

On Tuesday, September 12, 2017 at 11:04:42 AM UTC+1, Frédéric Chapoton 
wrote:
>
> I have access failures to the git repo from trac :
>
> chapoton@pc-chapoton:~/sage$ git pull trac 
> u/mantepse/fricas_output_and_sage_conversion_bug
> fatal: read error: Connexion ré-initialisée par le correspondant
>
> Does anybody else suffers from that ?
>
> Frederic
>

-- 
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] git trac is down ?

[Daniel Krenn]

On 2017-09-12 12:49, Daniel Krenn wrote:
> On 2017-09-12 12:04, Frédéric Chapoton wrote:
>> I have access failures to the git repo from trac :
>>
>> chapoton@pc-chapoton:~/sage$ git pull trac
>> u/mantepse/fricas_output_and_sage_conversion_bug
>> fatal: read error: Connexion ré-initialisée par le correspondant
>>
>> Does anybody else suffers from that ?
> 
> Yes, same here (since this some hours at least).

Details:

dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac
fatal: read error: Connection reset by peer
dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)

(from AT)

-- 
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] git trac is down ?

[Dima Pasechnik]

basically same remote setup for me, and it still works fine; 
We can set up a github mirror, perhaps...

On Tuesday, September 12, 2017 at 11:58:57 AM UTC+1, Daniel Krenn wrote:
>
> On 2017-09-12 12:49, Daniel Krenn wrote: 
> > On 2017-09-12 12:04, Frédéric Chapoton wrote: 
> >> I have access failures to the git repo from trac : 
> >> 
> >> chapoton@pc-chapoton:~/sage$ git pull trac 
> >> u/mantepse/fricas_output_and_sage_conversion_bug 
> >> fatal: read error: Connexion ré-initialisée par le correspondant 
> >> 
> >> Does anybody else suffers from that ? 
> > 
> > Yes, same here (since this some hours at least). 
>
> Details: 
>
> dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac 
> fatal: read error: Connection reset by peer 
> dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v 
> tracgit://trac.sagemath.org/sage.git (fetch) 
> tracg...@trac.sagemath.org:sage.git (push) 
>
> (from AT) 
>

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

[sage-devel] Re: [sagemath-admins] git trac connection problems from continental Europe

[Dima Pasechnik]

I've created a trac mirror repo on github:
https://github.com/dimpase/sagetrac-mirror
Please pull from there, if you have problems with trac's git.

Cheers,
Dima


On Tue, Sep 12, 2017 at 12:07 PM, Dima Pasechnik  wrote:
> Reported on sage-devel.
> But works for me at UK...
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "sagemath-admins" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sagemath-admins+unsubscr...@googlegroups.com.
> 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] git trac is down ?

[Dima Pasechnik]

A mirror on github is up (see another message here), enjoy...
https://github.com/dimpase/sagetrac-mirror

On Tuesday, September 12, 2017 at 12:05:53 PM UTC+1, Dima Pasechnik wrote:
>
> basically same remote setup for me, and it still works fine; 
> We can set up a github mirror, perhaps...
>
> On Tuesday, September 12, 2017 at 11:58:57 AM UTC+1, Daniel Krenn wrote:
>>
>> On 2017-09-12 12:49, Daniel Krenn wrote: 
>> > On 2017-09-12 12:04, Frédéric Chapoton wrote: 
>> >> I have access failures to the git repo from trac : 
>> >> 
>> >> chapoton@pc-chapoton:~/sage$ git pull trac 
>> >> u/mantepse/fricas_output_and_sage_conversion_bug 
>> >> fatal: read error: Connexion ré-initialisée par le correspondant 
>> >> 
>> >> Does anybody else suffers from that ? 
>> > 
>> > Yes, same here (since this some hours at least). 
>>
>> Details: 
>>
>> dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac 
>> fatal: read error: Connection reset by peer 
>> dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v 
>> tracgit://trac.sagemath.org/sage.git (fetch) 
>> tracg...@trac.sagemath.org:sage.git (push) 
>>
>> (from AT) 
>>
>

-- 
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: [sagemath-admins] git trac connection problems from continental Europe

[Clemens Heuberger]

Am 2017-09-12 um 13:26 schrieb Dima Pasechnik:
> I've created a trac mirror repo on github:
> https://github.com/dimpase/sagetrac-mirror
> Please pull from there, if you have problems with trac's git.

do I understand correctly that this is a snapshot (as indicated on that page:
2017-09-12 12:15 UK time), so this is not suitable for running patchbots?

I tried accessing git://trac.sagemath.org/sage.git from two different
universities in Austria and one virtual server in Germany, no success.

Regards,

Clemens

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

[sage-devel] Re: [sagemath-admins] git trac connection problems from continental Europe

['Martin R' via sage-devel]

It worked for me after I rebooted my laptop (in Vienna, Austria).  I guess 
it's a coincidence, but who knows...

Martin

Am Dienstag, 12. September 2017 13:26:03 UTC+2 schrieb Dima Pasechnik:
>
> I've created a trac mirror repo on github: 
> https://github.com/dimpase/sagetrac-mirror 
> Please pull from there, if you have problems with trac's git. 
>
> Cheers, 
> Dima 
>
>
> On Tue, Sep 12, 2017 at 12:07 PM, Dima Pasechnik  > wrote: 
> > Reported on sage-devel. 
> > But works for me at UK... 
> > 
> > -- 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "sagemath-admins" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to sagemath-admi...@googlegroups.com . 
> > 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: [sagemath-admins] git trac connection problems from continental Europe

[Clemens Heuberger]

Am 2017-09-12 um 13:58 schrieb 'Martin R' via sage-devel:
> It worked for me after I rebooted my laptop (in Vienna, Austria).  I guess 
> it's
> a coincidence, but who knows...

a reboot did not help me (Klagenfurt, Austria).

Clemens

> 
> Martin
> 
> Am Dienstag, 12. September 2017 13:26:03 UTC+2 schrieb Dima Pasechnik:
> 
> I've created a trac mirror repo on github:
> https://github.com/dimpase/sagetrac-mirror
> 
> Please pull from there, if you have problems with trac's git.
> 
> Cheers,
> Dima
> 
> 
> On Tue, Sep 12, 2017 at 12:07 PM, Dima Pasechnik  > wrote:
> > Reported on sage-devel.
> > But works for me at UK...
> >
> > --
> >
> > ---
> > You received this message because you are subscribed to the Google 
> Groups
> > "sagemath-admins" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an
> > email to sagemath-admi...@googlegroups.com .
> > 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: [sagemath-admins] git trac connection problems from continental Europe

[Dima Pasechnik]

It is a snapshot, not constantly updated.
But it does contain all the branches present in the original repo.

We can look into setting up a constant updating, it
should not be too hard, and would take off load from trac, too.

Dima


On Tue, Sep 12, 2017 at 12:54 PM, Clemens Heuberger
 wrote:
> Am 2017-09-12 um 13:26 schrieb Dima Pasechnik:
>> I've created a trac mirror repo on github:
>> https://github.com/dimpase/sagetrac-mirror
>> Please pull from there, if you have problems with trac's git.
>
> do I understand correctly that this is a snapshot (as indicated on that page:
> 2017-09-12 12:15 UK time), so this is not suitable for running patchbots?
>
> I tried accessing git://trac.sagemath.org/sage.git from two different
> universities in Austria and one virtual server in Germany, no success.
>
> Regards,
>
> Clemens

-- 
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: [sagemath-admins] git trac connection problems from continental Europe

[Dima Pasechnik]

PS. it's set up using --mirror option of git clone and git push, so
it should actually be suitable for running anything (bots too) that
only needs read access to the repo.

In detail, on my desktop I did

git clone --bare g...@trac.sagemath.org:sage.git
cd sage.git/
git push --mirror g...@github.com:dimpase/sagetrac-mirror.git

to create a github mirror.
I understand that to update the mirror locally (on my desktop)
I merely need to run

git remote update

I am not sure ATM how to push these updates on github, but
it must be doable I guess...



On Tue, Sep 12, 2017 at 1:10 PM, Dima Pasechnik  wrote:
> It is a snapshot, not constantly updated.
> But it does contain all the branches present in the original repo.
>
> We can look into setting up a constant updating, it
> should not be too hard, and would take off load from trac, too.
>
> Dima
>
>
> On Tue, Sep 12, 2017 at 12:54 PM, Clemens Heuberger
>  wrote:
>> Am 2017-09-12 um 13:26 schrieb Dima Pasechnik:
>>> I've created a trac mirror repo on github:
>>> https://github.com/dimpase/sagetrac-mirror
>>> Please pull from there, if you have problems with trac's git.
>>
>> do I understand correctly that this is a snapshot (as indicated on that page:
>> 2017-09-12 12:15 UK time), so this is not suitable for running patchbots?
>>
>> I tried accessing git://trac.sagemath.org/sage.git from two different
>> universities in Austria and one virtual server in Germany, no success.
>>
>> Regards,
>>
>> Clemens

-- 
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: [sagemath-admins] git trac connection problems from continental Europe

[Maarten Derickx]

P.s. in case this helps others from making the same mistake as me: don't 
click the branch link on https://github.com/dimpase/sagetrac-mirror/ in 
order to see if all branches are there unless you have a decent system with 
some ram to spare.

On Tuesday, 12 September 2017 14:18:46 UTC+2, Dima Pasechnik wrote:
>
> PS. it's set up using --mirror option of git clone and git push, so 
> it should actually be suitable for running anything (bots too) that 
> only needs read access to the repo. 
>
> In detail, on my desktop I did 
>
> git clone --bare g...@trac.sagemath.org:sage.git 
> cd sage.git/ 
> git push --mirror g...@github.com:dimpase/sagetrac-mirror.git 
>
> to create a github mirror. 
> I understand that to update the mirror locally (on my desktop) 
> I merely need to run 
>
> git remote update 
>
> I am not sure ATM how to push these updates on github, but 
> it must be doable I guess... 
>
>
>
> On Tue, Sep 12, 2017 at 1:10 PM, Dima Pasechnik  > wrote: 
> > It is a snapshot, not constantly updated. 
> > But it does contain all the branches present in the original repo. 
> > 
> > We can look into setting up a constant updating, it 
> > should not be too hard, and would take off load from trac, too. 
> > 
> > Dima 
> > 
> > 
> > On Tue, Sep 12, 2017 at 12:54 PM, Clemens Heuberger 
> > > wrote: 
> >> Am 2017-09-12 um 13:26 schrieb Dima Pasechnik: 
> >>> I've created a trac mirror repo on github: 
> >>> https://github.com/dimpase/sagetrac-mirror 
> >>> Please pull from there, if you have problems with trac's git. 
> >> 
> >> do I understand correctly that this is a snapshot (as indicated on that 
> page: 
> >> 2017-09-12 12:15 UK time), so this is not suitable for running 
> patchbots? 
> >> 
> >> I tried accessing git://trac.sagemath.org/sage.git from two different 
> >> universities in Austria and one virtual server in Germany, no success. 
> >> 
> >> Regards, 
> >> 
> >> Clemens 
>

-- 
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] Patchbot failures metaticket

[Vincent Delecroix]

On 12/09/2017 12:23, Jeroen Demeyer wrote:

On 2017-09-11 18:59, Maarten Derickx wrote:

I think that all patchbot failure tickets should automatically deserve
the status critical.


They should be blockers (unless the error comes from a broken patchbot).


+1


p.s. Tips on how to search for tickets on trac are welcome!


Google

site:trac.sagemath.org elliptic curves

The only annoying thing with Google is that it tends to prefer old pages 
for bugs which are fixed long ago.


Or possibly, we could use the tag "patchbot" and hence a very simple 
trac query.


--
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] Patchbot failures metaticket

[Vincent Delecroix]

Hi,

I think a meta-ticket is a complete burden to maintain. And as already 
said in other mails, this identification should be done by other means.


Vincent

On 11/09/2017 18:59, Maarten Derickx wrote:

Hi all,

During the recent writing of new code and reviewing I got annoyed that it
costs really a lot of effort for me to see if there was already a ticket
for a certain patchbot failure. I therefore decided to create a metaticket
that should serve as an overview of all currently known patchbot failures.
It can be found here:

https://trac.sagemath.org/ticket/23832

I think that all patchbot failure tickets should automatically deserve the
status critical. Since patchbot failures make sage development and
reviewing way more troublesome. Are there any other people with an opinion
on this?

Thanks,
Maarten

p.s. Tips on how to search for tickets on trac are welcome!



--
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] git trac is down ?

[Vincent Delecroix]

On 12/09/2017 12:58, Daniel Krenn wrote:

On 2017-09-12 12:49, Daniel Krenn wrote:

On 2017-09-12 12:04, Frédéric Chapoton wrote:

I have access failures to the git repo from trac :

chapoton@pc-chapoton:~/sage$ git pull trac
u/mantepse/fricas_output_and_sage_conversion_bug
fatal: read error: Connexion ré-initialisée par le correspondant

Does anybody else suffers from that ?


Yes, same here (since this some hours at least).


Details:

dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac
fatal: read error: Connection reset by peer
dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)

(from AT)


Same for me (FR)

$ git remote -v
origin  git://github.com/sagemath/sage.git (fetch)
origin  git://github.com/sagemath/sage.git (push)
tracgit://trac.sagemath.org/sage.git (fetch)
tracgit://trac.sagemath.org/sage.git (push)
+quasar:/home/vdelecro/sage_patchbot$ git pull trac develop
fatal: read error: Connection reset by peer


(Though git pull origin develop does work of course)

--
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] git trac is down ?

[Vincent Delecroix]

There is already

git://github.com/sagemath/sage.git

On 12/09/2017 13:26, Dima Pasechnik wrote:

A mirror on github is up (see another message here), enjoy...
https://github.com/dimpase/sagetrac-mirror

On Tuesday, September 12, 2017 at 12:05:53 PM UTC+1, Dima Pasechnik wrote:


basically same remote setup for me, and it still works fine;
We can set up a github mirror, perhaps...

On Tuesday, September 12, 2017 at 11:58:57 AM UTC+1, Daniel Krenn wrote:


On 2017-09-12 12:49, Daniel Krenn wrote:

On 2017-09-12 12:04, Frédéric Chapoton wrote:

I have access failures to the git repo from trac :

chapoton@pc-chapoton:~/sage$ git pull trac
u/mantepse/fricas_output_and_sage_conversion_bug
fatal: read error: Connexion ré-initialisée par le correspondant

Does anybody else suffers from that ?


Yes, same here (since this some hours at least).


Details:

dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac
fatal: read error: Connection reset by peer
dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)

(from AT)







--
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: [sagemath-admins] git trac connection problems from continental Europe

[Dima Pasechnik]

On Tuesday, September 12, 2017 at 2:25:34 PM UTC+1, Maarten Derickx wrote:
>
> P.s. in case this helps others from making the same mistake as me: don't 
> click the branch link on https://github.com/dimpase/sagetrac-mirror/ in 
> order to see if all branches are there unless you have a decent system with 
> some ram to spare.
>

Well, the desktop version works on my (new) mobile phone Chrome browser :-)
besides, you can search for a branch...

 

>
> On Tuesday, 12 September 2017 14:18:46 UTC+2, Dima Pasechnik wrote:
>>
>> PS. it's set up using --mirror option of git clone and git push, so 
>> it should actually be suitable for running anything (bots too) that 
>> only needs read access to the repo. 
>>
>> In detail, on my desktop I did 
>>
>> git clone --bare g...@trac.sagemath.org:sage.git 
>> cd sage.git/ 
>> git push --mirror g...@github.com:dimpase/sagetrac-mirror.git 
>>
>> to create a github mirror. 
>> I understand that to update the mirror locally (on my desktop) 
>> I merely need to run 
>>
>> git remote update 
>>
>> I am not sure ATM how to push these updates on github, but 
>> it must be doable I guess... 
>>
>>
>>
>> On Tue, Sep 12, 2017 at 1:10 PM, Dima Pasechnik  
>> wrote: 
>> > It is a snapshot, not constantly updated. 
>> > But it does contain all the branches present in the original repo. 
>> > 
>> > We can look into setting up a constant updating, it 
>> > should not be too hard, and would take off load from trac, too. 
>> > 
>> > Dima 
>> > 
>> > 
>> > On Tue, Sep 12, 2017 at 12:54 PM, Clemens Heuberger 
>> >  wrote: 
>> >> Am 2017-09-12 um 13:26 schrieb Dima Pasechnik: 
>> >>> I've created a trac mirror repo on github: 
>> >>> https://github.com/dimpase/sagetrac-mirror 
>> >>> Please pull from there, if you have problems with trac's git. 
>> >> 
>> >> do I understand correctly that this is a snapshot (as indicated on 
>> that page: 
>> >> 2017-09-12 12:15 UK time), so this is not suitable for running 
>> patchbots? 
>> >> 
>> >> I tried accessing git://trac.sagemath.org/sage.git from two different 
>> >> universities in Austria and one virtual server in Germany, no success. 
>> >> 
>> >> Regards, 
>> >> 
>> >> Clemens 
>>
>

-- 
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] git trac is down ?

[Vincent Delecroix]

On 12/09/2017 16:26, Vincent Delecroix wrote:



On 12/09/2017 12:58, Daniel Krenn wrote:

On 2017-09-12 12:49, Daniel Krenn wrote:

On 2017-09-12 12:04, Frédéric Chapoton wrote:

I have access failures to the git repo from trac :

chapoton@pc-chapoton:~/sage$ git pull trac
u/mantepse/fricas_output_and_sage_conversion_bug
fatal: read error: Connexion ré-initialisée par le correspondant

Does anybody else suffers from that ?


Yes, same here (since this some hours at least).


Details:

dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac
fatal: read error: Connection reset by peer
dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v
trac    git://trac.sagemath.org/sage.git (fetch)
trac    g...@trac.sagemath.org:sage.git (push)

(from AT)


Same for me (FR)

$ git remote -v
origin  git://github.com/sagemath/sage.git (fetch)
origin  git://github.com/sagemath/sage.git (push)
trac    git://trac.sagemath.org/sage.git (fetch)
trac    git://trac.sagemath.org/sage.git (push)
+quasar:/home/vdelecro/sage_patchbot$ git pull trac develop
fatal: read error: Connection reset by peer


(Though git pull origin develop does work of course)


Correction: does not work on quasar but *does* on mangouste

@mangouste$ git remote -v
origin  https://github.com/sagemath/sage.git (fetch)
origin  https://github.com/sagemath/sage.git (push)
tracg...@trac.sagemath.org:sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)
@mangouste$ git pull trac develop
Depuis trac.sagemath.org:sage
 * branch  develop-> FETCH_HEAD
Déjà à jour.


So it seems that the git server does not longer accept read only 
requests without ssh 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] git trac is down ?

[Clemens Heuberger]

Am 2017-09-12 um 16:28 schrieb Vincent Delecroix:
> So it seems that the git server does not longer accept read only requests
> without ssh authentication...

I confirm that: on one and the same machine:

$ LANG=C git fetch git://trac.sagemath.org/sage.git
fatal: read error: Connection reset by peer
$ LANG=C git fetch g...@trac.sagemath.org:sage.git
>From trac.sagemath.org:sage
 * branch  HEAD   -> FETCH_HEAD

This is a problem for a patchbot which will usually not have a valid ssh key.

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

[sage-devel] Re: git trac is down ?

[Frédéric Chapoton]

This works for me with the "mangouste" setting:

git remote -v
origin https://github.com/sagemath/sage.git (fetch)
origin https://github.com/sagemath/sage.git (push)
trac g...@trac.sagemath.org:sage.git (fetch)
trac g...@trac.sagemath.org:sage.git (push)


Le mardi 12 septembre 2017 12:04:42 UTC+2, Frédéric Chapoton a écrit :
>
> I have access failures to the git repo from trac :
>
> chapoton@pc-chapoton:~/sage$ git pull trac 
> u/mantepse/fricas_output_and_sage_conversion_bug
> fatal: read error: Connexion ré-initialisée par le correspondant
>
> Does anybody else suffers from that ?
>
> Frederic
>

-- 
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] git trac is down ?

[Dima Pasechnik]

On Tuesday, September 12, 2017 at 3:28:06 PM UTC+1, vdelecroix wrote:
>
> There is already 
>
> git://github.com/sagemath/sage.git 
>

this is not a full mirror of trac's git repo.
 

>
> On 12/09/2017 13:26, Dima Pasechnik wrote: 
> > A mirror on github is up (see another message here), enjoy... 
> > https://github.com/dimpase/sagetrac-mirror 
> > 
> > On Tuesday, September 12, 2017 at 12:05:53 PM UTC+1, Dima Pasechnik 
> wrote: 
> >> 
> >> basically same remote setup for me, and it still works fine; 
> >> We can set up a github mirror, perhaps... 
> >> 
> >> On Tuesday, September 12, 2017 at 11:58:57 AM UTC+1, Daniel Krenn 
> wrote: 
> >>> 
> >>> On 2017-09-12 12:49, Daniel Krenn wrote: 
>  On 2017-09-12 12:04, Frédéric Chapoton wrote: 
> > I have access failures to the git repo from trac : 
> > 
> > chapoton@pc-chapoton:~/sage$ git pull trac 
> > u/mantepse/fricas_output_and_sage_conversion_bug 
> > fatal: read error: Connexion ré-initialisée par le correspondant 
> > 
> > Does anybody else suffers from that ? 
>  
>  Yes, same here (since this some hours at least). 
> >>> 
> >>> Details: 
> >>> 
> >>> dakrenn@pc72-math /local/dakrenn/sage/source $ LANG=C git fetch trac 
> >>> fatal: read error: Connection reset by peer 
> >>> dakrenn@pc72-math /local/dakrenn/sage/source $ git remote -v 
> >>> tracgit://trac.sagemath.org/sage.git (fetch) 
> >>> tracg...@trac.sagemath.org:sage.git (push) 
> >>> 
> >>> (from AT) 
> >>> 
> >> 
> > 
>

-- 
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] Patchbot failures metaticket

[Maarten Derickx]

Hi Vincent,

I think "a complete burden" is highly exaggerated, there should not be a 
new patchbot ticket to often. And if someone has to create a ticket then 
just copy pasting the failing files and the ticket number to the ticket 
description should not be to much work.

As for removing old stuff I am totally happy to volunteer as a maintainer 
of the ticket so that failures for old beta's and other releases are 
removed from time to time.

The ticket also has some benefits, namely you see a nice overview of all 
the files affected, so this will make checking wether the files for which 
you currently have a patchbot failing way faster then clicking on all the 
results of a trac query.

As a summary your solution would make writing new tickets easier, and the 
current solution makes checking wether a ticket exists easier. Since the 
latter will happen way more often I think the benefits outweigh the costs.

On Tuesday, 12 September 2017 15:34:11 UTC+2, vdelecroix wrote:
>
> Hi, 
>
> I think a meta-ticket is a complete burden to maintain. And as already 
> said in other mails, this identification should be done by other means. 
>
> Vincent 
>
> On 11/09/2017 18:59, Maarten Derickx wrote: 
> > Hi all, 
> > 
> > During the recent writing of new code and reviewing I got annoyed that 
> it 
> > costs really a lot of effort for me to see if there was already a ticket 
> > for a certain patchbot failure. I therefore decided to create a 
> metaticket 
> > that should serve as an overview of all currently known patchbot 
> failures. 
> > It can be found here: 
> > 
> > https://trac.sagemath.org/ticket/23832 
> > 
> > I think that all patchbot failure tickets should automatically deserve 
> the 
> > status critical. Since patchbot failures make sage development and 
> > reviewing way more troublesome. Are there any other people with an 
> opinion 
> > on this? 
> > 
> > Thanks, 
> > Maarten 
> > 
> > p.s. Tips on how to search for tickets on trac are welcome! 
> > 
>

-- 
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] Patchbot failures metaticket

[Vincent Delecroix]

Hi Marteen,

"complete burden" = "each release". So precisely, we need somebody to 
volunteer to maintain this list. I already hardly find the energy to 
fill a ticket for the reasons why my patchbot is not working any more at 
each new release (including the fact that I need to search for a 
reason). In case I know the problem, I just send an e-mail on 
sage-release and in case I find the answer (or somebody finds it) I 
disable explicitely the package on my patchbot. Here is the list of 11 
broken optional packages on quasar


# deformation: 
https://groups.google.com/forum/#!topic/sage-devel/gEFC-ZwtAGU

# normaliz: https://trac.sagemath.org/ticket/23586
# giac: https://groups.google.com/forum/#!topic/sage-devel/QMfm3NOBZaI
# polytopes_db: 
https://groups.google.com/forum/#!topic/sage-devel/KI0qtg1kYoA

# cbc: https://trac.sagemath.org/ticket/22006
# gap_packages, database_gap: https://trac.sagemath.org/ticket/22576
# qepcad: https://trac.sagemath.org/ticket/22851
# database_cremona_ellcurve: https://trac.sagemath.org/ticket/23840
# libtheora??
# sip: https://groups.google.com/forum/#!topic/sage-devel/Jc-5u9YslkI
# openblas is not used anywhere

Though in an ideal world
 - tickets should not be merged if any patchbot is not happy with it
 - patchbot should also be identified with its set of optional packages 
installed (for now the server does not make any distinction)

 - patchbot should test tickets upgrading an optional package

Best
Vincent

PS: thank you for willing to work on this. People do not seem to care so 
much about failing doctests due to installation of optional packages.


On 12/09/2017 18:28, Maarten Derickx wrote:

Hi Vincent,

I think "a complete burden" is highly exaggerated, there should not be a
new patchbot ticket to often. And if someone has to create a ticket then
just copy pasting the failing files and the ticket number to the ticket
description should not be to much work.

As for removing old stuff I am totally happy to volunteer as a maintainer
of the ticket so that failures for old beta's and other releases are
removed from time to time.

The ticket also has some benefits, namely you see a nice overview of all
the files affected, so this will make checking wether the files for which
you currently have a patchbot failing way faster then clicking on all the
results of a trac query.

As a summary your solution would make writing new tickets easier, and the
current solution makes checking wether a ticket exists easier. Since the
latter will happen way more often I think the benefits outweigh the costs.

On Tuesday, 12 September 2017 15:34:11 UTC+2, vdelecroix wrote:


Hi,

I think a meta-ticket is a complete burden to maintain. And as already
said in other mails, this identification should be done by other means.

Vincent

On 11/09/2017 18:59, Maarten Derickx wrote:

Hi all,

During the recent writing of new code and reviewing I got annoyed that

it

costs really a lot of effort for me to see if there was already a ticket
for a certain patchbot failure. I therefore decided to create a

metaticket

that should serve as an overview of all currently known patchbot

failures.

It can be found here:

https://trac.sagemath.org/ticket/23832

I think that all patchbot failure tickets should automatically deserve

the

status critical. Since patchbot failures make sage development and
reviewing way more troublesome. Are there any other people with an

opinion

on this?

Thanks,
Maarten

p.s. Tips on how to search for tickets on trac are welcome!







--
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: git trac is down ?

[Clemens Heuberger]

Am 2017-09-12 um 12:53 schrieb Dima Pasechnik:
> works for me... (from UK)

what is your git remote configuration? So basically, is the failure in
authenticated mode reproducible?

Clemens

> 
> On Tuesday, September 12, 2017 at 11:04:42 AM UTC+1, Frédéric Chapoton wrote:
> 
> I have access failures to the git repo from trac :
> 
> chapoton@pc-chapoton:~/sage$ git pull trac
> u/mantepse/fricas_output_and_sage_conversion_bug
> fatal: read error: Connexion ré-initialisée par le correspondant
> 
> Does anybody else suffers from that ?
> 
> Frederic
> 
> -- 
> 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: git trac is down ?

[Dima Pasechnik]

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.

we have seen this before, firewalls don't like git://



-- 
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: git trac is down ?

[Vincent Delecroix]

On 12/09/2017 20:32, Dima Pasechnik wrote:

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.


We should not force a user to upload her ssh key on trac in order to 
pull a branch.



we have seen this before, firewalls don't like git://


Which firewall?

--
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: git trac is down ?

[Clemens Heuberger]

Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:
> On 12/09/2017 20:32, Dima Pasechnik wrote:
>> ah, right, do not use git://,  use
>> the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.
> 
> We should not force a user to upload her ssh key on trac in order to pull a 
> branch.

for patchbots, we cannot.

> 
>> we have seen this before, firewalls don't like git://
> 
> Which firewall?
> 


-- 
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: git trac is down ?

[Vincent Delecroix]

On 12/09/2017 20:46, Clemens Heuberger wrote:

Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:

On 12/09/2017 20:32, Dima Pasechnik wrote:

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.


We should not force a user to upload her ssh key on trac in order to pull a 
branch.


for patchbots, we cannot.


Why? We could force the patchbot user to have a trac account with an 
uploaded ssh key and make the patchbot fetch via ssh. (of course we do 
not want to)





we have seen this before, firewalls don't like git://


Which firewall?







--
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: git trac is down ?

[Dima Pasechnik]

On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote:
>
> On 12/09/2017 20:32, Dima Pasechnik wrote: 
> > ah, right, do not use git://,  use 
> > the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch. 
>
> We should not force a user to upload her ssh key on trac in order to 
> pull a branch. 
>

Oh well, trac's git does not support http, AFAIK. Or perhaps does not have 
it enabled.
Erik would know...

Anyhow, we can use a mirror on github, say.
 

>
> > we have seen this before, firewalls don't like git:// 
>
> Which firewall? 
>

the google's one, that protects GCE host where trac is run.
 

-- 
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: git trac is down ?

[Erik Bray]

On Tue, Sep 12, 2017 at 9:59 PM, Dima Pasechnik  wrote:
>
>
> On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote:
>>
>> On 12/09/2017 20:32, Dima Pasechnik wrote:
>> > ah, right, do not use git://,  use
>> > the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.
>>
>> We should not force a user to upload her ssh key on trac in order to
>> pull a branch.
>
>
> Oh well, trac's git does not support http, AFAIK. Or perhaps does not have
> it enabled.
> Erik would know...

It has *never* supported read-only access via HTTP or HTTPS.

> Anyhow, we can use a mirror on github, say.
>
>>
>>
>> > we have seen this before, firewalls don't like git://
>>
>> Which firewall?
>
>
> the google's one, that protects GCE host where trac is run.
>
>
> --
> 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.

[sage-devel] promoting github.com/sagemath/sage to full git trac mirror?

[Dima Pasechnik]

There are several reasons for this:
one is to allow http(s):// and git:// read access to all the trac branches,

less load on the trac server...

To keep it up to date one can simply run a cronjob
on trac, doing
git push --mirror ...
every 10 minutes, say...
(or run a cronjob on a third side, with a local mirror,
that would do
git remote update
followed by
git push --mirror...

The repo is not very big, just over 200Mb.

Any thoughts?

Dima

-- 
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: SAGE_PATH and PYTHONPATH

[Erik Bray]

On Sat, Sep 9, 2017 at 9:20 PM, Ralf Hemmecke  wrote:
> On 09/09/2017 05:05 PM, Maarten Derickx wrote:
>> In case people start setting pythonpath after reading this thread:
>> you will actually get some silly doctest failures if python path is
>> set.
>
> I don't need to set SAGE_PATH (or PYTHONPATH) for testing Sage. All I
> want is to tell Sage about a locally installed package that does not
> come from "sage -i".
>
> As I understand what Nils was saying is that instead of SAGE_PATH I
> should simply switch to PYTHONPATH directly.
>
> That would be OK for me.
>
> However, it's quite bad that the commit that removed SAGE_PATH did not
> also consider to change the documentation for Sage 8.0. It still says
> that SAGE_PATH is in use.

I agree--this is one of those cases where we could do better about
deprecation.  Even if it were imperative to change things so that
SAGE_PATH were ignored completely, it would still be a better
deprecation path to at least supply a warning that it's not used
anymore :)

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

[sage-devel] Re: promoting github.com/sagemath/sage to full git trac mirror?

[Robert Jacobson]

I think there is utility in leaving github.com/sagemath/sage as it is:

   - It's easy to navigate using the GitHub web interface, whereas the 
   entire trac server repo is not. (Try browsing the branches.)
   - It gives direct, no-nonsense access to releases, RC's, and beta's. 

Having a full GitHub mirror of the trac server repo is also useful for the 
reasons you've already mentioned. So maybe have 
github.com/sagemath/sagetrac-mirror in addition to github.com/sagemath/sage.

Best,

Robert


On Tuesday, 12 September 2017 16:21:50 UTC-4, Dima Pasechnik wrote:
>
> There are several reasons for this: 
> one is to allow http(s):// and git:// read access to all the trac 
> branches, 
>
> less load on the trac server... 
>
> To keep it up to date one can simply run a cronjob 
> on trac, doing 
> git push --mirror ... 
> every 10 minutes, say... 
> (or run a cronjob on a third side, with a local mirror, 
> that would do 
> git remote update 
> followed by 
> git push --mirror... 
>
> The repo is not very big, just over 200Mb. 
>
> Any thoughts? 
>
> Dima 
>

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

[sage-devel] Re: promoting github.com/sagemath/sage to full git trac mirror?

[Dima Pasechnik]

On Tuesday, September 12, 2017 at 9:42:51 PM UTC+1, Robert Jacobson wrote:
>
> I think there is utility in leaving github.com/sagemath/sage as it is:
>
>- It's easy to navigate using the GitHub web interface, whereas the 
>entire trac server repo is not. (Try browsing the branches.)
>- It gives direct, no-nonsense access to releases, RC's, and beta's. 
>
> Having a full GitHub mirror of the trac server repo is also useful for the 
> reasons you've already mentioned. So maybe have 
> github.com/sagemath/sagetrac-mirror in addition to 
> github.com/sagemath/sage.
>

that's certainly another option.

In fact, probably a bit more tweaking is needed to make the the web 
interface on github mirror usable.
It gets cluttered, as you see here on a prototype:
https://github.com/dimpase/sagetrac-mirror
as more branches get pushed to...

Dima

>
> Best,
>
> Robert
>
>
> On Tuesday, 12 September 2017 16:21:50 UTC-4, Dima Pasechnik wrote:
>>
>> There are several reasons for this: 
>> one is to allow http(s):// and git:// read access to all the trac 
>> branches, 
>>
>> less load on the trac server... 
>>
>> To keep it up to date one can simply run a cronjob 
>> on trac, doing 
>> git push --mirror ... 
>> every 10 minutes, say... 
>> (or run a cronjob on a third side, with a local mirror, 
>> that would do 
>> git remote update 
>> followed by 
>> git push --mirror... 
>>
>> The repo is not very big, just over 200Mb. 
>>
>> Any thoughts? 
>>
>> Dima 
>>
>

-- 
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: promoting github.com/sagemath/sage to full git trac mirror?

[Dima Pasechnik]

On Tue, Sep 12, 2017 at 9:55 PM, Dima Pasechnik  wrote:
>
>
> On Tuesday, September 12, 2017 at 9:42:51 PM UTC+1, Robert Jacobson wrote:
>>
>> I think there is utility in leaving github.com/sagemath/sage as it is:
>>
>> It's easy to navigate using the GitHub web interface, whereas the entire
>> trac server repo is not. (Try browsing the branches.)
>> It gives direct, no-nonsense access to releases, RC's, and beta's.
>>
>> Having a full GitHub mirror of the trac server repo is also useful for the
>> reasons you've already mentioned. So maybe have
>> github.com/sagemath/sagetrac-mirror in addition to github.com/sagemath/sage.
>
>
> that's certainly another option.
>
> In fact, probably a bit more tweaking is needed to make the the web
> interface on github mirror usable.
> It gets cluttered, as you see here on a prototype:
> https://github.com/dimpase/sagetrac-mirror
> as more branches get pushed to...

although they say that these links are gone after a couple of hours by
themselves... We'll see.

>
> Dima
>>
>>
>> Best,
>>
>> Robert
>>
>>
>> On Tuesday, 12 September 2017 16:21:50 UTC-4, Dima Pasechnik wrote:
>>>
>>> There are several reasons for this:
>>> one is to allow http(s):// and git:// read access to all the trac
>>> branches,
>>>
>>> less load on the trac server...
>>>
>>> To keep it up to date one can simply run a cronjob
>>> on trac, doing
>>> git push --mirror ...
>>> every 10 minutes, say...
>>> (or run a cronjob on a third side, with a local mirror,
>>> that would do
>>> git remote update
>>> followed by
>>> git push --mirror...
>>>
>>> The repo is not very big, just over 200Mb.
>>>
>>> Any thoughts?
>>>
>>> Dima
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/i_ColVl-AOA/unsubscribe.
> To unsubscribe from this group and all its topics, 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: git trac is down ?

[Clemens Heuberger]

Am 2017-09-12 um 20:48 schrieb Vincent Delecroix:
> On 12/09/2017 20:46, Clemens Heuberger wrote:
>> Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:
>>> On 12/09/2017 20:32, Dima Pasechnik wrote:
 ah, right, do not use git://,  use
 the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.
>>>
>>> We should not force a user to upload her ssh key on trac in order to pull a
>>> branch.
>>
>> for patchbots, we cannot.
> 
> Why? We could force the patchbot user to have a trac account with an uploaded
> ssh key and make the patchbot fetch via ssh. (of course we do not want to)

that would probably have to be a ssh key without passphrase. I'd feel more
comfortable if such a key would only have read-only access on trac's git.

So it would not longer be easy to "just run a patchbot".

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

[sage-devel] Re: git trac is down ?

[Frédéric Chapoton]

In case nobody has noticed, let me insist that this behaviour is currently 
preventing most (if not all) the patchbots from doing anything.

Frederic

Le mardi 12 septembre 2017 12:04:42 UTC+2, Frédéric Chapoton a écrit :
>
> I have access failures to the git repo from trac :
>
> chapoton@pc-chapoton:~/sage$ git pull trac 
> u/mantepse/fricas_output_and_sage_conversion_bug
> fatal: read error: Connexion ré-initialisée par le correspondant
>
> Does anybody else suffers from that ?
>
> Frederic
>

-- 
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: git trac is down ?

[Vincent Delecroix]

On 13/09/2017 08:17, Clemens Heuberger wrote:

Am 2017-09-12 um 20:48 schrieb Vincent Delecroix:

On 12/09/2017 20:46, Clemens Heuberger wrote:

Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:

On 12/09/2017 20:32, Dima Pasechnik wrote:

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.


We should not force a user to upload her ssh key on trac in order to pull a
branch.


for patchbots, we cannot.


Why? We could force the patchbot user to have a trac account with an uploaded
ssh key and make the patchbot fetch via ssh. (of course we do not want to)


that would probably have to be a ssh key without passphrase. I'd feel more
comfortable if such a key would only have read-only access on trac's git.


No. You can use a the ssh keyring for that purpose.


So it would not longer be easy to "just run a patchbot".


Indeed. And anyway, you don't want the patchbot to have write access to 
some branches on the git server.


--
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: git trac is down ?

[Clemens Heuberger]

Am 2017-09-13 um 08:20 schrieb Vincent Delecroix:
> On 13/09/2017 08:17, Clemens Heuberger wrote:
>> Am 2017-09-12 um 20:48 schrieb Vincent Delecroix:
>>> On 12/09/2017 20:46, Clemens Heuberger wrote:
 Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:
> On 12/09/2017 20:32, Dima Pasechnik wrote:
>> ah, right, do not use git://,  use
>> the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.
>
> We should not force a user to upload her ssh key on trac in order to pull 
> a
> branch.

 for patchbots, we cannot.
>>>
>>> Why? We could force the patchbot user to have a trac account with an 
>>> uploaded
>>> ssh key and make the patchbot fetch via ssh. (of course we do not want to)
>>
>> that would probably have to be a ssh key without passphrase. I'd feel more
>> comfortable if such a key would only have read-only access on trac's git.
> 
> No. You can use a the ssh keyring for that purpose.

My patchbots run under a separate user account and should just be started when
the system boots.

Using a keyring would require somehow to unlock the keyring.

-- 
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: git trac is down ?

[Vincent Delecroix]

On 12/09/2017 22:00, Erik Bray wrote:

On Tue, Sep 12, 2017 at 9:59 PM, Dima Pasechnik  wrote:



On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote:


On 12/09/2017 20:32, Dima Pasechnik wrote:

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.


We should not force a user to upload her ssh key on trac in order to
pull a branch.



Oh well, trac's git does not support http, AFAIK. Or perhaps does not have
it enabled.
Erik would know...


It has *never* supported read-only access via HTTP or HTTPS.


Perhaps I was wrong in my claim about protocls. There are the two 
following possibilities to configure access to the git server


trac1git://trac.sagemath.org/sage.git
trac2g...@trac.sagemath.org:sage.git

As far as I used to think 1) is http and 2) is ssh (I might be wrong 
here). What I am sure about and has been reported by Frédéric is that:


   *trac1 used to work but does not work anymore*

Vincent

--
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: git trac is down ?

[Vincent Delecroix]

On 13/09/2017 08:24, Vincent Delecroix wrote:

On 12/09/2017 22:00, Erik Bray wrote:
On Tue, Sep 12, 2017 at 9:59 PM, Dima Pasechnik  
wrote:



On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote:


On 12/09/2017 20:32, Dima Pasechnik wrote:

ah, right, do not use git://,  use
the same thing, g...@trac.sagemath.org:sage.git, for both push and 
fetch.


We should not force a user to upload her ssh key on trac in order to
pull a branch.



Oh well, trac's git does not support http, AFAIK. Or perhaps does not 
have

it enabled.
Erik would know...


It has *never* supported read-only access via HTTP or HTTPS.


Perhaps I was wrong in my claim about protocls. There are the two 
following possibilities to configure access to the git server


trac1    git://trac.sagemath.org/sage.git
trac2    g...@trac.sagemath.org:sage.git

As far as I used to think 1) is http and 2) is ssh (I might be wrong 
here).


I was indeed wrong. This is using the git protocol on port 9418. 
Documentation at



https://git-scm.com/book/id/v2/Git-on-the-Server-The-Protocols#_the_git_protocol

What I am sure about and has been reported by Frédéric is that:


    *trac1 used to work but does not work anymore*


Hence: why the git protocol is not supported anymore?

--
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: git trac is down ?

[Volker Braun]

On Tuesday, September 12, 2017 at 10:00:32 PM UTC+2, Erik Bray wrote:
>
> It has *never* supported read-only access via HTTP or HTTPS. 
>

Afaik we have always supported git:// access and our documentation 
explicitly recommends setting it up that way; Its also how the git-trac 
script configures things.  

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