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

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

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

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

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

> 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

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

> > > 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

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

> 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

[sage-release] Re: Sage 9.1 released

> 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

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

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.gordo

Re: [sage-release] Sage 9.1 released

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, >

Re: [sage-release] Sage 9.1 released

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

Re: [sage-release] Sage 9.1 released

> > 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 > >

Re: [sage-release] Sage 9.1 released

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

Re: [sage-release] Sage 9.1 released

> > 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 >

Re: [sage-release] Sage 9.1 released

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

Re: [sage-release] Sage 9.1 released

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

[sage-release] Re: Sage 9.1 released

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 >

[sage-release] Re: Sage 9.1 released

> > 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

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

> 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

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

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

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

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

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

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

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

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

[sage-release] Re: Sage 9.0 released

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

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

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] Re: Sage 9.0.beta4 released

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 f

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

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

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

FWIW make ptestlong (though no optional packages) -- All tests passed! -- Total time for all tests: 10172.0 seconds cpu time: 14976.0 seconds

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

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 >

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

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

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

> > > 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

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

> 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

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

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

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

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:

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

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

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

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

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

> 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 >

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

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

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

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 ->

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

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

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

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. >> >

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

> 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

Re: [sage-release] Sage 8.4 released

> -> 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

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

> > > > > 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

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

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 > > > >

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

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

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

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

Re: [sage-release] Sage 8.3 release notes

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

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

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:

[sage-release] Re: Sage 8.1 released

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

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

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

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

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" grou

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

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 &quo

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

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: >> > >> >

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

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 releas

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

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:

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

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

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

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

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

> > 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

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

s 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. &g

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

> 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

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

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

Re: [sage-release] Sage 7.6 released

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... >> > >

Re: [sage-release] Sage 7.6 released

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... >> > >

Re: [sage-release] Sage 7.6 released

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.

Re: [sage-release] Sage 7.6 released

> >> 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

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

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

Re: [sage-release] Sage 7.6 released

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"

Re: [sage-release] Sage 7.6 released

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/.../.

Re: [sage-release] Sage 7.6 released

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

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

> 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

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

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

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

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

Re: [sage-release] Sage 7.3 released

> > > > 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

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

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

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

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

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

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

Re: [sage-release] Sage 7.0 released

> 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 :(

Re: [sage-release] Sage 7.0 released

> 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

Re: [sage-release] Sage 7.0 released

> 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?

Re: [sage-release] Sage 7.0 released

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

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

> > > > 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

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

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 ope

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

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 ...

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

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

[sage-release] Re: Sage 7.0 released

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

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

> 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

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

s 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

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

> > 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-release] Re: Sage-6.10.rc1 binaries test

> 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 somethi

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

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-release] Re: Sage-6.10.rc1 binaries test

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

[sage-release] Re: Sage 6.9 released

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 >

Re: [sage-release] Sage 6.9 released

> > > > 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,

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

e 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&quo

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

> > > >> 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

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

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

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

> > > 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

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

>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

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

> 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

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

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

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

> > > 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

  1   2   3   >