a reboot of the trac host fixed the problem.
On Wednesday, September 13, 2017 at 8:31:11 AM UTC+1, David Roe wrote:
>
> I haven't been able to find a log and I need to go to sleep. Dima should
> have access though
> David
>
> On Wed, Sep 13, 2017 at 3:17 AM, Vincent Delecroix <20100.d...@gma
I haven't been able to find a log and I need to go to sleep. Dima should
have access though
David
On Wed, Sep 13, 2017 at 3:17 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
>
>
> On 13/09/2017 09:17, David Roe wrote:
>
>> On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik
>> wrote:
On 13/09/2017 09:17, David Roe wrote:
On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik wrote:
As I mentioned, this is not under our control which ports are blocked on
GCE hosts, and which are not.
I think it is (see https://cloud.google.com/compute/docs/vpc/using-firewalls),
but I'm still
On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik wrote:
> As I mentioned, this is not under our control which ports are blocked on
> GCE hosts, and which are not.
>
I think it is (see https://cloud.google.com/compute/docs/vpc/using-firewalls),
but I'm still confused. If you look at our list of f
As I mentioned, this is not under our control which ports are blocked on GCE
hosts, and which are not.
Why don't we merely retarget bots to pull branches from github?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
On 13/09/2017 08:58, Volker Braun wrote:
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 a
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: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
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,
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
22 matches
Mail list logo
