[sage-release] Re: Sage 8.0.beta1 released

2017-04-12 Thread Adam Webb
Hi, I don't know if my set-up is somehow different but I have a problem while building installing brial. This occurs with 7.6 as well as 8.0 beta.1 During the check stage I get the following. [brial-0.8.5] checking whether /sage-8.0.beta1/local/var/lib/sage/installed/python2-2.7.13.p0

[sage-release] Re: Sage 8.0.beta1 released

2017-04-10 Thread Rebecca Miller
I fixed the problem, my Fetch head was connected to a previous ticket I had written. I just needed to reset it to trac/develop. Thanks, Rebecca On Thursday, April 6, 2017 at 2:55:55 PM UTC-5, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git >

Re: [sage-release] Re: Sage 8.0.beta1 released

2017-04-10 Thread John H Palmieri
On Sunday, April 9, 2017 at 12:03:03 AM UTC-7, Jeroen Demeyer wrote: > > On 2017-04-08 14:23, Eric Gourgoulhon wrote: > > make ptestlong created > > an empty directory "home" in SAGE_ROOT > > That's an old issue. I never investigated where that "home" came from. > I finally tracked that

Re: [sage-release] Re: Sage 8.0.beta1 released

2017-04-10 Thread Dima Pasechnik
Could it be that you are behind a firewall that blocks git:// port? (we have seen this several times...) Switch to https or ssh. -- 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,

Re: [sage-release] Re: Sage 8.0.beta1 released

2017-04-09 Thread Rebecca Miller
git remote -v says {trac git://trac.sagemath.org/sage.git (fetch) trac g...@trac.sagemath.org:sage.git (push)} On Sun, Apr 9, 2017 at 2:55 AM, Dima Pasechnik wrote: > > > On Sunday, April 9, 2017 at 12:06:15 AM UTC+1, Rebecca Miller wrote: >> >> Hi Volker, >> >> I'm

[sage-release] Re: Sage 8.0.beta1 released

2017-04-09 Thread Dima Pasechnik
On Sunday, April 9, 2017 at 12:06:15 AM UTC+1, Rebecca Miller wrote: > > Hi Volker, > > I'm unable to pull this new version using git. Has anyone else had a > similar problem? Worked for me. From where are you pulling, and how? what does your git remote -v say? > > > Thanks, >

Re: [sage-release] Re: Sage 8.0.beta1 released

2017-04-09 Thread Jeroen Demeyer
On 2017-04-08 14:23, Eric Gourgoulhon wrote: make ptestlong created an empty directory "home" in SAGE_ROOT That's an old issue. I never investigated where that "home" came from. as well as two files: __home_eric__sage_temp_manifold_6686_dir_R1ZgOC_src_pyx.cpp

[sage-release] Re: Sage 8.0.beta1 released

2017-04-08 Thread Rebecca Miller
Hi Volker, I'm unable to pull this new version using git. Has anyone else had a similar problem? Thanks, Rebecca Miller -- 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

[sage-release] Re: Sage 8.0.beta1 released

2017-04-08 Thread Eric Gourgoulhon
Le samedi 8 avril 2017 13:58:58 UTC+2, Eric Gourgoulhon a écrit : > > From a fresh git clone + pull develop on Ubuntu 16.04 x86_64 i7-6700HQ + > 16 MB RAM, parallel (-j8) build OK and make ptestlong successful. > I've noticed a difference w.r.t. sage 8.0.beta0: make ptestlong created an empty

[sage-release] Re: Sage 8.0.beta1 released

2017-04-07 Thread John H Palmieri
With a clean tarball, "./sage -i PKG" fails: Error: You must set either the SAGE_LOCAL or SAGE_SCRIPTS_DIR environment variable to run this Error setting environment variables by sourcing '/Users/palmieri/Desktop/TEMP/sage-8.0.beta1/src/bin/sage-env'; possibly contact sage-devel (see