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 t
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
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,
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 w
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...@tr
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-chapot
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 bot
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
>> tra
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.)
>
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 Git
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 PYTHONPAT
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
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.
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
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
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
> branc
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://
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 an
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 fai
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
reas
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 stuf
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...
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,
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 pee
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_out
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 sys
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 re
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: Co
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 real
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 tick
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 Pase
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.co
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
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
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 pul
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
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 T
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 rec
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 failu
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 c
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é-initi
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 fro
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.sage
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 y
44 matches
Mail list logo
