I ran ssh -v k...@trac.sagemath.org. It also fails :-) But I have no
problem in pushing changes to trac...
On Wednesday, June 29, 2016 at 11:49:31 AM UTC+9, tara fife wrote:
>
> Thanks,
>
> I went into the known_host file, and deleted everything, since I should
> only have things for Sage. Then
Thanks,
I went into the known_host file, and deleted everything, since I should only
have things for Sage. Then I reran ssh -v g...@trac.sagemath.org, and got the
same error message as before. I already pasted my new public key into the text
box in the ssh preferences tab and saved it. I don't
Perhaps you had the same issue with mine. Then the correct fix was just to
remove the line for trac.sagemath.org in the file .ssh/known_hosts, not
resetting your own ssh keys. Now that you seem to have changed your ssh
private/public key pair, you need to register your new ssh public key to
tra
I wasn't able to push changes to trac, and I thought the problem had to do with
the ssh key, so I reset it, and now I can't connect at all. I'm using an Ubuntu
14.04, and I've also tried to connect via a Kbuntu 12.04.
When I run ``ssh -v g...@trac.sagemath.org``, I get the following error.
Ope
On Tue, Jun 28, 2016 at 6:38 PM, Erik Bray wrote:
> On Tue, Jun 28, 2016 at 6:19 PM, Erik Bray wrote:
>> Hi all,
>>
>> As Luca just pointed out to me, and I also noticed on my own earlier
>> this morning, the web interface on git.sagemath.org is bugging out and
>> not displaying file contents. E
On Tuesday, June 28, 2016 at 6:23:18 PM UTC+2, Erik Bray wrote:
>
> Currently the release manager *closes* a ticket and marks it as
> "fixed" when merging the change for testing.
No. Tickets are closed *after* tests succeed.
The only race condition is if somebody else reopens positively review
leif wrote:
> Erik Bray wrote:
>> While we're tinkering with the workflow, I think we need to change the
>> workflow associated with testing changes.
>>
>> Currently the release manager *closes* a ticket and marks it as
>
> s/currently the release manager/the current release manager/ ;-)
>
>> "fi
Erik Bray wrote:
> While we're tinkering with the workflow, I think we need to change the
> workflow associated with testing changes.
>
> Currently the release manager *closes* a ticket and marks it as
s/currently the release manager/the current release manager/ ;-)
> "fixed" when merging the ch
On Tue, Jun 28, 2016 at 6:19 PM, Erik Bray wrote:
> Hi all,
>
> As Luca just pointed out to me, and I also noticed on my own earlier
> this morning, the web interface on git.sagemath.org is bugging out and
> not displaying file contents. E.g.:
> https://git.sagemath.org/sage.git/tree/README.md?h=
On Tue, Jun 28, 2016 at 4:06 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> On 28/06/16 16:04, Erik Bray wrote:
>>
>> Hi all,
>>
>> The current ticket workflow in Trac only allows creating new tickets
>> with a status 'new'. So when posting a branch with proposed changes,
>> for exampl
Hi all,
As Luca just pointed out to me, and I also noticed on my own earlier
this morning, the web interface on git.sagemath.org is bugging out and
not displaying file contents. E.g.:
https://git.sagemath.org/sage.git/tree/README.md?h=develop
Curiously it shows the correct number of line numbers
Hi all,
The current ticket workflow in Trac only allows creating new tickets
with a status 'new'. So when posting a branch with proposed changes,
for example it is necessary to create the ticket, and then immediately
update it to needs_review.
This is fine for tickets that don't immediately have
On 28/06/16 16:04, Erik Bray wrote:
Hi all,
The current ticket workflow in Trac only allows creating new tickets
with a status 'new'. So when posting a branch with proposed changes,
for example it is necessary to create the ticket, and then immediately
update it to needs_review.
This is fine f
yes, I can confirm this is a bug.
see https://trac.sagemath.org/ticket/20896
On Tuesday, June 28, 2016 at 8:35:44 AM UTC+1, Kwankyu Lee wrote:
>
> It is also strange why the pasted text copied from terminal looks double
> spaced...
>
--
You received this message because you are subscribed to th
It is also strange why the pasted text copied from terminal looks double
spaced...
--
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...@googlegr
I found a strange bug that has existed at least from Sage 7.1
In a fresh start of Sage,
sage: GF(2)^2
Vector space of dimension 2 over Finite Field of size 2
sage: CyclicPermutationGroup(10).algebra(FiniteField(5))
---
T
16 matches
Mail list logo
