Re: [sage-release] Re: Sage 10.2.beta3 released

[kcrisman]

On Saturday, September 23, 2023 at 10:07:24 PM UTC-4 John H Palmieri wrote:

Building Sage's own gfortran worked to build scipy (and this is an argument 
to keep the gfortran package around, by the way).



I just successfully upgraded Sage only by doing this as well.  The homebrew 
scipy is a newer version, fwiw.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6770e52d-1e1c-483d-8c1b-faae64854129n%40googlegroups.com.

Re: [sage-release] Sage 10.0.rc0 released

[kcrisman]

On Wednesday, April 26, 2023 at 5:32:27 AM UTC-4 sage-goo...@lma.metelu.net 
wrote:

Hi, 

Sage's current openssl version (3.0.5) hass several "High severity" 
vulnerabilities, see https://www.openssl.org/news/vulnerabilities.html 

It would be nice to have the fixes included in the next Sage release.


Thanks for noting this! 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/541c1472-1ba8-4129-ab67-7463eb229cfdn%40googlegroups.com.

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

[kcrisman]

> could you try to re-install R, and check what you see in the log? 
> (i.e. "Package 'r' is currently not installed" would be wrong message, 
> I suppose, I'd rather see something about "uninstalling") 
>
>
I would too, but:

[r-3.6.2.p0] Package 'r' is currently not installed

[r-3.6.2.p0] No legacy uninstaller found for 'r'; nothing to do

It otherwise installs fine, though. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9ab52802-2146-45a6-9167-64b74f890cb0o%40googlegroups.com.

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

[kcrisman]

>
>
> Otherwise it's a bug. 
>
>
I was not using a system package for R.  While Matthias' link may 
conceivably be relevant as well, I'm currently leaning toward the other 
option.  On the old run (upgrading R) I have in the log the first time 
(unsuccessful):

Warning: No files to uninstall for 'r'
Uninstalling existing 'r'


While on the second (unsuccessful) and most recent (successful) run I see:

Package 'r' is currently not installed

No legacy uninstaller found for 'r'; nothing to do

Perhaps that helps someone who understands the uninstaller logic - that 
came after I had to stop keeping track of build system developments.
 

> On Linux I see 
> $ grep libR local/var/lib/sage/installed/r-3.6.2.p0 
> "lib/R/lib/libR.so", 
> "lib/pkgconfig/libR.pc", 
>
>
>
It's the Mac equivalent.  (I don't think any system packages are used for 
my install, or very few.)  Unfortunately I don't have the state before this 
upgrade any more.

$ grep libR local/var/lib/sage/installed/r-3.6.2.p0 

"lib/R/lib/libR.dylib",
"lib/pkgconfig/libR.pc", 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/161201ad-43ba-4f12-b917-6617d111b89bo%40googlegroups.com.

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

[kcrisman]

> mkdir ../../../../library/tools/libs
>
> installing 'sysdata.rda'
>
> dyld: Library not loaded: 
> /Users/.../sage/local/lib/libopenblas_haswellp-r0.3.6.dylib
>
>   Referenced from: /Users/.../sage/local/lib/R/lib/libR.dylib
>
>
For reference, doing

$ rm -rf local/lib/R/

ended up solving the problem.  But that seems like a bug - shouldn't the 
previous R install properly be deleted, in our current paradigm of first 
uninstalling (if I understand it correctly)?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f50588d7-2094-498a-870c-b63716e105d3o%40googlegroups.com.

[sage-release] Re: Sage 9.1 released

[kcrisman]

> Binaries are now on their way to the mirrors!
>>
>
> Thanks. What about the binaries for Windows? Some users are asking for 
> them on ask.sagemath and apparently, they are not yet on the mirrors.
>

Still not on the mirrors, or Github pages as 
https://www.sagemath.org/download.html implies they should be.  Presumably 
they haven't been created yet.

See also https://github.com/sagemath/website/issues/198 - which is simply a 
"current status" issue, not a "complaining" issue.  Goodness knows just 
keeping Sage up-to-date is a big job, much less producing binaries.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a9969806-0632-4114-aea5-ffee0619cea0o%40googlegroups.com.

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

[kcrisman]

On Mac OS X 10.11.  Upgrading via git pull trac develop and make from 
somewhere in the 9.0 betas, I get a lot of good things, until:

mkdir ../../../../library/tools/libs

installing 'sysdata.rda'

dyld: Library not loaded: 
/Users/.../sage/local/lib/libopenblas_haswellp-r0.3.6.dylib

  Referenced from: /Users/.../sage/local/lib/R/lib/libR.dylib

  Reason: image not found

/bin/bash: line 1: 24759 Doneecho 
"tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"

 24760 Trace/BPT trap: 5   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
R_ENABLE_JIT=0 TZ=UTC ../../../bin/R --vanilla --slave

make[8]: *** [sysdata] Error 133

make[7]: *** [all] Error 2

make[6]: *** [R] Error 1

make[5]: *** [R] Error 1

make[4]: *** [R] Error 1



Error building r-3.6.2.p0




real2m5.131s

user0m47.882s

sys 0m46.001s



Error installing package r-3.6.2.p0




$ ls local/lib/libopenblas[tab]

libopenblas.0.dyliblibopenblas.dylib  
libopenblas_haswellp-r0.3.9.dylib  


So I'm not sure why it's asking for an older version of libopenblas.  Full 
R log at http://www.math.gordon.edu/~kcrisman/r-3.6.2.p0.log

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/46fe726e-0808-4a2e-a1de-e1aa3b361289o%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

On Thursday, May 28, 2020 at 5:55:10 PM UTC-4, Justin C. Walker wrote:
>
>
>
> > On May 20, 2020, at 15:53 , Volker Braun  > wrote: 
> > 
> > The "master" git branch has been updated to Sage-9.1. As always, you can 
> get the latest beta version from the "develop" git branch. Alternatively, 
> the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
> Finally got back to this.  Why being locked down full-time reduces time 
> available to do this stuff is beyond me… 
>
> As mentioned earlier, there were no problems with my 10.13 and 10.15 
> systems (2017 iMac Pro, 18-core Xeon W, and 2019 MBP, 9-core Core i9, 
> respectively): build and tests (‘ptestlong’) all completed without 
> problems. 
>

Justin, just FYI looks like we could probably use a 10.13 or 10.14 binary, 
thus far the only ones are 10.11 and 10.15 - if that is something you are 
interested in (and Volker agrees, which I assume he would).  I don't know 
if we have any binarybot for that.  Very glad the whole mirror situation 
got resolved for you. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/eee130fb-3a52-4eab-b3dd-85f7f9ba20d2%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

On Saturday, May 23, 2020 at 2:44:04 PM UTC-4, Matthias Köppe wrote:
>
> For debugging this, please note that this is executed using 
> build/bin/sage-system-python, which is not necessarily the same as ./sage 
> -python.
>
>>
>>

Interesting.  In which case my system Python is always py2.  Here is 
another data point, from a Python 3 build (hopefully zooming to mirrors 
soon).  urllib doesn't like 

$ ./build/bin/sage-system-python 

Python 2.7.10 (default, Oct 23 2015, 19:19:21) 

[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.5)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> import urllib

>>> eval(urllib.urlopen('http://www.sagemath.org/mirror_list').read())

Traceback (most recent call last):

  File "", line 1, in 

  File "", line 1

error code: 1010

 ^

SyntaxError: invalid syntax

>>> urllib.urlopen('http://www.sagemath.org/mirror_list').read()

'error code: 1010'

$ ./sage -python

Python 3.7.3 (default, May 23 2020, 09:48:14) 

