perhaps adding an invalid ssh key still breaks the communication between
git server and trac...
Can they still push changes to the git server?
On Friday, July 1, 2016 at 12:35:55 AM UTC+1, Viviane Pons wrote:
>
> Hi,
>
> I'm with two new sage git users: eviatarbach and avenrias and they seem to
Just got this error when saving changes to #18889:
closeWarning: The change has been saved, but an error occurred while sending
notifications: expected string or buffer
Important?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe f
Hi,
I'm with two new sage git users: eviatarbach and avenrias and they seem to
have a similar problem. They have put their ssh key on trac (I've checked),
but it keeps saying "Permission denied (publickey)" when they try
ssh -T g...@trac.sagemath.org info
Here is what they get:
OpenSSH_7.2p2 Ub
On Thu, Jun 30, 2016 at 8:35 AM, Erik Bray wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, 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
Hi leif,
> Well, it's apparently just that your toolchain isn't using binutils
> consistently; usually LLVM's tools get installed as 'llvm-ar' and
> 'llvm-ranlib', or they don't get installed into the default PATH.
I don't have llvm-ar or llvm-ranlib installed AFAIK (they're in the
package llvm w
Erik Bray wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, 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
On Tue, Jun 28, 2016 at 10:20 PM, Volker Braun wrote:
> 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.
I'm jus
On Tue, Jun 28, 2016 at 7:14 PM, 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 curre
On Thu, Jun 30, 2016 at 5:18 PM, Frédéric Chapoton wrote:
> I am doing things inside a virtualenv because I do not want to destroy my
> sage installation (which happened once or twice) by trying to make sage with
> python3.
>
> But if there is a better way, I am ready to listen. So far, despite m
On Thursday, June 30, 2016 at 5:12:50 PM UTC+2, Frédéric Chapoton wrote:
>
> It is still not very clear to me what SAGE_PYTHON3 (well hidden) is
> supposed to achieve.
>
When building Sage-the-distribution, it builds python3 instead of python2.
Anything that uses Sage's own python will then be b
I am doing things inside a virtualenv because I do not want to destroy my
sage installation (which happened once or twice) by trying to make sage
with python3.
But if there is a better way, I am ready to listen. So far, despite my
askings, nobody has told me "how to try to build sage using pyt
As I wrote in the ticket I'm not exactly sure what you're using a
virtualenv for.
To be clear, I think it's great to use virtualenv for development in
general. But I think this will only confuse things when building
SAGE-THE-DISTRIBUTION from scratch since everything should get
installed into $SA
Thanks.
It is still not very clear to me what SAGE_PYTHON3 (well hidden) is
supposed to achieve. Am I right to say that if the code of sage and
all its dependencies would work with py3, "export SAGE_PYTHON3=yes" then
"make build" would build a py3 sage ?
I have made a ticket to document SAGE_PY
Johan S. H. Rosenkilde wrote:
>>> ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required
>>> by /usr/lib/libLLVM-3.8.so)
>>
>>
>> Are you using llvm? As far as I know that doesnt' work, though I haven't
>> tried it myself.
>
> I was baffled about that too. I haven't consciou
Hi,
> sage: sage: f1(x) = -1
> sage: sage: f2(x) = 2
> sage: sage: f = Piecewise([[(0,pi/2),f1],[(pi/2,pi),f2]])
> /home/novoselt/sage/src/bin/sage-ipython:1: DeprecationWarning: use
> lower-case piecewise instead
> See http://trac.sagemath.org/14801 for details.
> #!/usr/bin/
It wouldn't surprise me too much if you can' t build python2 inside a
python 3 venv. Its pretty low on the priority of things to support imho.
Try building with SAGE_PYTHON3=yes
On Thursday, June 30, 2016 at 3:29:25 PM UTC+2, Frédéric Chapoton wrote:
>
> Hello everybody,
>
> I am trying to bui
Hello everybody,
I am trying to build sage with python3 (I asked for help here before, but
got only little).
It fails, of course (see log below for "make build"). I would like to
understand how.
I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
python3
This python3 comp
>> ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required
>> by /usr/lib/libLLVM-3.8.so)
>
>
> Are you using llvm? As far as I know that doesnt' work, though I haven't
> tried it myself.
I was baffled about that too. I haven't consciously done anything that
would use llvm. I
On Thursday, June 30, 2016 at 2:26:47 PM UTC+2, Johan S. R. Nielsen wrote:
>
> ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required
> by /usr/lib/libLLVM-3.8.so)
Are you using llvm? As far as I know that doesnt' work, though I haven't
tried it myself.
--
You received th
I've created #20904 to deprecate the Matrix.I property which is ready for
review.
This seemed to be the only case that most people agreed was bad. There
remains Matrix.T and Matrix.H as well as a handful of other public API
properties scattered randomly across Sage.
Best,
Johan
--
You receiv
> sounds like the first "make" failed...
That's not clear to me. The compile of Sage itself seemed to work but
then make failed during doc-building. This has happened so often during
the years I've worked with Sage, however, that I've learned to ignore
it. Inspecting the error now, I see that this
it's quite not clear from your post how to reproduce this. The log mentions
some git branch; where is this branch?
It might also be easier to parse if you take the failing doctest out and
produce few lines of Sage code that
need to get the error interactively, at Sage prompt (on the git branch in
Ready for review now!
On Wednesday, June 29, 2016 at 3:20:09 PM UTC+1, Dima Pasechnik wrote:
>
> This is going to happen on https://trac.sagemath.org/ticket/20905
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
23 matches
Mail list logo
