), and the build continues and finishes successfully.
Since my emacs install is not overly excotic, I wonder why this hangs.
Martin
Am Dienstag, 17. Dezember 2013 20:07:32 UTC+1 schrieb Volker Braun:
What is going on in the log, is the installation restarting by itself 4
times? Or are you
the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
make: *** [build] Error 1
What can I do?
Cheers, Jaap
On Wed, Dec 18, 2013 at 12:00 PM, Volker Braun
vbrau...@gmail.comjavascript:
wrote:
Sage 6.0
A.k.a. Today is a good day to die, the credo of release engineering
Yes, the sage -upgrade should just pull changes to the source repo and
then rebuild. Will end up in precisely the same place as where you started
it.
On Thursday, December 19, 2013 8:46:10 PM UTC, Justin C. Walker wrote:
On Dec 19, 2013, at 07:02 , Volker Braun wrote:
I'm pleased
Correction: I pushed a bit too much to the develop branch, so the official
beta is the 6.1.beta3 tag (git checkout 6.1.beta3).
On Friday, January 3, 2014 4:19:53 PM UTC-10, Volker Braun wrote:
See the git develop branch, as usual. Tarball is here:
http://boxen.math.washington.edu/home
.tar.gz
François
From: sage-r...@googlegroups.com javascript:
[sage-r...@googlegroups.comjavascript:]
on behalf of Volker Braun [vbrau...@gmail.com javascript:]
Sent: Saturday, 4 January 2014 16:44
To: sage-r...@googlegroups.com javascript
On Sunday, January 5, 2014 7:42:50 PM UTC-10, P Purkayastha wrote:
How can I fix this?
Does make distclean make fix it?
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send
Imho Windows is just too broken to be able to develop on. We should aim for
a binary package using whichever atlas library we can use (e.g. from
cygwin) rather than go on some quest for compiling ATLAS on windows.
On Friday, January 10, 2014 2:53:28 AM UTC-10, Jean-Pierre Flori wrote:
It
Is this really an issue? Its true that tar will extract the files as
group-writeable if your umask allows it. But the gid is going to be your
primary group. It would be decidedly weird if there are untrusted users in
your own primary group.
On Wednesday, January 8, 2014 8:15:56 AM UTC-5,
in Maxima #15529. Somebody should open a ticket and see if its possible to
prevent the python build from calling hg.
On Friday, January 17, 2014 12:45:00 AM UTC-5, P Purkayastha wrote:
On 01/16/2014 01:10 PM, Volker Braun wrote:
It is my pleasure to announce Sage-6.1.beta5. As usual, you can
You *should* not change upstream tarballs. Sometimes, we have to. There is
no good way to change the upstream tarball without changing the version
number. Arguably, thats a feature. Maybe use package-2014123.tar.gz if you
have to.
There is no point in a spkg-src script if the tarball is not
On Monday, February 3, 2014 12:04:58 PM UTC, John Cremona wrote:
I deleted all of src/doc/output and re-made, and the problem went away.
You can also make doc-clean
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this
Yes, the release manager can do that ;-)
Is there any other ticket that should go in there?
On Tuesday, February 4, 2014 8:06:24 AM UTC, Jeroen Demeyer wrote:
It has been proposed to make a Sage 6.1.1 release to fix the broken
LaTeX in the notebook (#15778). I think that is a good
.
Should this be filed as a ticket ?
Emmanuel Charpentier
Le jeudi 30 janvier 2014 22:08:14 UTC+1, Volker Braun a écrit :
I'm pleased to announce the release of Sage-6.1!
This means that now the master branch changed for the first time, and
now points to the new stable release
If SAGE_ATLAS_LIB is set then we don't compile atlas. If the system atlas
libraries don't work then you'll get an error later on, of course.
On Wednesday, February 5, 2014 10:52:11 AM UTC, Nathann Cohen wrote:
I'd say [1] is wrong and the *pt* files are optional.
For sure the debian
make doesn't know about changed environment variables, so you either
recompile from scratch or keep using your current install.
On Wednesday, February 5, 2014 10:59:55 AM UTC, Nathann Cohen wrote:
If SAGE_ATLAS_LIB is set then we don't compile atlas. If the system
atlas
libraries don't
Binaries are now available at
http://boxen.math.washington.edu/home/buildbot/binaries/
Harald: please mirror!
On Wednesday, February 5, 2014 10:56:34 AM UTC, Volker Braun wrote:
This is a hotfix release for the notebook mathjax issue.
The trac master branch now points to 6.1.1
The develop branch has been updated to 6.2.beta1. The master branch stays
at 6.1.1. Source tarball is here:
http://boxen.math.washington.edu/home/release/sage-6.2.beta1/sage-6.2.beta1.tar.gz
Changelog (note: add --author Release Manager to only see the trac ticket
merges):
$ git log --oneline
Mercurial is a Python program. While building Sage's Python the interpreter
might be in a bad shape, or we inject libraries via LD_LIBRARY_PATH into
the system interpreter that break it.
On Thursday, February 27, 2014 11:37:37 PM UTC+1, François wrote:
It is all a bit of a mystery. Why is the
I've never seen that error. The documentation is built at the end, so that
means that Sage was built without errors. Can you try running the doctests?
Perhaps some component is not working and somehow makes the
numeric/environment.pickle invalid?
If all fails, run make distclean make...
On
Does Sage actually work? Run sage -btp src/ and ignore the doctests that
require the documentation built..
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I unpacked the sage-6.2.beta3 tarball and ran make make doc-clean
make and it worked without error. Somebody who can reproduce the failure
should investigate...
On Friday, March 7, 2014 2:41:41 PM UTC, Volker Braun wrote:
Does Sage actually work? Run sage -btp src/ and ignore the doctests
try a make distclean make
On Saturday, March 8, 2014 3:38:35 PM UTC, defeo wrote:
After a `git pull develop`, build fails with the error below. Same
fail on a frech clone. Same on beta3. Any ideas?
Luca
cc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC
On Monday, March 10, 2014 11:42:52 AM UTC, Nathann Cohen wrote:
? You think that there is an proper way to do that ?
Just make a backup of the third-party files before installing a newer
version. When you reinstall the old version, just restore that backup. Of
course we'd need a way to
Ah, ok. There is currently a race with the installation of setuptools-using
Python packages (which includes matplotlib dependencies). This looks very
much like it.
It will be fixed by http://trac.sagemath.org/ticket/13201, I hope...
--
You received this message because you are subscribed to
Just try make again, its likely to not hit that particular race all the
time. Or build in serial.
On Tuesday, March 11, 2014 9:42:36 AM UTC, Nathann Cohen wrote:
Ah, ok. There is currently a race with the installation of
setuptools-using Python packages (which includes matplotlib
Why don't you have /dev/stdout? Which operating system? Its supposed to be
present in Linux, though not POSXI.
On Wednesday, March 12, 2014 9:19:46 PM UTC-4, Jonathan Bober wrote:
I built, and all tests passed. However, I can't seen to install packages:
jb12407@lmfdb5:~/sage-6.2.beta4$
why it wants it to be a directory.)
On Thu, Mar 13, 2014 at 1:40 PM, Volker Braun vbrau...@gmail.comjavascript:
wrote:
Why don't you have /dev/stdout? Which operating system? Its supposed to
be present in Linux, though not POSXI.
On Wednesday, March 12, 2014 9:19:46 PM UTC-4, Jonathan
was set to en_US.UTF-8, and
that changed nothing. I don't have any problem displaying the sage banner.
On Thu, Mar 13, 2014 at 2:03 PM, Volker Braun vbrau...@gmail.comjavascript:
wrote:
Do you have some wonky locale settings, e.g. UTF8 handed through by ssh
to a server that is not unicode
08852aac599c6901511941ef74ac69121c917095b783209ef75985d7cc095a2b09d2e98577786252f4b6bbb1efc1b39c25518f9406e9001ceec93d35de252857
sage-6.2.beta4.tar.gz
On Friday, March 14, 2014 11:00:20 AM UTC-4, kcrisman wrote:
On Tuesday, March 11, 2014 4:08:10 PM UTC-4, Volker Braun wrote:
This includes the fix
On Friday, March 14, 2014 7:53:10 PM UTC-4, Jonathan Bober wrote:
I don't know why. However, having just spent a bit of time fighting with
selinux while setting up apache stuff, I've decided that this must also be
some sort of strange selinux issue.
Highly unlikely unless you put Sage
On Tuesday, March 18, 2014 2:19:05 PM UTC-4, kcrisman wrote:
gcc -g -Wl,-no_pie -o gap ariths.o .. weakptr.o -lm
/Users/.../sage-6.2.beta4/local/lib/libgmp.a
/usr/bin/ld: unknown flag: -no_pie
collect2: error: ld returned 1 exist status
I'm searching for stuff about this, maybe
Which version of OSX and Sage, and did you try the branch at the
aforementioned ticket?
On Wednesday, March 19, 2014 5:41:41 AM UTC-4, Maarten Derickx wrote:
When I tried to build it also failed at singular. ld complains about: symbol
dyld_stub_binding_helper not found . Googling for this
The develop branch on git has been updated to 6.2.beta5. Alternatively,
you can download the source tarball:
http://boxen.math.washington.edu/home/release/sage-6.2.beta5/sage-6.2.beta5.tar.gz
$ git log --first-parent develop ^6.2.beta4 --oneline
9db8c5c Updated Sage version to 6.2.beta5
cca671d
at that time ^^;
Nathann
On 23 March 2014 21:56, Volker Braun vbrau...@gmail.com javascript:wrote:
The develop branch on git has been updated to 6.2.beta5. Alternatively,
you can download the source tarball:
http://boxen.math.washington.edu/home/release/sage-6.2.beta5/sage-6.2.beta5.tar.gz
$ git
On Monday, March 24, 2014 5:46:16 PM UTC, Nathann Cohen wrote:
How much RAM do you have?
4GB
That should be enough if your swap is set up correctly. How much swap space
do you have? (e.g. output of top)
--
You received this message because you are subscribed to the Google Groups
Get it from the develop git branch or the source tarball
at
http://boxen.math.washington.edu/home/release/sage-6.2.beta6/sage-6.2.beta6.tar.gz
Mini-changelog:
12bbca0 Updated Sage version to 6.2.beta6
a473d6f Trac #14800: Implement Pynac-Python callback for function::subs()
cdfaa4a Trac
URL: http://trac.sagemath.org/14780
Reported by: burcin
Ticket author(s): Burcin Erocal, Volker Braun
Reviewer(s): Volker Braun, Jean-Pierre Flori
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group
make distclean make
On Tuesday, April 8, 2014 6:38:02 PM UTC+2, Ralf Stephan wrote:
Barfs in make doc here (after make):
-f local/etc/sage-started.txt ] || local/bin/sage-starts
build/pipestatus ./sage --docbuild --no-pdf-links all html 21 tee -a
logs/dochtml.log
Traceback (most
It builds fine on bsd with 10.6. Maybe you need to update your XCode?
On Thursday, April 10, 2014 3:04:37 PM UTC+2, Dima Pasechnik wrote:
I am stuck on singular on OSX 10.6.8 with
libtool: unrecognized option `-dynamic' error
(no amount of distclean seem to help, I even tried pulling
Scroll up, the real error should be somewhere.
On Tuesday, April 15, 2014 7:42:37 PM UTC+1, John Cremona wrote:
I am having trouble building the docs here: after (git checkout
develop; git pull trac develop; make) Sage builds fine but there was
an error message building docs, so I did
We need the whole log, not just the last two lines.
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this
I've updated the scripts for generating the virtual appliance, its now
based on CentOS 6 which should be less maintenance effort... Updated VM is
here:
http://boxen.math.washington.edu/home/vbraun/vm/sage-6.1.1.ova
http://boxen.math.washington.edu/home/vbraun/vm/sage-6.1.1.ova.sha512
--
You
Are you volunteering to write the announcement? ;-)
On Tuesday, May 13, 2014 8:26:05 AM UTC+1, Daniel Krenn wrote:
Is there a reason, why there is still no official announcement (e.g. in
sage-announce) of Sage 6.2?
--
You received this message because you are subscribed to the Google
It works on the buildbot which errors do you get?
On Tuesday, May 13, 2014 4:12:44 PM UTC+1, Simon King wrote:
Hi Releasers,
On 2014-05-11, Ralf Stephan gtr...@gmail.com javascript: wrote:
I get doctest failures in dev/sagedev.py that go away when I switch to
master and make, but
Get it from the updated develop git branch or the source tarball
at http://boxen.math.washington.edu/home/release/sage-6.3.beta1.tar.gz
Mini-changelog:
36af814 Trac #16265: transducers.weight: new common transducer
bbc23e1 Trac #15099: Implement numeric evaluation of zetaderiv
cf5d0ef Trac
You have my attention. We can of course wait with any future releases until
somebody fixes this.
In an ideal world we would have reliable library versioning, so you
wouldn't need to rebuild maxima UNLESS the ecl library version changes in
an incompatible way (which can be read off from the
On Tuesday, May 27, 2014 7:31:37 PM UTC+1, kcrisman wrote:
I've had more trouble with building doc since the git switch than I can
shake a stick at.
We intentionally made warnings into errors that break doc build. The docs
didn't build before either, you just didn't notice.
--
You
I think the best option is to fix the sigalarm delivery to be 100% reliable
On Thursday, May 29, 2014 2:34:13 PM UTC+1, Ralf Stephan wrote:
On Thu, May 29, 2014 at 12:28 PM, Volker Braun
vbrau...@gmail.comjavascript:
wrote:
The reason is alarm() not working reliably. The failing test
Get it from the develop git branch or download the self-contained source
tarball at
http://boxen.math.washington.edu/home/tmp-release/sage-6.3.beta6.tar.gz
Mini changelog:
1467152 Trac #16186: extend transducers.add to arbitrary input-length
b5dd91b Trac #16668: Enhance
This meta-ticket tracks random doctest failures:
http://trac.sagemath.org/ticket/15459
On Saturday, July 19, 2014 8:14:22 AM UTC-4, Emmanuel Charpentier wrote:
make ptestlong got me one failure in src/sage/interfaces/expect.py at line
796. Doctesting it standalone (./sage -t --long
.
http://ask.sagemath.org/questions/scope:all/sort:activity-desc/page:1/query:load_ext/
http://stackoverflow.com/search?q=sage+ipython+notebook
So it would be nice to have that work out of the box
as soon as we can. Maybe for the next beta?
Samuel
-
From: Volker Braun vbrau
This is http://trac.sagemath.org/ticket/15535
On Friday, July 25, 2014 7:35:02 AM UTC-4, Justin C. Walker wrote:
On Jul 19, 2014, at 11:21, leif not.r...@online.de javascript: wrote:
On 19.07.2014 11:07, Emmanuel Charpentier wrote:
Ahem...
Le samedi 19 juillet 2014 07:14:20 UTC+2, Volker
C. Walker jus...@mac.com
javascript: wrote:
On Jul 28, 2014, at 19:40, Volker Braun vbrau...@gmail.com javascript:
wrote:
See the develop git branch or download the all-in-one tarball
http://boxen.math.washington.edu/home/vbraun/tmp-release/sage-6.3.beta7.tar.gz
Built w/o problems
, Ralf Stephan gtr...@gmail.com
javascript: wrote:
On Tue, Jul 29, 2014 at 3:27 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
$SAGE_LOCAL/lib/libga
p
ralf@ark:~/sage l local/lib/libgap
ls: cannot access local/lib/libgap: No such file or directory
--
You received
The graph database issue is http://trac.sagemath.org/ticket/16735 (needs
review)
On Tuesday, July 29, 2014 8:30:44 AM UTC-4, Justin C. Walker wrote:
On Jul 28, 2014, at 19:40, Volker Braun vbrau...@gmail.com javascript:
wrote:
See the develop git branch or download the all-in-one
I've created http://trac.sagemath.org/ticket/16751 for this issue.
On Saturday, August 2, 2014 4:18:59 AM UTC-4, Jan Keitel wrote:
I can't build this on a 2013 MacBook Air running Mac Os 10.9.4, because
Singular fails to build:
Error building Sage.
The following package(s) may have
Except that singular's configure doesn't even support that...
On Saturday, August 2, 2014 9:47:35 AM UTC-4, leif wrote:
Volker Braun wrote:
IMHO everything should be configured with --enable-shared
--disable-static...
I *knew* you'd take the bait B)
-leif
On Saturday
Agree, we should get ready for 6.3. Outstanding issues:
* The permissions of the release folder on boxen need to be fixed
* I slammed my finger in a door and it is painful to type
And recently fixed:
* I was traveling and just got back to the UK a few hours ago
On Monday, August 4, 2014
On Monday, August 4, 2014 10:39:06 AM UTC+1, François wrote:
* Dima pointed an obvious problem that I didn’t see when I gave a positive
review here:
http://trac.sagemath.org/ticket/16735#comment:7
That probably should be fixed before release.
IMHO it is a reasonable burden to make
Here is the first release candidate. Please give it a test and report any
build problems. As usual, get the newest git develop branch or
download http://boxen.math.washington.edu/home/release/sage-6.3.rc0.tar.gz
8a63d57 Trac #16752: Cleanup in hypergeometric functions
201bb8a Trac #15191: Add
:09 PM UTC+1, Harald Schilly wrote:
On Tue, Aug 5, 2014 at 5:26 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
Interesting, which gcc version?
well, mabye it is picking up the wrong file? (I'll delete my CCACHE and
try again) ... i don't know.
version numbers:
(sage-sh
Also, where is the /home/harri/.local coming from? Is that from some
environment variable that you have set?
On Tuesday, August 5, 2014 9:33:20 PM UTC+1, Harald Schilly wrote:
gcc -I/home/harri/.local/include -L/home/harri/.local/lib
In any case, can you post logs/pkgs/r-3.1.1.p0.log
On Wednesday, August 6, 2014 8:37:09 AM UTC+1, Harald Schilly wrote:
On Tue, Aug 5, 2014 at 11:12 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
Also, where is the /home/harri/.local coming from? Is that from some
environment
This looks like it is picking up some environment variable. Can you post
the output of env?
On Thursday, August 7, 2014 8:46:33 AM UTC+1, Harald Schilly wrote:
On Wed, Aug 6, 2014 at 1:35 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
In any case, can you post logs/pkgs/r-3.1.1
I guess AFM = Adobe Font Metrics, seems like something is wrong with your
system fonts.
On Monday, August 11, 2014 9:55:11 AM UTC+1, P Purkayastha wrote:
File src/doc/de/tutorial/tour_functions.rst, line 24, in doc.de.tutorial
.tour_functions
Failed example:
plot(f, 0, 2)
Expected
IMHO we should just give up on correcting naming errors. If you can't
decide on how to write your own name then I would call it a feature that
each novel spelling is a first contribution
On Tuesday, August 12, 2014 12:14:09 PM UTC+1, Harald Schilly wrote:
I'm happy to add the release log,
If you want to update your local master branch you should do:
git checkout master# switch to your local master branch
git pull --ff-only trac master
On Tuesday, August 12, 2014 1:26:30 PM UTC+1, Andrew wrote:
git pull --ff-only 6.3
not the recommended way to update the master branch to a
See the develop git branch or the source tarball at
http://boxen.math.washington.edu/home/release/sage-6.4.beta0.tar.gz
Mini-changelog:
07b385d Updated Sage version to 6.4.beta0
974c1c1 Trac #16807: Overflow error in conversion Integer -
FiniteFieldElement_pari_ffelt
7d50824 Trac #16794:
On Friday, August 15, 2014 6:25:05 AM UTC+1, kcrisman wrote:
That's silly, especially because often someone else writes your name and
in the deluge of tickets it's hard.
Is it? This discussion crops up every time after a release. I'd rather fix
a Math bug than hand-edit different spellings
Whats the origin remote? See output of git remote -v. If it is your own
repo (github fork, e.g.) then you'll have to push 6.3 there yourself.
On Friday, August 15, 2014 6:32:41 AM UTC+1, kcrisman wrote:
See the develop git branch or the source tarball at
Get the new develop git branch or download the source tarball at
http://boxen.math.washington.edu/home/release/sage-6.4.beta1.tar.gz
Mini-changelog:
c629c44 Trac #16842: Add crossreference to degree in order for a
permutation group
5722f34 Trac #16667: Random failure in polynomial_element.pyx
Please post the config.log from inside the gcc build dir.
On Wednesday, August 27, 2014 4:34:05 PM UTC+1, Samuel Lelievre wrote:
From: Volker Braun
Subject: Sage 6.3 released
Thanks! On Mac OS X 10.10 Yosemite Public Beta 2
(released last Friday, 2014-08-21), building Sage 6.3 fails
:46 GMT+02:00 Volker Braun:
Thats not the right config.log, the error was in the libgcc
subdirectory.
Changed:
http://www.math.u-psud.fr/~lelievre/t/config.log.tgz
(it's now the config.log file which I found in the directory
sage-6.3/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc
Git develop branch.
Source
tarball: http://boxen.math.washington.edu/home/release/sage-6.4.beta2.tar.gz
Mini-changelog:
95c1030 Trac #16890: Wrong argument name in class
FreeQuadraticModule_submodule_with_basis_field
12080c3 Trac #16886: Add PARI's idealchinese function to Sage
124f9bc Trac
SAGE_INSTALL_GCC is not set
I'll add it to the buildbot config.
On Saturday, August 30, 2014 9:15:23 AM UTC+1, Jeroen Demeyer wrote:
Are all Sage binaries still built with
SAGE_FAT_BINARY=yes and SAGE_INSTALL_GCC=yes?
I am asking because of
The develop git branch has been updated. Alternatively,
download http://boxen.math.washington.edu/home/release/sage-6.4.beta3.tar.gz
Mini-changelog:
c1cc800 Trac #16912: Upgrade Cython to 0.21
01ab218 Trac #16945: Switch buckygen package to sage-git directory layout
8aa4263 Trac #16944: GF(q) -
This happened once before at http://trac.sagemath.org/ticket/15915,
apparently the fix was not sufficient. Can you
I've created http://trac.sagemath.org/ticket/16968 for this issue, can you
add a description about your machine there?
On Thursday, September 11, 2014 4:04:04 PM UTC+1, Ralf
On Thursday, September 18, 2014 3:00:41 PM UTC+1, Samuel Lelievre wrote:
typedef void (^dispatch_block_t)(void);
^
/usr/include/dispatch/object.h:362:3: error: unknown type name
That header is Objective-C, which should never have been included when
compiling C sources.
This is some more fallout from #16858. Jeroen, do you already have a
followup ticket for numerical noise?
On Saturday, September 27, 2014 9:51:46 PM UTC+1, Justin C. Walker wrote:
On Sep 27, 2014, at 07:51 , Volker Braun wrote:
As usual, get the updated develop git branch. Alternatively
On Sunday, September 28, 2014 5:54:23 PM UTC+1, Stein William wrote:
Also, all those by default warning slow doctests things in the log
(on doing make ptestlong) are annoying...
Good, I hope somebody will clean up some of the unnecessarily long doctests
--
You received this message
to timeouts, making it unnecessarily difficult to use
SAGE_DEBUG.
On Sunday, September 28, 2014 8:45:52 PM UTC+1, Stein William wrote:
On Sun, Sep 28, 2014 at 11:49 AM, Volker Braun vbrau...@gmail.com
javascript: wrote:
On Sunday, September 28, 2014 5:54:23 PM UTC+1, Stein William wrote
of my depth
here... Do you need a build log ? If so, I'd start afresh : my install.log
is currently 26 Mb long...
HTH,
--
Emmanuel Charpentier
Le samedi 27 septembre 2014 16:51:26 UTC+2, Volker Braun a écrit :
As usual, get the updated develop git branch. Alternatively,
self-contained
I made #17071 for that issue.
On Monday, September 29, 2014 10:00:03 PM UTC+1, Volker Braun wrote:
I've seen that sporadically on the buildbot recently. But I haven't been
able to track it down. make distclean make fixes it.
On Monday, September 29, 2014 9:51:28 PM UTC+1, Emmanuel
On Tuesday, September 30, 2014 11:37:04 AM UTC+1, Jeroen Demeyer wrote:
But it wrongly assumes that doctest time scales linearly with computer
speed.
Sure. At the end of the day, it is basically impossible to predict how long
a piece of code is going to take to run on a modern computer
Workaround:
mkdir -p local/share/sage/ext/valgrind
make
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to
Thats already fixed, I'll just release a beta6 shortly.
On Monday, October 13, 2014 12:11:01 AM UTC+1, François wrote:
Volker are you pushing to develop already? Reverting
the valgring update?
Francois
--
You received this message because you are subscribed to the Google Groups
Quick update mainly to fix the Python compilation issue.
Git develop branch or
http://sage.sagedev.org/home/release/sage-6.4.beta6.tar.gz
Mini-changelog:
36c150e Updated Sage version to 6.4.beta6
67235a8 Trac #17144: Update to flint-2.4.4
7fd6e66 Trac #17145: Tornado depends on setuptools
Notable changes are
* OSX 10.10 support
* SageNB now can do 3d plots without Java, so it is usable again in chrome.
Please test, especially if you are a notebook user!
As usual, pull the develop git branch or download the self-contained
tarball
/samuel.lelievre/t/20141030_osx109_s64rc0_install.log.tgz
http://carva.org/samuel.lelievre/t/20141030_osx109_s64rc0_logs_pkgs_config.log.tgz
http://carva.org/samuel.lelievre/t/20141030_osx109_s64rc0_logs_pkgs_gcc491p0.log.tgz
2014-10-30 15:12 GMT+01:00 Volker Braun vbrau...@gmail.com javascript
Can you post the log for the failed ecm compile? GCC 4.6 is a bit old in
the tooth now, of course...
On Friday, October 31, 2014 12:24:47 PM UTC, Dima Pasechnik wrote:
On 2014-10-30, Volker Braun vbrau...@gmail.com javascript: wrote:
--=_Part_742_1112049983.1414678340265
Content-Type
Fix is in http://trac.sagemath.org/ticket/1726
http://trac.sagemath.org/ticket/17262#comment:152
On Friday, October 31, 2014 12:24:47 PM UTC, Dima Pasechnik wrote:
building on Ubuntu 12.04 on an i7 Intel (that's my
new Dell laptob, shipped with Ubuntu (!)) runs into trouble at ECM
Yes!
On Friday, October 31, 2014 2:56:44 PM UTC, Dima Pasechnik wrote:
doctest failures in ipython_notebook related to its dependence on
ssl. Should the corresponding (long) tests (9 out of 18) be marked as
optional?
--
You received this message because you are subscribed to the Google
http://trac.sagemath.org/ticket/17268
On Friday, October 31, 2014 8:33:19 PM UTC, kcrisman wrote:
Bizarrely, after earlier today having things working fine, now I
unaccountably have the old notebook. I did sage -f sagenb several times
(and it unpacked the correct one) but no idea what
On Saturday, November 1, 2014 9:31:26 AM UTC, Jeroen Demeyer wrote:
On 2014-10-30 15:12, Volker Braun wrote:
* SageNB now can do 3d plots without Java, so it is usable again in
chrome.
For me, this upgrade breaks 3D graphics to some extent:
When issuing the command cube(viewer=jmol) using
This is the second release candidate. Most important fixes are easy_install
sometimes activating the wrong version and some more changes to the gcc
package to perhaps get it to build even if homebrew is present (untested,
though). Please give it a whirl and report back!
As usual, pull the
Virtual Machine image:
http://boxen.math.washington.edu/home/vbraun/vm/sage-6.4.rc1.ova
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
#17278
On Sunday, November 2, 2014 7:54:59 PM UTC, William Stein wrote:
On Sat, Nov 1, 2014 at 3:52 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
This is the second release candidate. Most important fixes are
easy_install
sometimes activating the wrong version and some more
On Monday, November 3, 2014 1:58:40 PM UTC, kcrisman wrote:
sage: sphere(viewer='tachyon') # fine in 6.3, for some reason gives a Jmol
in 6.4 rc0
How is that even consistent with the rest of the graphics framework? There
is no plot(sin, viewer='svg'). However sphere().show(viewer='tachyon')
Also, what is the expected result of
sage: sphere(viewer='tachyon').show(viewer='jmol')
On Monday, November 3, 2014 2:18:56 PM UTC, Volker Braun wrote:
On Monday, November 3, 2014 1:58:40 PM UTC, kcrisman wrote:
sage: sphere(viewer='tachyon') # fine in 6.3, for some reason gives a
Jmol
On Sunday, November 2, 2014 5:10:19 AM UTC, Clemens Heuberger wrote:
$ /local/sage/sage-6.3/sage -n directory='sage.sagenb'
Traceback (most recent call last):
...
File string, line 1
notebook(directory=rsage.sagenb)
^
1 - 100 of 813 matches
Mail list logo