[Clang 7.3.0 (clang-703.0.31)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> import urllib

>>> eval(urllib.urlopen('http://www.sagemath.org/mirror_list').read())

Traceback (most recent call last):

  File "", line 1, in 

AttributeError: module 'urllib' has no attribute 'urlopen'

>>> urllib.urlopen('http://www.sagemath.org/mirror_list').read()

Traceback (most recent call last):

  File "", line 1, in 
AttributeError: module 'urllib' has no attribute 'url open' 


>From https://docs.python.org/3/library/urllib.request.html: The legacy 
urllib.urlopen function from Python 2.6 and earlier has been discontinued; 
urllib.request.urlopen() 
 
corresponds 
to the old urllib2.urlopen.

Note that 
https://github.com/sagemath/sage/blob/4427340fcd58c915e9b803cb5fbc8e720a8c335c/build/sage_bootstrap/download/mirror_list.py#L179
 
still has one instance of this function 
while 
https://github.com/sagemath/website/blob/785f16e785721e51e1c222bbb2e17d5dcc54cb07/scripts/mirror_manager.py#L456
 
has some references to this which is presumably where I got it from.

But in any case that is the error.  Conceivably relevant: 
* https://twitter.com/scottmmjackson/status/1215639072464613377
I tried to trace it further but I just don't have time to do so, as it 
really starts to require messing with the entire mirror list module and I 
mainly just wanted to build binaries.  But I think these things should be 
looked into, especially the implied (if not actual) use of urllib.urlopen.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d9107cc6-23ee-45a0-a106-71f395415d5c%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

> >  CRITICAL [mirror_list|_load:91]: Downloaded mirror list has syntax 
> error: error code: 1010 
> > 
> > 
> https://github.com/sagemath/sage/blob/develop/build/sage_bootstrap/download/mirror_list.py#L91
>  
> Hi, 
>
> could you debug this? What's the value of mirror_list just before 
>
> https://github.com/sagemath/sage/blob/4427340fcd58c915e9b803cb5fbc8e720a8c335c/build/sage_bootstrap/download/mirror_list.py#L89
>  
>
> Dima 
>

As the error above indicates, I got "error code: 1010" and I was able to 
confirm this via a print statement in a different Sage build by doing sage 
-i bliss after removing the mirror list.  Replacing the mirror list and 
bliss installed fine.

I can confirm this another way using the syntax provided in the actual file 
in comments.  Could this be a Python 2 v 3 issue?  I don't really 
understand why it would return this error code.

$ ./sage -python

Python 2.7.15 (default, May 21 2020, 11:09:06) 

[GCC 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> import urllib

>>> eval(urllib.urlopen('http://www.sagemath.org/mirror_list').read())

Traceback (most recent call last):

  File "", line 1, in 

  File "", line 1

error code: 1010

 ^

SyntaxError: invalid syntax

>>> urllib.urlopen('http://www.sagemath.org/mirror_list').read()

'error code: 1010'
 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/86c68ace-ae07-4981-93c3-dc47dc99df22%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

On Saturday, May 23, 2020 at 1:40:13 AM UTC-4, Justin C. Walker wrote:
>
>
>
> > On May 22, 2020, at 21:41 , Matthias Köppe  > wrote: 
> > 
> > On Friday, May 22, 2020 at 6:54:01 PM UTC-7, kcrisman wrote: 
> > Justin 
> > 
> > $ make -j6 build/make/Makefile --stop 
> > ./bootstrap -d 
> > rm -rf config configure build/make/Makefile-auto.in 
> > rm -f src/doc/en/installation/*.txt 
> > src/doc/bootstrap:48: installing src/doc/en/installation/arch.txt and 
> src/doc/en/installation/arch-optional.txt 
> > src/doc/bootstrap:48: installing src/doc/en/installation/debian.txt and 
> src/doc/en/installation/debian-optional.txt 
> > src/doc/bootstrap:48: installing src/doc/en/installation/fedora.txt and 
> src/doc/en/installation/fedora-optional.txt 
> > src/doc/bootstrap:48: installing src/doc/en/installation/cygwin.txt and 
> src/doc/en/installation/cygwin-optional.txt 
> > src/doc/bootstrap:48: installing src/doc/en/installation/homebrew.txt 
> and src/doc/en/installation/homebrew-optional.txt 
> > gettext and the gettextize program must be installed and be in 
> > your PATH. E.g. Homebrew installs them in /usr/local/opt/gettext/bin. 
> > Bootstrap failed, downloading required files instead. 
> > Attempting to download package 
> configure-765c5cb3e24dd134708eca97e4c52e0221cd94ba.tar.gz from mirrors 
> > Downloading the Sage mirror list 
> > CRITICAL [mirror_list|_load:91]: Downloaded mirror list has syntax 
> error: error code: 1010 
> > Searching fastest mirror 
> > ERROR [mirror_list|_rank_mirrors:145]: Could not reach any mirror 
> directly and no proxy set 
> > 
> > I just got exactly the same error, from within binary-pkg.  Same issue 
> that I definitely had internet because binary-pkg just got everything from 
> the git repo before this happened.   Did anyone find a fix or even 
> diagnosis? 
>
> So far, it appears not. 
>
> > I don't know what's going on with the mirror list, but you can avoid 
> this particular download by installing autotools (see 
> build/pkgs/*-bootstrap.txt for the details). 
>
> Any clue why this would afflict 10.14 (after success building 9.1.rc5), 
> but not 10.13 and 10.15? 
>

I have a feeling it's more to do with when you try it, or maybe even 
network issues.

The error seems to indicate that there is an error of some kind of in 
downloading.  Some stuff online suggests error code 1010 is a blocked URL?

 CRITICAL [mirror_list|_load:91]: Downloaded mirror list has syntax error: 
error code: 1010

https://github.com/sagemath/sage/blob/develop/build/sage_bootstrap/download/mirror_list.py#L91

Anyway, what I did as a workaround was to manually copy the contents 
of http://www.sagemath.org/mirror_list into the 
file 
source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidmas391y/upstream/mirror_list
 
(your filename will obviously be different).  But that is not a long-term 
solution, and I'm otherwise baffled.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e6b9ab09-b9c5-4d75-8a2b-01b55fa02a88%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

>
> Justin 
>
> $ make -j6 build/make/Makefile --stop 
> ./bootstrap -d 
> rm -rf config configure build/make/Makefile-auto.in 
> rm -f src/doc/en/installation/*.txt 
> src/doc/bootstrap:48: installing src/doc/en/installation/arch.txt and 
> src/doc/en/installation/arch-optional.txt 
> src/doc/bootstrap:48: installing src/doc/en/installation/debian.txt and 
> src/doc/en/installation/debian-optional.txt 
> src/doc/bootstrap:48: installing src/doc/en/installation/fedora.txt and 
> src/doc/en/installation/fedora-optional.txt 
> src/doc/bootstrap:48: installing src/doc/en/installation/cygwin.txt and 
> src/doc/en/installation/cygwin-optional.txt 
> src/doc/bootstrap:48: installing src/doc/en/installation/homebrew.txt and 
> src/doc/en/installation/homebrew-optional.txt 
> gettext and the gettextize program must be installed and be in 
> your PATH. E.g. Homebrew installs them in /usr/local/opt/gettext/bin. 
> Bootstrap failed, downloading required files instead. 
> Attempting to download package 
> configure-765c5cb3e24dd134708eca97e4c52e0221cd94ba.tar.gz from mirrors 
> Downloading the Sage mirror list 
> CRITICAL [mirror_list|_load:91]: Downloaded mirror list has syntax error: 
> error code: 1010 
> Searching fastest mirror 
> ERROR [mirror_list|_rank_mirrors:145]: Could not reach any mirror directly 
> and no proxy set 


I just got exactly the same error, from within binary-pkg.  Same issue that 
I definitely had internet because binary-pkg just got everything from the 
git repo before this happened.   Did anyone find a fix or even diagnosis?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/064012a5-3f2f-461a-8e6e-848f649a913b%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

 Anyway, I'd like to (if possible) build one last py2 binary that way for 
>> the mirrors
>>
>
> +1. We should definitely have py2 binaries of 9.1. 
>

Do you understand how binary-pkg works well enough to give advice as to 
whether just adding a configure line to the yaml file would suffice to do 
this? 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/72f5796b-5c56-4f58-9748-30aad55d0533%40googlegroups.com.

Re: [sage-release] Sage 9.1 released

[kcrisman]

Built from scratch on OS X 10.11 with Py2, passed all (normal) tests except 
two 3d plot files timed out, those passed second time by themselves.  Sage 
is robust!

Volker, would it be fairly easy to pass something in the yaml file for the 
binary-pkg to build a binary for Python 2?  I note that the build target 
doesn't include "./configure".  I'm hesitant to mess with it though since 
there are a lot of moving parts.

Unfortunately that py2/3 distinction wouldn't make it into the name. 
 Anyway, I'd like to (if possible) build one last py2 binary that way for 
the mirrors, and then also build a py3 binary (assuming I don't run out of 
disk space, which has definitely been a problem of late due to old computer 
filling up) for 9.1.

Thanks!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f06fc77c-69a9-4866-99b8-d6319eada2af%40googlegroups.com.

[sage-release] Re: Sage 9.1 released

[kcrisman]

On Wednesday, May 20, 2020 at 6:53:54 PM UTC-4, Volker Braun wrote:
>
> The "master" git branch has been updated to Sage-9.1. As always, you can 
> get the latest beta version from the "develop" git branch. Alternatively, 
> the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> There was no change over 9.1.rc5
>

Brief note that http://www.sagemath.org/download-source.html still says 
9.0, that seems to be a template variable that hasn't updated yet. 
 http://www.sagemath.org/download-latest.html only has the rc versions, as 
expected. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b10abe0f-f759-4f9b-9d2f-de4d117131f7%40googlegroups.com.

[sage-release] Re: Sage 9.1 released

[kcrisman]

>
> I have updated https://wiki.sagemath.org/ReleaseTours/sage-9.1
>
>
I have to say I am very impressed by this.  It is actually organized - it 
really takes a gardener to steward things like that, and it's more work 
than people realize.  

>  
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/cc860562-2cea-4bb3-bd84-14ba1b873ccb%40googlegroups.com.

[sage-release] Re: Sage 9.1.rc1 released

[kcrisman]

> The external and oeis failures are copied below.
>
> Follow up at https://trac.sagemath.org/ticket/25536
>

I've added tickets for them, and to the list there.  Both should be pretty 
trivial to fix - unfortunately I just deleted my 9.1rc install to save disk 
space.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e5ee7ae9-760e-4eec-b060-107ff61ecff0%40googlegroups.com.

[sage-release] Re: Sage 9.1.rc1 released

[kcrisman]

On Thursday, April 23, 2020 at 6:02:11 PM UTC-4, kcrisman wrote:
>
>
>
>
> Built from scratch on OS X 10.11.6, using ./configure and then make.  I 
>>> suggest that https://doc.sagemath.org/html/en/installation/source.html 
>>> is incorrect in suggesting that Py3 is necessary to *build* Sage.
>>>
>>
>> You're right, this needs to be updated. Python 2 also works. I've opened 
>> https://trac.sagemath.org/ticket/29556 for updating the installation 
>> instructions.
>>
>>
> Great.  By the way, passes all (basic) tests, four files needed to be 
> rerun for timing out :-) 
>

And to be clear, this was the default setup - I didn't try to use Py2 for 
Sage itself:

$ ./sage -ipython
Python 3.7.3 (default, Apr 23 2020, 09:19:49)  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b4920bb5-5350-418d-a620-f44fa11eab3d%40googlegroups.com.

[sage-release] Re: Sage 9.1.rc1 released

[kcrisman]

Built from scratch on OS X 10.11.6, using ./configure and then make.  I 
>> suggest that https://doc.sagemath.org/html/en/installation/source.html 
>> is incorrect in suggesting that Py3 is necessary to *build* Sage.
>>
>
> You're right, this needs to be updated. Python 2 also works. I've opened 
> https://trac.sagemath.org/ticket/29556 for updating the installation 
> instructions.
>
>
Great.  By the way, passes all (basic) tests, four files needed to be rerun 
for timing out :-) 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6df6ee32-29c0-4ee0-9683-042e96836315%40googlegroups.com.

[sage-release] Re: Sage 9.1.rc1 released

[kcrisman]

Built from scratch on OS X 10.11.6, using ./configure and then make.  I 
suggest that https://doc.sagemath.org/html/en/installation/source.html is 
incorrect in suggesting that Py3 is necessary to *build* Sage.

Testing that Sage starts...

[2020-04-23 12:33:27] SageMath version 9.1.rc1, Release Date: 2020-04-22

Yes, Sage starts.


real 250m34.371s

user 483m50.050s

sys 96m20.518s

Sage build/upgrade complete!


$ python --version

Python 2.7.10

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/7a7f3e96-c4a2-48b3-829f-5f7d7032e974%40googlegroups.com.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

For a data point, I am currently trying to use binary-pkg to create a Sage 
9.0 binary for Mac, and ran into *exactly* the same issue - presumably 
because it (the version of Sage I had in binary-pkg, that is) had upgraded 
from 8.9.beta6 or so.  I guess it must have hit the window for not having 
this dist-helpers file around.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/ba22c736-0493-4c17-840c-3d2f4046a577%40googlegroups.com.

[sage-release] Re: Sage 9.0 released

[kcrisman]

On Wednesday, January 1, 2020 at 5:45:51 PM UTC-5, Emmanuel Charpentier 
wrote:
>
> Congratulations ! And atriple ban four the release manager, who managed to 
> get a Python 3-base Sage just in time. Kudos...
>
> Le mercredi 1 janvier 2020 13:15:15 UTC+1, Volker Braun a écrit :
>>
>> Just in time for the new decade,
>>
>
> Mandatory nitpick: the second decade of the 21ts century CE shall end on 
> Dec 31, 2020 23:59:59. As it has already been noted, there is no year 0 in 
> this calendar :
>
> https://xkcd.com/2249/ 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/5e7708bb-7157-4e15-894d-d81e490a7965%40googlegroups.com.

Re: [sage-release] Sage 9.0.beta4 released

[kcrisman]

By the way, building the Mac app with beta4 on Python 3 seems to have 
worked very nicely!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/eb28cb79-62fa-46cc-bdd6-e03d02c87303%40googlegroups.com.

[sage-release] Re: Sage 9.0.beta4 released

[kcrisman]

On Thursday, November 7, 2019 at 9:02:53 PM UTC-5, kcrisman wrote:
>
> And with Python 3 support on beta4 on Mac OS X 10.11.6, a single 
> verifiable doctest failure on ptestlong, of which only the first one is an 
> actual failure (the rest depend on it).  I note that if I run the first 
> test by hand, it not only works but A and B give the long name based on pid 
> and so forth correctly.
>
> 1 item had failures:
>4 of   8 in sage.misc.sageinspect._sage_getsourcelines_name_with_dot
> [339 tests, 4 failures, 18.87 s]
>

And 

cython('''cpdef test_funct(x,y): return''')
in  sage.misc.sageinspect.sage_getsourcelines seems to have similar issues, 
but not consistently - sometimes all tests in this file pass.  Maybe some 
kind of race condition?  Whether I use one or multiple threads does not 
seem to matter.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a0d6267c-1d20-4126-82b2-d6df028761ea%40googlegroups.com.

[sage-release] Re: Sage 9.0.beta4 released

[kcrisman]

And with Python 3 support on beta4 on Mac OS X 10.11.6, a single verifiable 
doctest failure on ptestlong, of which only the first one is an actual 
failure (the rest depend on it).  I note that if I run the first test by 
hand, it not only works but A and B give the long name based on pid and so 
forth correctly.

sage -t --long src/sage/misc/sageinspect.py
**
File "src/sage/misc/sageinspect.py", line 2132, in 
sage.misc.sageinspect._sage_getsourcelines_name_with_dot
Failed example:
cython('''
class A:
def __init__(self):
"some init doc"
pass
class B:
"some class doc"
class A(A):
pass
''')
Exception raised:
Traceback (most recent call last):
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 681, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1123, in compile_and_execute
exec(compiled, globs)
  File "", line 10, in 

''')
  File "sage/misc/lazy_import.pyx", line 353, in 
sage.misc.lazy_import.LazyImport.__call__ 
(build/cythonized/sage/misc/lazy_import.c:3686)
return self.get_object()(*args, **kwds)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/misc/cython.py",
 
line 599, in cython_compile
return cython_import_all(tmpfile, get_globals(), **kwds)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/misc/cython.py",
 
line 489, in cython_import_all
m = cython_import(filename, **kwds)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/misc/cython.py",
 
line 469, in cython_import
return builtins.__import__(name)
ModuleNotFoundError: No module named 
'_Users_...__sage_temp_GC06259_23216_tmp_lqbw2l0c_pyx_0'
**
File "src/sage/misc/sageinspect.py", line 2142, in 
sage.misc.sageinspect._sage_getsourcelines_name_with_dot
Failed example:
B.A.__name__
Exception raised:
Traceback (most recent call last):
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 681, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1123, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 

B.A.__name__
NameError: name 'B' is not defined
**
File "src/sage/misc/sageinspect.py", line 2144, in 
sage.misc.sageinspect._sage_getsourcelines_name_with_dot
Failed example:
B.A.__qualname__
Exception raised:
Traceback (most recent call last):
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 681, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1123, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 

B.A.__qualname__
NameError: name 'B' is not defined
**
File "src/sage/misc/sageinspect.py", line 2146, in 
sage.misc.sageinspect._sage_getsourcelines_name_with_dot
Failed example:
sage_getsource(B.A)
Exception raised:
Traceback (most recent call last):
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 681, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/Users/.../testpy3sage/sage-9.0.beta4-py3/sage-9.0.beta4/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1123, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 

sage_getsource(B.A)
NameError: name 'B' is not defined
**
1 item had failures:
   4 of   8 in sage.misc.sageinspect._sage_getsourcelines_name_with_dot
[339 tests, 4 failures, 18.87 s]

-- 
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 view this discussion on the web visit 

[sage-release] Re: Sage 9.0.beta4 released

[kcrisman]

FWIW  make ptestlong (though no optional packages)

--

All tests passed!

--

Total time for all tests: 10172.0 seconds

cpu time: 14976.0 seconds

cumulative wall time: 19701.3 seconds

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/2467c703-8d20-4e0f-af34-1c42d1b76fd7%40googlegroups.com.

[sage-release] Re: Sage 9.0.beta4 released

[kcrisman]

Okay, I just found https://trac.sagemath.org/ticket/28660 so sorry for the 
noise.  But I guess my comment about testers stands.
 

> I admit I haven't paid enough attention to the py3 switch on sage-devel, 
> but this still surprised me, based on the wording at 
> https://wiki.sagemath.org/Python3-compatible%20code  I suppose that when 
> the py3 switch for default is thrown, we should make sure to have a special 
> request for testing from the whole community to make sure we have no weird 
> regressions on py2 until after 9.1 (or that is what the Wiki currently 
> says).
>
> $ ./sage -v
>
> SageMath version 9.0.beta4, Release Date: 2019-11-02
>
> $ ./sage -python
>
> Python 2.7.15 (default, Nov  6 2019, 12:35:23) 
>
> [GCC 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31)] on darwin
>
> Type "help", "copyright", "credits" or "license" for more information.
>
> >>> 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/00d4a4cc-1b8e-4fd9-bbc7-66bd4c0102fc%40googlegroups.com.

[sage-release] Re: Sage 9.0.beta4 released

[kcrisman]

I admit I haven't paid enough attention to the py3 switch on sage-devel, 
but this still surprised me, based on the wording 
at https://wiki.sagemath.org/Python3-compatible%20code  I suppose that when 
the py3 switch for default is thrown, we should make sure to have a special 
request for testing from the whole community to make sure we have no weird 
regressions on py2 until after 9.1 (or that is what the Wiki currently 
says).

$ ./sage -v

SageMath version 9.0.beta4, Release Date: 2019-11-02

$ ./sage -python

Python 2.7.15 (default, Nov  6 2019, 12:35:23) 

[GCC 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e305effd-1f7f-4ff7-92ef-f6ce3d79ba7d%40googlegroups.com.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

>
> > This has also been reported on devel [1,2] and might affect more Mac 
> users when upgrading to 8.9. Perhaps a copy of sage-dist-helpers could be 
> added back to src/bin for some deprecation period? 
>
> A symlink could do it. 
>

Very nice sleuthing all around.  I do recommend something be done for that 
as a stopgap for an 8.9rc - presumably it should also be tested out.  But 
for people who do not regularly upgrade to betas, but do build from source, 
this would be quite helpful. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/fd053937-44e4-4ca8-9142-30b8af89ea49%40googlegroups.com.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

> That's expected.  The package build directory is under SAGE_LOCAL 
> ($SAGE_LOCAL/var/tmp/sage/build/gap-4.10.0.p0) but the file's 
> destination path ($SAGE_LOCAL) is appended to this.  This is how it's 
> supposed to work (DESTDIR installation). 
>
> It's probably too late to diagnose now (though it would be good if you 
> could give steps to reproduce). 


Yeah, unfortunately my main goal was getting a working Sage install, so the 
evidence has been eliminated, so to speak.
 

>  But the question is what type of file 
> was 
>
> /Users/karl.crisman/Downloads/sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src
>  
>
>
> that it refuses to overwrite because it was supposedly a directory? 
>


I can tell you a rough answer to that, after my most recent upgrade the 
name of the directory seems to have changed slightly though:

$ ls -l 
~/Downloads/sage/local/share/gap/bin/x86_64-apple-darwin15.6.0-default64-kv3/

total 32

lrwxr-xr-x  1 karl.crisman  78570554  18 Aug 14 14:39 config.h -> 
../../gen/config.h

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:39 gac -> ../../gac

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:39 gap -> ../../gap

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:40 src -> ../../src
 

>
> The GAP package installs a *symlink* at the path 
> $SAGE_LOCAL/share/gap/bin//src 
>
>
So yes, that is what seems to be happening.
 

> When you upgrade GAP, first of all, it should be *uninstalling* the 
> previous gap package, so this link should just be removed.  The 
> question is was it a symlink for you in the first place?


Apparently.
 

>  Or an actual 
> directory?  When you run `make clean-gap` does it get removed? 
>
>
Is that something I can do from within Sage?  I didn't know that was a make 
target for us.   My assumption is that the symlink was not removed or it 
wouldn't have complained.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/02c26f61-e386-4734-b239-79dcae96b476%40googlegroups.com.

Re: [sage-release] Sage 8.9.beta4 released

[kcrisman]

On Wednesday, July 31, 2019 at 6:52:04 PM UTC-4, Volker Braun wrote:
>
> I think the gap / gap_packages url confusion is because both reference the 
> same tarball file, we don't handle that case well I think.
>
> For the record, we had some networking issue on the fileserver. The 
> sagepad.org machine is not part of the mirror network but my personal 
> server and serves as fallback.
>
>
Just as a data point, I'm still having this issue right now.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e12ced8a-d159-4a77-949c-a4f2585d2fb2%40googlegroups.com.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

On Friday, March 8, 2019 at 8:18:02 AM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Mar 8, 2019 at 12:40 PM kcrisman > 
> wrote: 
> > 
> > 
> > 
> > On Friday, March 8, 2019 at 3:24:45 AM UTC-5, Dima Pasechnik wrote: 
> >> 
> >> https://trac.sagemath.org/ticket/27388 fixed the permissions, but 
> >> because it's an upgrade from the state where there was a read-only 
> >> file, it breaks (on OSX only) 
> > 
> > 
> > Would that mean that, in general, upgrades from beta4 (which seems to be 
> the last version without this problem, according to one of the tickets) via 
> git pull and make will break indefinitely?  Should we have a blanket 
> recommendation to rebuild from scratch? 
>
> this is too blanket :-) 
> e.g. in this particular case it suffices to manually remove 
> SAGE_LOCAL/share/gap 
> and rebuild gap spkg 
> (and then run make, naturally...) 
>

Weirdly, I had to do this again even after the update mentioned here 
(apparently going from 8.7.beta6 to 8.9.beta6).   Is this likely to happen 
every time we upgrade GAP?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a06cf450-3b21-44de-be6b-b870dd27d64a%40googlegroups.com.

Re: [sage-release] Sage 8.7.beta5 released

[kcrisman]

Thanks, that is helpful - and a different error than what I got.  I gave 
the gist of this to the relevant sage-devel thread, thank you!
 

> >> 
> >> Justin, just to try for another data point for 
> https://groups.google.com/forum/#!topic/sage-devel/pNvpzOH4e1Q could you 
> try running the optional internet tests as well for this one?  Just running 
> --optional=sage,internet on one file, e.g. src/sage/databases/oeis.py 
> should suffice to test this out.  Thanks! 
> > 
> > Did that, with attached results (146 failures).  Why would “https” be an 
> unknown URL type. 
> > 
> > I ran this on two of the systems: 10.11.6 (MBP) and 10.13.6 (iMac Pro). 
>
> And the results: same failures (as in the now-attached log).  Too much 
> coffee, I suspect. 
>
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.7.beta5 released

[kcrisman]

Justin, just to try for another data point 
for https://groups.google.com/forum/#!topic/sage-devel/pNvpzOH4e1Q could 
you try running the optional internet tests as well for this one?  Just 
running --optional=sage,internet on one file, 
e.g. src/sage/databases/oeis.py should suffice to test this out.  Thanks!


>
> Built w/o problems on three macOS platforms from a fresh clone of the 
> develop tree. 
>
> 10.11.6 (mid-2015 MBP, Quad-core Core i7): all tests passed! 
>
> 10.13.6 (2017 iMac Pro, 18-core Xeon W): all tests passed! 
> However, repeating the “loop” testing of polynomials.pyx showed the same 
> intermittent failures as before (this failure occurred in 4 of 8 tests). 
>
> 10.14.2 (2017 MBP, Quad-core Core i7): one testing failure: 
> sage -t --long --warn-long 77.8 
> src/sage/numerical/backends/logging_backend.py  # Killed due to abort 
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

> this is too blanket :-) 
> e.g. in this particular case it suffices to manually remove 
> SAGE_LOCAL/share/gap 
> and rebuild gap spkg 
> (and then run make, naturally...) 
>
>
Great, thanks!  Apparently that sufficed.
 

> Certainly there is never a guarantee that a "git pull"+"make" would 
> just work, as 
> the current state could be beyond repair... 
>
>
Yes, of course!  In this case I had a working Sage install at beta1 or 
beta2, though.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

On Friday, March 8, 2019 at 3:24:45 AM UTC-5, Dima Pasechnik wrote:
>
> https://trac.sagemath.org/ticket/27388 fixed the permissions, but 
> because it's an upgrade from the state where there was a read-only 
> file, it breaks (on OSX only) 
>

Would that mean that, in general, upgrades from beta4 (which seems to be 
the last version without this problem, according to one of the tickets) via 
git pull and make will break indefinitely?  Should we have a blanket 
recommendation to rebuild from scratch?  Thanks for any advice here - 
luckily from testing the app version I have some still working Sage 
installs, but I like having my devel version separately working.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.7.beta6 released

[kcrisman]

upgrading from some early 8.6 beta, I get something weird with file 
permissions on gap.  Everything seems to go well, but:



pkg/laguna-3.9.0 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

pkg/polenta-1.3.8 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

pkg/polycyclic-2.14 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

pkg/resclasses-4.7.1 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

pkg/sophus-1.24 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

pkg/tomlib-1.2.7 -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg

../gap -> 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/bin/gap


real 2m48.230s

user 1m30.082s

sys 0m59.461s

Copying package files from temporary location 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst to 
/Users/.../sage/local

cp: cannot overwrite directory 
/Users/.../sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src 
with non-directory 
/Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src

cp: /Users/.../sage/local/./share/gap/pkg/ctbllib/tst/docxpl.tst: 
Permission denied



Error copying files for gap-4.10.0.p0.




I have a feeling that there is a typo of some kind in the commit 


https://github.com/sagemath/sage/commit/ca94bd97d73ee544c273fbb28cb774b3af12ecb6#diff-a9a04fa360dca60daa488241916fdb9c


though I can't say immediately where, because the full line is


non-directory 
/Users/karl.crisman/Downloads/sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/karl.crisman/Downloads/sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src


and indeed I don't see why there should be a file that has the entire path 
to sage/local TWICE; probably should use a temp file if for some reason 
that was the desired behavior? I did not do anything unusual in this setup.


Thanks!  Everything else seems to be progressing normally.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: square root very strange in 8.5.beta3

[kcrisman]

On Thursday, November 15, 2018 at 7:06:50 AM UTC-5, Simon King wrote:
>
> Hi! 
>
> On 2018-11-15, Erik Bray > wrote: 
> > Perhaps there should be a common suite of unit tests applicable to 
> > symbolic functions / functions that can return symbolic expressions in 
> > order to help ensure a consistent interface.  This is all pretty 
> > embarrassing :( 
>
> Could that be a use case of our category framework? I.e., have a 
> "category of symbolic expressions", whose only object is SR and whose 
> morphisms are symbolic functions? 


There was a fair amount of work done around this a number of years ago, but 
it was not fully completed (as noted).  There is still (I think) a Trac 
ticket regarding making a "hold" context which would be great, but I think 
it also would require some meddling in Pynac again to fully implement them. 
   See https://trac.sagemath.org/ticket/24861 for hold of derivatives.  Or 
for limit: https://trac.sagemath.org/ticket/19203

As to the integral of piecewise, that is probably just continuing the 
previous long-ago piecewise implementation behavior - the notion being that 
we probably didn't have a way to even use "integrate" before the new 
piecewise symbolic functions were implemented.  Hopefully this would be 
pretty easy to do by an alias.

And the derivatives are similar - when the D[0] notation was implemented 
there wasn't really a unified interface with the symbolic functions.   And 
that documentation isn't well understood - 
see https://trac.sagemath.org/ticket/17445

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.rc1 released

[kcrisman]

On Friday, October 19, 2018 at 11:30:57 AM UTC-4, Dima Pasechnik wrote:
>
>
>
> On Fri, 19 Oct 2018, 17:19 kcrisman, > 
> wrote:
>
>>
>>
>> And what about trying to open while holding down Control key? 
>>>
>>
>> Yes.
>>  
>>  
>>
>>>
>>> As well, and here we are getting into weirdness, could it be that 
>>> security settings differ per country/language, and there could be some 
>>> blacklisting going on on US machines? From the same link: 
>>>
>>>
>> From the same link:  "Then I tried on my side computer which is updated 
>> to High Sierra.  The disk image opened fine. Looking the output of the 
>> mount command, it turned out that the disk image contained an APFS 
>> partition which is not supported by El Capitan."
>>
>> I bet this is what Justin ran into as well.
>>
>
> except that Justin tested on 10.13, which should support all this, no?
>
>>
>>
He also tested on 10.11, I think.  Anyway, hopefully it's a blip.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.rc1 released

[kcrisman]

> maybe different security settings matter? 
> Have you copied the thing to Applications? 
>
>
Can't copy anything if the dmg won't mount!  Nothing I tried seemed to get 
around that :-( including moving the dmg various places, though it would 
have really surprised me if that had made a difference.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4 released

[kcrisman]

> -> 10.11.6 (mid 2015 MBP, Quad core Core i7, 16GB Memory): testing 
> (‘ptestlong’) yielded no failures! 

 

I wonder if a binary dmg built on this would be mountable by others.  At 
the very least, once I am connected to a stable power source after this 
weekend I'll try to make some binaries for 10.11 if you don't beat me to 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 an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.rc1 released

[kcrisman]

>
> > 
> > works on OSX 10.13.6, Intel Core 2 Duo 
> > (good indication that it would work everywhere, IMHO) 
>
> The image could not be mounted in my case, or KCrisman’s case (in both, 
> the image did not [seem to] contain mountable file systems).  I think in 
> both cases, the MD5 checksums matched after download. 
>
> I tried on 10.13.6; Karl used 10.11. 
>

Correct.  However, in the meantime I guess the mirrors have it, 
e.g. http://mirrors.mit.edu/sage/osx/intel/index.html worked for me to 
download.  This downloaded fine.  BUT I received the same bizarre 'no 
mountable file systems' message.  Don't know what to do here.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.rc1 released

[kcrisman]

On Tuesday, October 16, 2018 at 12:23:09 AM UTC-4, Justin C. Walker wrote:
>
>
>
> > On Oct 14, 2018, at 15:43 , Volker Braun  > wrote: 
> > 
> > I built OSX test binaries for 8.4.rc1, you can find them at the usual 
> place 
> > 
> > http://files.sagemath.org/osx/intel/index.html 
> > 
> > These are built with XCode 10, and should work on OSX >= 10.6. Support 
> for a few earlier versions was dropped in this XCode update. Also, these 
> are built without gcc (i.e. without SAGE_INSTALL_GCC). Please test! 
>
> I downloaded sage-8.4.rc1-OSX_10.13.6_x86_64.app.dmg a while ago.  I 
> verified the checksum, and then tried to open the .dmg on a 10.6.8 system. 
>  After churning for a while, I got an alert saying the disk image could not 
> be opened because there was no  were "no mountable file systems”. 
>
> I used the “open” command from the command line, with the name of the .dmg 
> file.  Is there something I missed? 
>

Yeah, this is *exactly* what happened to me (except I double-clicked). 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.4.rc1 released

[kcrisman]

On Sunday, October 14, 2018 at 6:43:40 PM UTC-4, Volker Braun wrote:
>
> I built OSX test binaries for 8.4.rc1, you can find them at the usual place
>
> http://files.sagemath.org/osx/intel/index.html
>
>>
>>
It keeps on timing out after 1.09 GB for me.  Trying to download the rest 
results in a corrupted download, I think.  The checksum is correct, 
however.  I get the "no mountable filesystems" error.  This is on OS X 
10.11 though for the life of me I can't see why that would happen when the 
checksum is correct.  I figure it has to have something to do with the 
timeout.  This happened with two different connections (work and home). 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.4.rc1 released

[kcrisman]

On Sunday, October 14, 2018 at 6:43:40 PM UTC-4, Volker Braun wrote:
>
> I built OSX test binaries for 8.4.rc1, you can find them at the usual place
>
> http://files.sagemath.org/osx/intel/index.html
>
> These are built with XCode 10, and should work on OSX >= 10.6. 
>
>>
>>
Thanks, that is helpful and I'll test that out.  Takes a lot less time to 
download than build my own binaries if I'm only testing!

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.3 release notes

[kcrisman]

On Thursday, September 6, 2018 at 12:46:13 PM UTC-4, Harald Schilly wrote:
>
> Commit for website: 
>
> https://github.com/sagemath/website/commit/daa32c428adc288ec994beb7c44dedec06b74b81
>  
> leading to http://www.sagemath.org/changelogs/sage-8.3.txt 
>
> Thank you :-) 
>

Yes!!! 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.beta5 released

[kcrisman]

On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote:
>
> We didn’t test clang 3.7 which is what your machine is using at OS X 
> 10.11. 


Would that be the same as this one?  I also have 10.11.

$ clang --version

Apple LLVM version 7.3.0 (clang-703.0.31)

Target: x86_64-apple-darwin15.6.0

Thread model: posix

InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1 released

[kcrisman]

Related to binaries for 8.1, please 
see https://ask.sagemath.org/question/40649/sagemath-for-macos-1013/ .  We 
apparently currently only have 10.11 and 10.12 binaries available.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.beta0 released

[kcrisman]

One thing we can take here is that perhaps we should think more about what 
> meta-info should go into commits. 
> One useful, and currently missing, field would the tag of the release it 
> was merged in.
>

A year or two ago I was hoping to do a relatively easy fix to Volker's 
scripts to automatically put that info on the Trac ticket as well, which 
tedious task had presumably been done manually by the RM for quite some 
time.  Never found the time, but your idea would parallel that one and be 
quite useful.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.rc2 released

[kcrisman]

On Saturday, November 18, 2017 at 5:40:09 PM UTC-5, kcrisman wrote:
>
> I'm still waiting for Mac app to build and test it, but otherwise things 
> seem fine.
>

Seems okay! 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.rc1 released

[kcrisman]

On Saturday, November 18, 2017 at 3:56:27 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2017-11-18 04:47, kcrisman wrote: 
> > So maybe that is part of the issue.  How could that be happening? 
>
> Maybe you have more than 1 version of Sage installed? 
>

Of course, I typed "sage" instead of "./sage" - stupid.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.rc1 released

[kcrisman]

On Friday, November 17, 2017 at 10:37:22 PM UTC-5, kcrisman wrote:
>
>
>
> On Friday, November 17, 2017 at 1:31:44 PM UTC-5, Justin C. Walker wrote:
>>
>>
>> > On Nov 17, 2017, at 10:12 , kcrisman <kcri...@gmail.com> wrote: 
>> > 
>> > I'm building this from scratch on Mac from tarball, would appreciate if 
>> we waited on releasing 8.1 until I can confirm notebook things working 
>> there.  Or Justin can check out notebook functionality on his build. 
>>  Thanks! 
>>
>> 8.1-rc1 built fine for me, and I did try one or two quick notebook trials 
>> w/o obvious problems.  Since I’m more of a CLI guy, I don’t have enough 
>> experience to “check it out”, but if you have suggestions, I will try them. 
>>
>
> No, that's all we need.  I would like time to separately test the Mac app 
> as well  but that will have to wait overnight, assuming I have time 
> tomorrow EST to try it out. 
>

I'm having trouble (on Mac) getting the old notebook to start. 
 http://localhost:/sagenb/www/run-sagenb.html comes when I click on the 
"run old Sage notebook" in the sage-export screen, but then nothing 
happens.  The log looks normal but never gets to the actual notebook.

Also, I downloaded the correct tarball but I get

:sage-8.1.rc1 karl.crisman$ sage -n

┌┐

│ SageMath version 8.1.beta5, Release Date: 2017-09-11   │

│ Type "notebook()" for the browser-based notebook interface.│

│ Type "help()" for help.│

└┘

sage: version()

'SageMath version 8.1.beta5, Release Date: 2017-09-11'



$ git log

commit e47ca9ea995ba64ed72a47f90d0e8f47f7429ce9

Author: Volker Braun <vbraun.n...@gmail.com>

Date:   Wed Nov 15 15:47:33 2017 +0100


Updated SageMath version to 8.1.rc1



So maybe that is part of the issue.  How could that be happening?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.rc1 released

[kcrisman]

On Friday, November 17, 2017 at 1:31:44 PM UTC-5, Justin C. Walker wrote:
>
>
> > On Nov 17, 2017, at 10:12 , kcrisman <kcri...@gmail.com > 
> wrote: 
> > 
> > I'm building this from scratch on Mac from tarball, would appreciate if 
> we waited on releasing 8.1 until I can confirm notebook things working 
> there.  Or Justin can check out notebook functionality on his build. 
>  Thanks! 
>
> 8.1-rc1 built fine for me, and I did try one or two quick notebook trials 
> w/o obvious problems.  Since I’m more of a CLI guy, I don’t have enough 
> experience to “check it out”, but if you have suggestions, I will try them. 
>

No, that's all we need.  I would like time to separately test the Mac app 
as well  but that will have to wait overnight, assuming I have time 
tomorrow EST to try it out. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.1.rc1 released

[kcrisman]

I'm building this from scratch on Mac from tarball, would appreciate if we 
waited on releasing 8.1 until I can confirm notebook things working there. 
 Or Justin can check out notebook functionality on his build.  Thanks!

On Friday, November 17, 2017 at 8:20:49 AM UTC-5, Eric Gourgoulhon wrote:
>
> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + 
> pull develop, parallel (-j16) build OK.
> ptestlong OK as well, modulo 2 doctests:
>
> sage -t --long --warn-long 46.1 src/sage/plot/plot3d/implicit_plot3d.py  # 
> 1 doctest failed
> sage -t --long --warn-long 46.1 src/sage/plot/plot3d/shapes2.py  # 1 
> doctest failed
>
> As usual on this computer since a few betas, this is due to the failure of 
> Jmol to create some file in ~/.sage/temp/. Both doctests are passed when 
> run standalone. 
>
> Besides, there is no longer any issue with the notebook exporter. 
>
> Best wishes,
>
> Eric.
>
>
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 8.0 released (desire binary for OSX 10.11.6)

[kcrisman]

On Monday, August 7, 2017 at 12:45:27 PM UTC-4, Bruce wrote:
>
>
> On Sunday, August 6, 2017 at 3:40:07 PM UTC-7, Volker Braun wrote:
>>
>> Binaries for OSX 10.12.6 are at 
>> http://files.sagemath.org/osx/intel/index.html
>>
>> May also work on older versions of OSX, but I have no way of testing
>>
>
>
> I just tested it.
> The OSX 10.12.6 binary does not work on OSX 10.11.6
>
> I'm cross posting to sage-devel where there may be someone who has a 
> working binary for El Capitan sage-8.0-OSX_10.11.6-x86_64
>

Do we still have a need for this?  I was computer-free for a bit but can 
create one if useful. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

On Saturday, July 8, 2017 at 2:47:41 AM UTC-4, Justin C. Walker wrote:
>
>
> > On Jul 6, 2017, at 00:52 , Volker Braun  > wrote: 
> > 
> > As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
> Built from a git checkout.  No problems (macOS 10.11.6. Quad-core Core 
> i7).  Testing (‘ptestlong’): 
> - first run yielded one failure 
>sage -t --long --warn-long 101.6 src/sage/libs/gap/assigned_names.py 
> timed out 
> - reran the build (essentially just the testing) and all tests passed. 
>
> Justin 


How is the notebook and/or app for you?  

Actually, more generally - we tested everything but it would be good to see 
if the buildbot for OS X produces an app dmg that functions nicely on 
startup.  I'm still on 10.11 so I can't test that directly - it's running 
10.12, right Volker?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

>
> Ditto for https://trac.sagemath.org/ticket/19974, which is IMNSHO, more 
> urgent, 
>

Ready for review. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

Ah, thank you!!

On Friday, June 23, 2017 at 10:45:21 AM UTC-4, Meier wrote:
>
> I would like to submit the translation required for Portuguese of the 
> first sentences and a maybe a more complete translation in the near future 
> for the Sage as a whole.
>
> Portuguese:
>
>
> Esta seção refere-se ao notebook Sage legado, ou "sagenb". Consulte a 
> documentação da sagenb para obter maiores detalhes.
>
>
>
> SageMath está em transição para uso do Jupyter como padrão, que tem uma 
> estrutura diferente. A diferença mais importante para os usuários é que as 
> planilhas individuais no Jupyter são salvas no seu sistema local (como 
> qualquer outro arquivo é salvo), enquanto que no tipo de notebook anterior 
> Sage (ou sagenb) o principal ponto de acesso está nos arquivos descritos 
> abaixo através do servidor.
>
>
>
> On Fri, Jun 23, 2017 at 11:24 AM, kcrisman <kcri...@gmail.com 
> > wrote:
>
>>
>>
>> On Friday, June 23, 2017 at 5:48:11 AM UTC-4, Emmanuel Charpentier wrote:
>>>
>>>
>>>
>>> Le vendredi 23 juin 2017 07:21:04 UTC+2, vdelecroix a écrit :
>>>>
>>>> On 22/06/2017 22:11, Volker Braun wrote 
>>>> > This might be the last beta for 8.0, so if you have anything super 
>>>> urgent 
>>>> > let me know... 
>>>>
>>>> If we are about to switch to Jupyter as a default, then I guess that 
>>>>
>>>> https://trac.sagemath.org/ticket/22777 
>>>>
>>>> would better be fixed. 
>>>>
>>>
>>> Seconded.
>>>
>>> Ditto for https://trac.sagemath.org/ticket/19974, which is IMNSHO, more 
>>> urgent, 
>>>
>>
>>
>> And I'll point out that there is good progress on this ticket.  For full 
>> support, it would be WONDERFUL to have translations in Portuguese, Russian, 
>> and Japanese for the following text, at the very least for the first 
>> sentence and the phrase "legacy SageNB notebook".
>>
>> +++
>>
>> This section refers to the legacy Sage notebook, or “sagenb”. See the 
>> sagenb documentation for full details.
>>
>>
>> SageMath <https://trac.sagemath.org/wiki/SageMath> is transitioning to 
>> using the Jupyter notebook as a default, which has a different structure. 
>> The most important difference for users is that individual worksheets in 
>> Jupyter are saved on your local system just like any other file, whereas in 
>> the Sage notebook the main point of access is in the files described below 
>> via the server.
>>
>> Legacy SageNB Notebook 
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to sage-r...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Luiz Roberto Meier
>
> *After silence, that which comes nearest to expressing the inexpressible 
> is music. -- Aldous Huxley*
>
> *Without music, life would be a mistake. -- Nietzsche*
> --
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

> This might be the last beta for 8.0, so if you have anything super urgent 
> > let me know... 
>
> If we are about to switch to Jupyter as a default, then I guess that 
>
> https://trac.sagemath.org/ticket/22777 
>
>
I think that Volker's note in #17783 is that perhaps the syntax has to 
change to work with Jupyter?
 

> would better be fixed. 
>

Well, for now the "export" server is the default ... that 
said, https://trac.sagemath.org/ticket/19974 is probably even more so 
important.  There is a branch that should be fine as far as it goes, but in 
any case if anyone gives a little feedback I can finish that today.

(By the way, if anyone has a *stable* link by actual Jupyter people that is 
a good graphical overview of how to use Jupyter that would be a good thing 
to add there, and in a few other places.)

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

I have some OS X beta0 binaries I hope some people could test out - is 
there a good place to upload them?  (I could send Harald a link if need be; 
unfortunately it isn't a place that can handle great bandwidth of 
downloads.)
Thanks,
- kcrisman

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

On Monday, April 3, 2017 at 10:47:56 PM UTC-4, kcrisman wrote:
>
>
>
> On Monday, April 3, 2017 at 1:19:06 PM UTC-4, Volker Braun wrote:
>>
>> In sage.yaml change "branch: develop" to "branch: master". Then build 
>> again...
>>
>
> No no, I I already did that once I realized that I had waited too long - 
> and I find it useful to have built 8.0.beta0 binaries anyway.  
>
> What I mean is that I am in the middle of make bdist-sage-osx with the 
> correct yaml but in the midst of it (as often the case) the dochtml didn't 
> build correctly because there was another branch (namely, develop).  I 
> would prefer to not have to just delete binary-pkg and start over.   But I 
> don't want to just type "make doc-clean" because I'm not sure how 
> binary-pkg will interpret that.
>


cd-ing to the actual Sage and make doc-clean and make doc didn't seem to 
have any negative side effects to then continuing make bdist-sage-osx at 
least afaict.  So I guess doing that didn't mess up any env vars, which I 
was worried about. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

On Monday, April 3, 2017 at 10:47:56 PM UTC-4, kcrisman wrote:
>
>
>
> On Monday, April 3, 2017 at 1:19:06 PM UTC-4, Volker Braun wrote:
>>
>> In sage.yaml change "branch: develop" to "branch: master". Then build 
>> again...
>>
>
> No no, I I already did that once I realized that I had waited too long - 
> and I find it useful to have built 8.0.beta0 binaries anyway.  
>
> What I mean is that I am in the middle of make bdist-sage-osx with the 
> correct yaml but in the midst of it (as often the case) the dochtml didn't 
> build correctly because there was another branch (namely, develop).  I 
> would prefer to not have to just delete binary-pkg and start over.   But I 
> don't want to just type "make doc-clean" because I'm not sure how 
> binary-pkg will interpret that.
>


Kwankyu points out that https://trac.sagemath.org/ticket/22588 may finally 
solve this issue.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

On Monday, April 3, 2017 at 1:19:06 PM UTC-4, Volker Braun wrote:
>
> In sage.yaml change "branch: develop" to "branch: master". Then build 
> again...
>

No no, I I already did that once I realized that I had waited too long - 
and I find it useful to have built 8.0.beta0 binaries anyway.  

What I mean is that I am in the middle of make bdist-sage-osx with the 
correct yaml but in the midst of it (as often the case) the dochtml didn't 
build correctly because there was another branch (namely, develop).  I 
would prefer to not have to just delete binary-pkg and start over.   But I 
don't want to just type "make doc-clean" because I'm not sure how 
binary-pkg will interpret that.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

>
>> Try again!
>>>
>>
>> Will do once I am connected to power source ;-)
>>
>
> Nearly finished but because I (accidentally, but usefully) built binaries 
> of 8.beta0 due to the default target being "develop" not "master" I have 
> the usual error when you switch branches below.  How do I fix this inside 
> of binary-pkg?  I am hesitant to do make doc-clean since presumably that is 
> not a legitimate target in this event, and anyway I want the binaries. 
>  Thanks for assistance.
>

Ping? 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

Remember, we want LOTS OF TESTING of this one - including the Mac 
interface.  Any possible bugs in the move to the ExportSageNB interface 
must be exposed.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

On Thursday, March 30, 2017 at 1:07:21 PM UTC-4, Volker Braun wrote:
>
> I'm fixing it at https://github.com/hashdist/hashstack/pull/987
>

Okay; let me know when binary-pkg is ready to use again. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

On Wednesday, March 29, 2017 at 11:01:19 AM UTC-4, kcrisman wrote:
>
> Would binaries for OS X 10.11 be useful?  I assume the answer is yes - I 
> had better remember how to use https://github.com/sagemath/binary-pkg !
>

In the event:

[*gettext-bootstrap*]   tail -f 
/Users/.../.hashdist/tmp/gettext-bootstrap-ikflymbnm35x/_hashdist/build.log

Downloading http://download.zeromq.org/zeromq-4.1.3.tar.gz...

[ERROR] urllib failed to download (code: 503): 
http://download.zeromq.org/zeromq-4.1.3.tar.gz

Downloading http://download.zeromq.org/zeromq-4.1.3.tar.gz...

[ERROR] urllib failed to download (code: 503): 
http://download.zeromq.org/zeromq-4.1.3.tar.gz

Downloading http://download.zeromq.org/zeromq-4.1.3.tar.gz...

[ERROR] urllib failed to download (code: 503): 
http://download.zeromq.org/zeromq-4.1.3.tar.gz

*[CRITICAL]* You may wish to check your Internet connection or the remote 
server
make[1]: 

$ ping download.zeromq.org

PING zeromq-download-redirect.herokuapp.com (79.125.24.174): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

^C

--- zeromq-download-redirect.herokuapp.com ping statistics ---

4 packets transmitted, 0 packets received, 100.0% packet loss

Did anyone else trying to make binaries have this problem?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[kcrisman]

Would binaries for OS X 10.11 be useful?  I assume the answer is yes - I 
had better remember how to use https://github.com/sagemath/binary-pkg !

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.4 released

[kcrisman]

> Has Jeroen's changelog script been located? If so, please add it to the 
> sagemath/website repository.
>
> I've opened an issue to track this: 
> https://github.com/sagemath/website/issues/107
>

According to that issue, it was indeed recovered - perhaps it could be 
added to the Sage repo in some form or other (not sure how realistic that 
is). 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

make distclean ?
>

Just redoing make continued fine and all was well.   Some kind of race 
condition on vcversioner not having been upgraded/installed yet?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.6.beta0 released

[kcrisman]

On two systems I built this beta I had to remove ~/.sage/,
> as with it present  Sage just dies. (unless started with ---nodotsage).
>
> People with stuff in ~/.sage/ will not be happy.
>
>
>>
Like, say, the sagenb? 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.3 released

[kcrisman]

> > 
> > On Fri, Aug 5, 2016 at 11:05 AM leif  > > wrote: 
> > 
> > No, the tombstones (or zombies?) are these: 
> > 
> > 
> > Huh. I just started work on one of these half an hour ago. 
> > So call me ghoul or ? 
>
> Solange daraus keine Leichenfledderei wird, ok.  (Schon der Versuch ist 
> strafbar [1].) 
>

Oder aber:
http://stackoverflow.com/help/badges/17/necromancer 
"Awarded 291312 times"
Though in this case it might be better to start not having a milestone and 
then only 'awarding' a milestone to tickets with positive review, since we 
have little meaningful triage on Trac.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.3.beta4 released

[kcrisman]

On Saturday, June 18, 2016 at 9:56:14 AM UTC-4, Volker Braun wrote:
>
> This is http://trac.sagemath.org/ticket/20842
>
> It seems that the script is accidentally quadratic in the number of 
> filenames, and gcc has almost 100k files...
>
>>
>>
Thanks; I just destroyed my only working Sage on this computer with trying 
this (sage had still worked after a transfer from another computer, but gcc 
wasn't working any more).  I'll check this change out. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.3.beta4 released

[kcrisman]

On Saturday, June 18, 2016 at 7:01:47 AM UTC-4, leif wrote:
>
> Volker Braun wrote: 
> > KeyboardInterrupt means you pressed Ctrl-C (or maybe your cat ran over 
> > the keyboard) 
>
> But it took the cat about half an hour to get bored by "Setting up build 
> directory for gcc-4.9.3.p1" (or probably less, and then a couple of 
> minutes to figure out how to press Ctrl-C, I don't know it). 
>

Indeed. In fact, the cat tried several times, once waiting at least an hour 
for the build directory to get set up.  Any ideas on why the cat had to 
wait so very, very long, especially when taking the tarball out of 
upstream/ and putting it elsewhere allowed tar -xvf to open it up within a 
couple minutes?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.3.beta4 released

[kcrisman]

Had to make distclean && make but it had an awful long time setting up 
build directory for gcc (prior stuff did fine) and then after interrupting 
(after like a half hour), the entire gcc pkg log is:

Found local metadata for gcc-4.9.3.p1

Using cached file 
/Users/karl.crisman/Downloads/sage/upstream/gcc-4.9.3.tar.bz2

gcc-4.9.3.p1



Setting up build directory for gcc-4.9.3.p1

Traceback (most recent call last):

  File "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", 
line 246, in 

sys.exit(main())

  File "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", 
line 237, in main

archive.extractall(members=archive.names)

  File "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", 
line 129, in extractall

for m in members]

  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/tarfile.py",
 
line 1819, in getmember

tarinfo = self._getmember(name)

  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/tarfile.py",
 
line 2395, in _getmember

member_name = member.name

gcc-4.9.3.p1] KeyboardInterrupt

[gcc-4.9.3.p1] Error: failed to extract 
/Users/karl.crisman/Downloads/sage/upstream/gcc-4.9.3.tar.bz2]


While doing this, I get process like


Load Avg: 1.34, 1.55, 1.66  CPU usage: 29.48% user, 2.94% sys, 67.56% idle

91862  Python   98.1  00:27.40 1/1   015201M+  0B 0B 
91747


This process is sage-uncompress-spkg


This is on El Capitan OS X 10.11.5.  Any ideas?  I don't think it should 
take that long just to extract it?  (I'm reluctant to clone from scratch 
because I have a number of branches already existing, though perhaps they 
are all also pushed to trac, I don't remember.)

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.0 released

[kcrisman]

> repository: file:///Users/karl.crisman/Downloads/sage
> branch: osx-10-7
>
>
Got it - I've never seen that syntax before since I've never had to clone 
something already local before :) thank you very much.  Though 
unfortunately it still gives the same error message :(
 
http://trac.sagemath.org/ticket/20789

I think what is happening is that

def git_clone(config):
if os.path.exists(os.path.join(config.source_path, '.git')):
subprocess.check_call([
'git', 'checkout', config.branch
], cwd=config.source_path)
subprocess.check_call([
'git', 'pull', '--ff-only'
], cwd=config.source_path)
else:
subprocess.check_call([
'git', 'clone', config.repository, '-b', config.branch, 
config.source_path
])

is noting that my local path to the git repo does exist, but then

$ git checkout osx-10-7
error: pathspec 'osx-10-7' did not match any file(s) known to git.

which makes sense because that branch is not in binary-pkg (I couldn't 
figure out exactly where source_path was set).

But I'd rather patch binary-pkg than try to do it otherwise at this point.  
Almost there!

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.0 released

[kcrisman]

 > We improved the mac app bundling script recently, seems like it is not 
compatible with OSX 10.7

Volker: mgoerner helped me some at #20119:

"I think you can just remove $(TARGET)/.DS_store from the non_app_files: 
target in src/mac-app/Makefile and then build it on 10.7 -without the nice 
arrangement of the icons and background image :(

I am not sure how you can tell binary_pkg to pick up that change. I would 
commit that change to a local repository and point binary_pkg's sage_yaml 
to that local repository."


I did all this, and even


name: SageMath

repository: /Users/karl.crisman/Downloads/sage
branch: osx-10-7


doesn't seem to work.  Does the file assume an online repository?  I don't 
know how to make it look right but certainly


$ ls ../sage/.git

has the usual stuff.  Any help is greatly appreciated!

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.0 released

[kcrisman]

> We improved the mac app bundling script recently, seems like it is not 
> compatible with OSX 10.7
>
>>
>>
I saw some posts about 10.8 not working but that was post 7.2, it was 7.3 
betas, so I didn't think there would be a problem.  

Was this related to this?  
https://github.com/sagemath/binary-pkg/commit/4d827f34da028563e69b066bda5ffba91c937eaa

No: 
https://github.com/sagemath/sage/commit/7b66c50be6c44f97d9779b40aaca15cd2ee035e4
and specifically this line failed
https://github.com/sagemath/sage/blob/master/src/mac-app/tools/createDSStore/ds_store/buddy.py#L76

So is there any alternative?  In the past one could "just make the bundle" 
and then drop the binary in.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.0 released

[kcrisman]

While trying binary-pkg for Sage 7.2 on OS X 10.7 (due to be upgraded to 
new computer within a week, so wanted to provide last binaries from that), 
apparently the tar and non-app dmg were created, but the app failed with 
the following.  Any ideas?  (Later today or tomorrow I can provide these 
for upload to mirrors, but not if I don't have the app version.  I'll note 
I rarely had trouble creating bdist with the sage-bdist script...)

total size is 2610034433  speedup is 1.00
test -d sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage 
&& touch sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage
rm -f sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
ln -s Contents/Resources/sage/sage 
sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
cp 
/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/bin/sage-README-osx.txt
 
sage-7.2-OSX_10.7.5_x86_64/README.txt
rm -f sage-7.2-OSX_10.7.5_x86_64/.DS_Store
tools/createDSStore/createDSStore.py sage-7.2-OSX_10.7.5_x86_64 
sage-7.2-OSX_10.7.5_x86_64 SageMath-7.2.app
Traceback (most recent call last):
  File "tools/createDSStore/createDSStore.py", line 146, in 
app_name = sys.argv[3])
  File "tools/createDSStore/createDSStore.py", line 123, in createDSStore
with ds_store.DSStore.open(filePath, 'w+') as d:
  File 
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/store.py",
 
line 269, in open
store = buddy.Allocator.open (file_or_name, mode)
  File 
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
 
line 221, in open
return Allocator (f)
  File 
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
 
line 136, in __init__
count, self._unknown2 = self._root.read('>II')
  File 
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
 
line 76, in read
return struct.unpack (size_or_format, data)
struct.error: unpack requires a string argument of length 8
make[2]: *** [sage-7.2-OSX_10.7.5_x86_64/.DS_Store] Error 1
cp: SageMath/src/mac-app/sage-7.2-*.app.dmg: No such file or directory
ERROR:root:Script failed:
ERROR:root:DMG=/Users/karl.crisman/Downloads/binary-pkg/dist/sage-7.2-OSX_10.7.5-x86_64.app.dmg
rm -f $DMG
pwd
(cd SageMath/src/mac-app && make)
cp SageMath/src/mac-app/sage-7.2-*.app.dmg $DMG

Traceback (most recent call last):
  File 
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
 
line 170, in _run_module_as_main
"__main__", mod_spec)
  File 
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
 
line 85, in _run_code
exec(code, run_globals)
  File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py", 
line 78, in 
launch()
  File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py", 
line 74, in launch
package.dist_script.run()
  File 
"/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/bash_script.py", line 
37, in run
['bash', self._filename], cwd=self._cwd, env=self.env())
  File 
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
 
line 561, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['bash', 
'/Users/karl.crisman/Downloads/binary-pkg/tmp/SageMath/tmp976sv49f.sh']' 
returned non-zero exit status 1
make[1]: *** [dist-sage] Error 1
make: *** [bdist-sage-osx] Error 2

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.2.beta6 released

[kcrisman]

>
>
>
> Tried to build on 10.6.8, but the build never got started: 
> *** 
> You are using Xcode version 3.2.6. 
> ... 
>
> Is this no longer supported?  I must have missed the discussion. 
>
>
This doesn't surprise me if you do it from scratch; you may have an old 
enough Xcode that the compiler can't build the gcc required directly, but 
needs a bootstrap to build the latest gcc (which is apparently written in 
C++?).  That is what happened to my 10.4 builds some months ago and I 
didn't have time to pursue it any further.  Though I hadn't seen the "never 
got started" piece at that time.   Of course, that's just relying on my 
memory - the computer I used for that wouldn't have had anything close to 
Xcode 3.2.6, so your problem may be different.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.2.beta3 released

[kcrisman]

On Tuesday, April 12, 2016 at 12:34:29 PM UTC-4, Jeroen Demeyer wrote:
>
> On 2016-04-12 18:21, kcrisman wrote: 
> > In the meantime, are the only ways to get my upgrade to finish doing 
> > "make -k" 
>
> Can you try 
>
> make openssl-clean # mark openssl as not installed 
>


Is that a new make target, so "make PKG_NAME-clean"?

Anyway, this didn't work.  I'm not using openssl anyway, I think I only 
have it because I was testing some installation procedure once, but thought 
I'd report 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 an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.2.beta3 released

[kcrisman]

I'm having trouble upgrading due to http://trac.sagemath.org/ticket/20143 - 
apparently once you've installed an optional package you have to keep it 
installed.  I can't figure out easily (without using some git skills I 
don't have time to look up right now) where this was merged, but anyway ... 
do I really have to do "make depend"?  That seems non-Sage-style, though I 
can do it.  This is on Mac Lion, Intel Core i7.

Configured for darwin64-x86_64-cc.

*** Because of configuration changes, you MUST do the following before
*** building:

make depend

Building openssl...
make[3]: warning: -jN forced in submake: disabling jobserver mode.
making all in crypto...
/usr/bin/perl ../util/mkbuildinf.pl "gcc -I. -I.. -I../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
/usr/bin/perl x86_64cpuid.pl macosx > x86_64cpuid.s
gcc -I. -I.. -I../include  -fPIC -fno-common -DOPENSSL_PIC 
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 -O3 
-DL_ENDIAN -Wall -DOPEN$
ar  r ../libcrypto.a cryptlib.o mem.o mem_dbg.o cversion.o ex_data.o 
cpt_err.o ebcdic.o uid.o o_time.o o_str.o o_dir.o o_fips.o o_init.o 
fips_ers.o x86_64cpu$
ar: creating archive ../libcrypto.a
/usr/bin/ranlib: file: ../libcrypto.a(ebcdic.o) has no symbols
/usr/bin/ranlib: file: ../libcrypto.a(fips_ers.o) has no symbols
test -z "" || ar  r ../libcrypto.a fipscanister.o
ranlib ../libcrypto.a || echo Never mind.
ranlib: file: ../libcrypto.a(ebcdic.o) has no symbols
ranlib: file: ../libcrypto.a(fips_ers.o) has no symbols
making all in crypto/objects...
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC 
-fno-common -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -ar$
ar  r ../../libcrypto.a o_names.o obj_dat.o obj_lib.o obj_err.o obj_xref.o
/usr/bin/ranlib: file: ../../libcrypto.a(ebcdic.o) has no symbols
/usr/bin/ranlib: file: ../../libcrypto.a(fips_ers.o) has no symbols
ranlib ../../libcrypto.a || echo Never mind.
ranlib: file: ../../libcrypto.a(ebcdic.o) has no symbols
ranlib: file: 

[sage-release] Re: Sage 7.1.beta3 released

[kcrisman]

Quoting from
http://ask.sagemath.org/question/32822/osx-installation/
though perhaps this is resolved - please answer there:

(before the version info box) "RuntimeError: maximum recursion depth 
exceeded during compilation"

(after the version info box) "ERROR: The Sage installation tree has moved

from 
/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma
 
to /Applications/SageMath-7.1.beta3.app/Contents/Resources/sage

This is not supported, and Sage will not work."

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.0 released

[kcrisman]

I've deleted the Sage-7.0 OSX binaries
>
>>
>>
 Are there any processors we are sure they work on?  I guess in theory one 
could just say on the download page "use with > 2014 computers else use 
6.10" but maybe that's more trouble than it's worth.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.0 released

[kcrisman]

> Untested is broken:
>> http://ask.sagemath.org/question/32330/sage-notebook-is-not-working/
>> This is via the .app bundle, I think.  What could have changed to make 
>> this not work? 
>>
>
> is it notebook-specfic, or a not working OSX binary? 
>

It seems to be that the notebook doesn't import sage.all. Although a new 
comment here says

Yes, sage from sage-7.0-osx-10.11.2-x86_64.app.dmg as well as sage from the 
sage-7.0-osx-10.11.2-x86_64.dmg do not import "sage.all". They return an 
import error on cliquer.so even though the library exists.

so maybe it's related to that issue instead, hence not universal?

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.0.rc1 released

[kcrisman]

>
>
> As mentioned before, there are no incremental updates from 6.x. You need 
> to compile from scratch, e.g. after cleaning with "make distclean" or "git 
> clean -f -d -x". If you are still working on tickets based on 6.x then you 
> might want to use a separate git tree for sage 7.
>
>
>
I looked through several of the threads in sage-release but couldn't 
(quickly) find anything more detailed than this.  What happened that Sage 7 
is not upgradeable?

I think that it would then make sense to have some message print out if 
someone tries sage -upgrade (if that's even still supported) lest they hose 
their Sage install, that's been a problem with such updates in the past as 
well. 

Also, can you give a little more guidance on how to still use "old" git 
branches - can we just merge in the newest Sage or will that cause problems 
as well?

Thanks,
- kcrisman

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

[kcrisman]

>
> Another thing I wanted to mention is the following. 
>
> When I started Sage for the first time from the SageMath 6.10.rc1 
> binaries for OS X, it started ouputting a bunch of lines (roughly 
> 2300 of them) starting with "patching", before finally giving the 
> Sage welcome header and the Sage prompt. See a copy of some of 
> these lines further down. 
>
> Could this whole process be made to start by a message such as 
>
> Some patches will now be applied to take into account 
> the location you have chosen for your SageMath installation. 
> This should take at most a few minutes. 
>
> Just to let the person know what is going on, why, and how long 
> it is supposed to last. 
>
>
I'd +1 that; I haven't tested these binaries yet since I don't have El 
Capitan but I agree that is not very user-friendly. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage-6.10.rc1 binaries test

[kcrisman]

> Yes, use https://github.com/sagemath/binary-pkg
>
> On Tuesday, December 15, 2015 at 3:08:13 PM UTC+1, kcrisman wrote:
>>
>> Can users still contribute binaries under this new packaging?  Especially 
>> for other Linuces and older Mac OS that would be something we want to 
>> encourage.
>>
>>
Okay.  Should we use this rather than `sage -bdist`?  

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage-6.10.rc1 released

[kcrisman]

Two optional tests fails (perhaps this is already known):

$ ./sage --version
SageMath Version 6.10.rc1, Release Date: 2015-12-13


sage -t src/sage/groups/generic.py
**
File "src/sage/groups/generic.py", line 1388, in 
sage.groups.generic.structure_description
Failed example:
G.structure_description() # optional - database_gap
Expected:
'C7'
Got:
'"C7"'
**
File "src/sage/groups/generic.py", line 1393, in 
sage.groups.generic.structure_description
Failed example:
groups.matrix.GL(4,2).structure_description() # optional - database_gap
Expected:
'A8'
Got:
'"A8"'
**
1 item had failures:
   2 of  14 in sage.groups.generic.structure_description
[215 tests, 2 failures, 7.47 s]

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage-6.10.rc1 binaries test

[kcrisman]

On Tuesday, December 15, 2015 at 3:20:17 PM UTC-5, Volker Braun wrote:
>
> Yes. Patches to the documentation are welcome ;-)
>
>
>
In this case, nice try - I haven't even used binary-pkg yet!  If and when I 
may try. 

 

> On Tuesday, December 15, 2015 at 8:53:23 PM UTC+1, kcrisman wrote:
>>
>> Yes, use https://github.com/sagemath/binary-pkg 
>>>
>> Okay.  Should we use this rather than `sage -bdist`?  
>>
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 6.9 released

[kcrisman]

On Saturday, October 10, 2015 at 6:11:39 PM UTC-4, Volker Braun wrote:
>
> The "master" git branch has been updated to Sage-6.9. As always, you can 
> get the latest beta version from the "develop" git branch. Alternatively, 
> the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
That link seems to only link to rcs. 
 http://mirrors.mit.edu/sage/src/index.html and friends do work.
Also, I note that http://www.sagemath.org/download-source.html and related 
pages (including front page) hasn't been updated yet, though they do lead 
to the correct page for source for 6.9.
 

> 2cc7f6c Updated Sage version to 6.9
> 657d6ff Trac #19374: LaTeX display broken in Jupyter output cells
> aabe6d1 Updated Sage version to 6.9.rc3
> c504e6e Trac #19338: Doc for deprecated_function_alias() is wrong
> 277518c Trac #19347: Source tarball should contain gcc
> 698579c Updated Sage version to 6.9.rc2
> f99f57d Trac #19324: Force reconfiguration after GCC installation
> f603730 Updated Sage version to 6.9.rc1
> 74721d5 Trac #19125: DeprecatedMethod wrapping is broken
> 1b5a573 Trac #19294: Doctest failure with coxeter3
> 2f7c727 Updated Sage version to 6.9.rc0
>
>

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.9 released

[kcrisman]

>
>
> > The "master" git branch has been updated to Sage-6.9. As always, you can 
> > get the latest beta version from the "develop" git branch. 
> Alternatively, 
> > the self-contained source tarball is at 
> > http://www.sagemath.org/download-latest.html 
>
> Built from the tarball on OS X, 10.6.8 w/o problems.  Testing 
> ('ptestlong') showed one failure ('bad exit: 2' from 
> "coding/codecan/autgroup_can_label.pyx"). 
>

If you can build a couple binaries for 10.6 I plan to do this shortly for 
10.7; currently the most recent binaries for < 10.10 are of Sage 6.6. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

I have a question about the new "required" use of pretty_print in these 
rcs.  I created this interact in class today.

@interact
def _(a = 3, f = x^2):
f(x) = f
D = diff(f,x)
I = integrate(f,x)
pretty_print(html("The derivative of ${}$ at $a = {}$ is 
${}$".format(latex(f(x)),a, D(a
pretty_print(html("The indefinite integral of ${}$ is 
${}+C$".format(latex(f(x)),latex(I(x)

show(plot(f,(x,a-1,a+1))+plot(D(a)*(x-a)+f(a),(x,a-1,a+1),linestyle='--',color='green'),figsize=3)

This looks quite different without the pretty_print in Sage 6.8 (what we 
are currently using in the lab here at AIMS); namely, the lines directly 
follow one another, I guess  elements or something (view source doesn't 
seem to get what I want for interacts).  With the Sage 6.8 behavior for 
pretty_print, we get big huge spaces in between - not optimal at all for 
presentation.

I won't be able to get to a computer with rc2 for a bit; does the new 
pretty_print with html do the (better) behavior of just having separate 
html lines without huge spaces in between?  Otherwise you have to zoom out 
so much that it's barely worth using.  Or is there some other way to 
multiline?  Using \n seems to work okay but that is somewhat annoying 
compared to actually being able to, you know, write multiple lines...

Thanks for any feedback!
- kcrisman

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

>
>
>
>> If someone can check that the notebook still works properly and so forth 
>> that would be nice.  Unfortunately due to some kind of firewall I haven't 
>> been able to pull for a while (the sysadmin will look into this on Monday, 
>> I think, his first suggestion about proxies didn't work, unfortunately). 
>>
>
> For future reference, opened port 9418, for the git protocol, which I 
> think was the issue.
>
> Regards,
> Jan 
>

Yeah, this seems to have worked - thanks Jan! 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

With SAGE_INSTALL_CCACHE=yes I get (from tarball)

Found local metadata for ccache-3.2.2
Attempting to download package ccache-3.2.2.tar.bz2 from mirrors
Downloading the Sage mirror list
CRITICAL [mirror_list|_refresh:164]: Downloading the mirror list failed

Also, this causes the entire build to fail, which seems somewhat 
unreasonable - couldn't it just keep building and report that it won't use 
ccache?

Note that , particularly mysteriously 
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):


That's not good either.  Also, just setting the env var to blank didn't 
seem to negate it, currently trying with unsetting it.  That's probably my 
ignorance of bash, though.

I can provide more details later if you would find them interesting.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

>
>
> That's not good either.  Also, just setting the env var to blank didn't 
> seem to negate it, currently trying with unsetting it.  That's probably my 
> ignorance of bash, though.
>

Aagh, it's *still* trying to download it, even though the env var 
SAGE_INSTALL_CCACHE is now not even showing up in the list!  Also trying to 
download gcc 4.9.2 (remember, this is from the tarball).  I will reuntar 
the ball and see what happens. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

>From a fresh untarred ball on Mac Lion:

Found local metadata for gcc-4.9.2.p1
Attempting to download package gcc-4.9.2.tar.bz2 from mirrors
Downloading the Sage mirror list
CRITICAL [mirror_list|_refresh:164]: Downloading the mirror list failed
Traceback (most recent call last):
  File "/Users/.../sage-6.9.rc2/build/bin/sage-download-file", line 28, in 

SageDownloadFileApplication().run()
  File "/Users/.../sage-6.9.rc2/build/bin/../sage_bootstrap/cmdline.py", 
line 193, in run
tarball.download()
  File "/Users/.../sage-6.9.rc2/build/bin/../sage_bootstrap/tarball.py", 
line 148, in download
for mirror in MirrorList():
  File 
"/Users/.../sage-6.9.rc2/build/bin/../sage_bootstrap/mirror_list.py", line 
63, in __init__
self.mirrors = self._load()
  File 
"/Users/.../sage-6.9.rc2/build/bin/../sage_bootstrap/mirror_list.py", line 
78, in _load
return ast.literal_eval(mirror_list)
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py",
 
line 49, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ast.py",
 
line 37, in parse
return compile(expr, filename, mode, PyCF_ONLY_AST)
  File "", line 0

^
SyntaxError: unexpected EOF while parsing
make[2]: *** 
[/Users/.../sage-6.9.rc2/local/var/lib/sage/installed/gcc-4.9.2.p1] Error 1
make[1]: *** [all-toolchain] Error 2

real 6m46.434s
user 1m57.608s
sys 1m7.451s
***
Error building Sage.

I view this as a blocker bug.  Internet should not be required for Sage to 
build from scratch from a tarball.  I'll see whether this is also due to 
some firewall but in the meantime let's get this fixed.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

> I compiled it on ubuntu 15.04 successfully, sage --notebook=ipython 
> worked, but I had no latex displaying, raw one.
>
>
Interesting.  I was in the meantime able to upgrade my previous 
installation and sagenb seems to work fine.  Still interested in that 
ccache thing - I had to reduce the load on my machine somewhat but now 
should be able to run a fresh build of rc2 from tarball. 

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

Also, I still get

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):


-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 6.9.rc2 released

[kcrisman]

>
>
> gcc should be contained in the source tarball. This is fallout from the 
> build system changes. Fix needs review at 
>
>
What about the blank line with no failed packages?  Clearly a package 
failed.  So somehow whatever mechanism causes the package to be listed (I 
used to know what that is, but in the new build system I don't) is not 
working if a package is not even downloaded.  But that is still a failure 
in that package - OR there should be some separate message saying that 
there is a connectivity problem.  Because the final message isn't the 
connectivity message, it's the message about Sage not building, and even

SyntaxError: unexpected EOF while parsing

isn't exactly something that screams "you have a bad proxy setting", which 
is what turned out to be the case for me.

-- 
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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.