[sage-release] Sage-6.1.beta6 released

2014-01-20 Thread Volker Braun
Use either the "develop" branch or the source tarball at http://boxen.math.washington.edu/home/release/sage-6.1.beta6/sage-6.1.beta6.tar.gz Changelog overview: $ git rlog HEAD ^6.1.beta5 6111e51 Trac #15462: Fix phi for general tensor product of crystals aeace92 Trac #15546: Maxima build hangs o

Re: [sage-release] Re: Binary tarballs for Sage 6.0

2014-01-20 Thread Samuel Lelièvre
Here is what I think should be fixed in the sage_bdist_osx function: to produce the non-app version, set SAGE_APP_BUNDLE and SAGE_APP_DMG to 'no'; then to produce the app version, set SAGE_APP_BUNDLE and SAGE_APP_DMG to 'yes'. Best, Samuel -- You received this message because you are subscribed

[sage-release] Re: Sage 6.0 released

2014-01-20 Thread Volker Braun
Just to answer my own question, src/sage/combinat/root_system/coxeter_group.py calls gap3 if it finds one in the path. So there is the reason. It seems that Georg's gap3 install is broken, which is outside of our control. As a workaround, remove /usr/local64.hg/bin from the path before running

[sage-release] Re: Sage 6.0 released

2014-01-20 Thread Volker Braun
I'm willing to bet that gap3 is a shell script that runs gap-static-linux-i686 under the hood. The question is, who is calling gap3? On Monday, January 20, 2014 9:09:50 PM UTC, Simon King wrote: > > Also no surprise, since the local Sage-version of GAP is called gap and > not gap3. > -- Yo

[sage-release] Re: Sage 6.0 released

2014-01-20 Thread Simon King
Hi Georg, On 2014-01-20, Georg Grafendorfer wrote: > (sage-sh) ggeorg@maschke:ggeorg$ which gap > /scratch/userdata/.software/sage/local/bin/gap This is expected: Sage will use its own GAP version, and is supposed to totally ignore the other GAP installations in the system. > (sage-sh) ggeorg@m

[sage-release] Re: Binary tarballs for Sage 6.0

2014-01-20 Thread Hayden Stainsby
I don't really know how the config works, but I don't see any reason why it would be producing doubles of Sage.app build. I do have a mac I can try the build on, is there anything I can do to test this out? Hayden On Friday, 17 January 2014 18:17:28 UTC+1, Volker Braun wrote: > > I changed the

[sage-release] Re: Sage 6.0 released

2014-01-20 Thread Georg Grafendorfer
Hi Simon, sorry for the delay, here is the (different) answer: ggeorg@maschke% sage -sh Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything with other copies of Sage on your system. * Do not use this for installing Sage p