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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
), 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
801 - 820 of 820 matches
Mail list logo
