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

On Thu, Oct 24, 2019 at 9:27 PM Samuel Lelievre wrote: > > Sun 2019-10-19 22:33:17 UTC, Volker Braun: >> >> 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

[sage-release] Fwd: [sage-support] Changelog for Sage?

any idea why no release notices have been created after 8.7 ? -- Forwarded message - From: Szabolcs Horvát Date: Thu, Oct 17, 2019 at 11:59 AM Subject: [sage-support] Changelog for Sage? To: sage-support Is there a changelog for Sage 8.8 or 8.9? I can only find 8.7 on the

Re: [sage-release] Sage 8.9 released

On Fri, 11 Oct 2019, 16:04 Thierry, wrote: > On Fri, Oct 11, 2019 at 02:50:41PM -0500, Dima Pasechnik wrote: > > I can't post there on ask.* from phone, I believe that installing > > libncurses5-dev and libreadline-dev should allow the build to use system > > readline. >

Re: [sage-release] Sage 8.9 released

t 02, 2019 at 01:46:00PM -0500, Dima Pasechnik wrote: > > On Wed, Oct 2, 2019 at 11:27 AM John Cremona > wrote: > > > > > > > > > > > > On Wed, 2 Oct 2019 at 09:07, John Cremona > wrote: > > >> > > >> > > >&

Re: [sage-release] Sage 8.9 released

On Fri, 11 Oct 2019, 12:36 Thierry, wrote: > Thanks for your answer, please could you cc me if you open a ticket ? > I will - might take a bit of time, as I am travelling from IMA at UMN back to UK today. > > Ciao, > Thierry > > > On Fri, Oct 11, 2019 at 12:27:28PM -05

Re: [sage-release] Sage 8.9 released

at 12:14 PM Thierry wrote: > > Hi, > > there is also a readline-related issue on 8.9 there: > > https://ask.sagemath.org/question/48276/building-sage-89-from-source-fails/ > > Ciao, > Thierry > > > > On Wed, Oct 02, 2019 at 01:46:00PM -0500, Dima Pasechnik wro

Re: [sage-release] Sage 8.9 released

On Wed, Oct 2, 2019 at 11:27 AM John Cremona wrote: > > > > On Wed, 2 Oct 2019 at 09:07, John Cremona wrote: >> >> >> >> On Wed, 2 Oct 2019 at 02:22, Dima Pasechnik wrote: >>> >>> something did not work as you installed libncurses5-dev, >

Re: [sage-release] Sage 8.9 released

listed... Could you check that /usr/include/ncurses.h is present on the box? On Wed, Oct 2, 2019 at 3:20 AM John Cremona wrote: > > > > On Tue, 1 Oct 2019 at 18:20, Dima Pasechnik wrote: >> >> Hi John, >> >> Do you have >> libncurses5-dev >> i

Re: [sage-release] Sage 8.9 released

! Could you try installing it, then run make ncurses-clean make readline-clean ./configure and check whether system-wide readline is picked up? If yes, this should cure these machines... Dima On Tue, Oct 1, 2019 at 9:01 PM John Cremona wrote: > > > > On Tue, 1 Oct 2019 at 13:42, Di

Re: [sage-release] Sage 8.9 released

On Tue, Oct 1, 2019 at 7:43 PM John Cremona wrote: > > > > On Tue, 1 Oct 2019 at 12:08, Dima Pasechnik wrote: >> >> On Tue, Oct 1, 2019 at 6:59 PM Dima Pasechnik wrote: >> > >> > It seems that these machines don't have readline development files &g

Re: [sage-release] Sage 8.9 released

On Tue, Oct 1, 2019 at 6:59 PM Dima Pasechnik wrote: > > It seems that these machines don't have readline development files > properly installed. > > Could you attach config.log ? > I mean the "main" config.log, not the ones from package builds. > > On Tue, O

Re: [sage-release] Sage 8.9 released

It seems that these machines don't have readline development files properly installed. Could you attach config.log ? On Tue, Oct 1, 2019 at 6:38 PM John Cremona wrote: > > For a change instead of updating the git repository to build 8.9 I downloaded > the file 8.9.tar.gz from the Releases

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

On Thu, Sep 12, 2019 at 8:58 PM John H Palmieri wrote: > > > > On Thursday, September 12, 2019 at 12:30:34 PM UTC-7, Dima Pasechnik wrote: >> >> On Thu, Sep 12, 2019 at 5:55 PM John Cremona wrote: >> > >> > On ubuntu, upgrade from previous beta, python3

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

On Thu, Sep 12, 2019 at 5:55 PM John Cremona wrote: > > On ubuntu, upgrade from previous beta, python3 configured: make ptestlong > succeeds except for > > sage -t --long --warn-long 81.2 src/sage/libs/gap/element.pyx # 147 doctests > failed > this looks like a mis-build of sorts. Maybe also

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

On Wed, Sep 11, 2019 at 4:09 PM Mariel Supina wrote: > > > > On Wednesday, September 11, 2019 at 12:18:37 PM UTC+2, Dima Pasechnik wrote: >> >> OK, thanks, let's do more debugging of cypari: >> >>cd /srv/public/shared/sage/upstream >>tar xf c

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

Supina wrote: > > Attached is the output of > > set > > On Tuesday, September 10, 2019 at 7:16:23 PM UTC+2, Dima Pasechnik wrote: >> >> On Tue, Sep 10, 2019 at 5:30 PM Mariel Supina >> wrote: >> > >> > On Tuesday, September 10, 2019 at 5:50:53

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

On Tue, Sep 10, 2019 at 5:30 PM Mariel Supina wrote: > > On Tuesday, September 10, 2019 at 5:50:53 PM UTC+2, Dima Pasechnik wrote: >> >> Thanks. OK, I see that you're supposed to be building Pari, anyway, >> amd then the rest should have worked. Strange. >> >&

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

re --with-python=3. > > On Tuesday, September 10, 2019 at 3:53:06 PM UTC+2, Dima Pasechnik wrote: >> >> On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina >> wrote: >> > >> > Hi, >> > >> > On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dim

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

On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina wrote: > > Hi, > > On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote: >> >> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina >> wrote: >> > >> > On Debian stretch, I get a compilatio

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

On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina wrote: > > Hi, > > On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote: >> >> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina >> wrote: >> > >> > On Debian stretch, I get a compilatio

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

On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina wrote: > > On Debian stretch, I get a compilation error making sage 8.9.beta9. The > problem is in the package "cypari", the relevant log is attached: Are you upgrading? Building from scratch? The interesting line is error: [Errno 2] No such file

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

On Fri, Sep 6, 2019 at 11:13 AM E. Madison Bray wrote: > > On Fri, Sep 6, 2019 at 11:36 AM E. Madison Bray wrote: > > > > Consistently getting a test failure on Cygwin related to some oddity in GAP: > > > > sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py > >

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

On Wed, Sep 4, 2019 at 10:30 AM E. Madison Bray wrote: > > Although it might be a little late, at this point, if we want to make > sure it's well-enough tested, I think we should try to include the > following in 8.9 final: > > https://trac.sagemath.org/ticket/28356 yes please, and also two

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

On Fri, Aug 23, 2019 at 11:01 AM Sébastien Labbé wrote: > > Bonjour! > > With the new version, I have problems fetching the internet: > > sage: oeis([3,7,15,1], max_results=4) > Traceback (most recent call last) > ... > IOError: failed (_ssl.c:726)> > Error fetching >

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

On Mon, Aug 19, 2019 at 3:40 PM Emmanuel Charpentier wrote: > > FWIW, on a Debian testing installation running on core I7 + 16 GB RAM, an > upgrade to 8.9.beta7 from a freshly reinstalled 8.9.beta6 gives three failure > that seem identical to those reported for 8.9.beta6: > >

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

this is a MacOS only bug. Someone running it should work on fix... On Wed, 14 Aug 2019 20:35 kcrisman, wrote: > > > 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: >> > >> > >&g

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

You're using gcc version 4.8.5, released in 2015. I guess AVX 512 didn't exist yet. On Mon, Aug 5, 2019 at 11:17 PM Markus Wageringel wrote: > > The package fflas_ffpack-2.4.3 added in #26932 fails to compile for me on > CentOS 7.6.1810, due to several errors of this form: > > g++: error:

Re: [sage-release] Re: Sage 8..8 released

. On Wed, Jul 3, 2019 at 11:03 AM Jan Groenewald wrote: > > Hi > > On Wed, 3 Jul 2019 at 11:54, Dima Pasechnik wrote: >> >> Well, Debian 10 will be coming with an up to date Sage installable via apt. >> Do we need to duplicate this? > > > Debian 10 Buster has sag

Re: [sage-release] Re: Sage 8..8 released

On Wed, Jul 3, 2019 at 10:48 AM Jan Groenewald wrote: > > Hi > > On Tue, 2 Jul 2019 at 21:08, Volker Braun wrote: >> >> binaries are now on the way to the mirrors! > > > 1. It looks like Debian 9 is missing? > > 2. Debian 10 "buster" is due for release in 3 days. > There is a Debian 10 buildbot

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

File "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py", line 1373, in sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function Failed example: H.zeta_function() Expected: (81*x^4 + 72*x^3 + 32*x^2 + 8*x + 1)/(9*x^2 -

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

On Sat, Jun 15, 2019 at 10:51 PM darwin doppelganger wrote: > > I just wanted to mention that the self-contained source tarball for Sage > 8.8.rc1 hasn't yet appeared on any of the several mirrors that I tried among > those listed at http://www.sagemath.org/download-latest.html. I've noticed

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

Can we please get https://trac.sagemath.org/ticket/27950 in this release? It's docs on how to run Sage in conda, we are getting questions on it because our instructions are old, and cause at the moment conda needs a workaround. On Fri, Jun 14, 2019 at 7:40 AM Volker Braun wrote: > > As always,

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

On Wed, Jun 12, 2019 at 6:13 PM Volker Braun wrote: > > On Wednesday, June 12, 2019 at 2:05:04 PM UTC+2, E. Madison Bray wrote: >> >> One very easily solution to this, and I know some people will shudder >> (myself included) is to simply include the configure script in the >> repository. > > > We

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

On Wed, Jun 12, 2019 at 2:42 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 3:14 PM Dima Pasechnik wrote: > > > > On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray > > wrote: > > > > > > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: >

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

On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: > > > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray > > wrote: > > > > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: &g

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

On Wed, Jun 12, 2019 at 1:46 PM Dima Pasechnik wrote: > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray wrote: > > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray > > > wro

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

On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray > > wrote: > > > > > > I don't know why the rush to call this a release can

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

On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray wrote: > > I don't know why the rush to call this a release candidate when there are > clearly still several outstanding problems to be resolved before the next > release. > > As usual absolutely zero communication of a plan or coordination with

Re: [sage-release] Re: Sage 8.8.beta7 released

On Sat, Jun 1, 2019 at 7:25 AM Frédéric Chapoton wrote: > > Do we plan to distribute also a python3-version of sage 8.8 (binaries) ? Of > course, some tests are still not passing, but sage works nevertheless. IMHO it is too early. Some parts of python3 version produce patently incorrect

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

there are tickets listed here but still not marked as merged n trac, eg #27795 On Sat, 11 May 2019 at 14:40, 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.8.beta3 released

These are not actual doctest failures, these come from the patchbot being confused by these "Warning, slow doctest:" messages. And it seems that the doctest expected time completion is mis-computed for some reason, for, say, 0.19s for a doctest should be acceptable! On Tue, Apr 23, 2019 at 11:55

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

so you need to rebuild sagelib with new libvpx. In general after a major system update it's best to "make distclean" and rebuild from scratch. Or you can touch pyx files which depend upon libvpx and run make, but if there were mo updates it might be in vain. On Wed, Mar 20, 2019 at 4:07 PM

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

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 &

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

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) On Thu, Mar 7, 2019 at 4:50 PM kcrisman wrote: > > upgrading from some early 8.6 beta, I get something weird with file > permissions

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

On Tue, Feb 26, 2019 at 9:55 AM Sébastien Labbé wrote: > > > Using > --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage > External software detected for doctesting: >

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

It's really weird that mirrors don't checksum stuff they download and host. Could it be due to an error in setting the mirroring on Sage's side? Just wondering... On Thu, Jan 24, 2019 at 11:21 AM Harald Schilly wrote: > > > > On Thu, Jan 24, 2019 at 8:10 AM Vincent Delecroix

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

On Thu, Jan 24, 2019 at 11:10 AM Jeroen Demeyer wrote: > > On 2019-01-24 10:44, Dima Pasechnik wrote: > > curl -O would download html fragment > > Crazy stuff. What's the rationale for *not* following the Location > header by default? well, ask here: https://github.com/cur

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

On Thu, Jan 24, 2019 at 9:19 AM Jeroen Demeyer wrote: > > More precisely, the "tarball" is just this HTML fragment: > > You are being href="https://codeload.github.com/msoos/cryptominisat/tar.gz/5.6.6;>redirected. > > I don't know how the release manager downloaded that tarball, as the > link on

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

On Mon, Jan 14, 2019 at 5:07 PM Jeroen Demeyer wrote: > > On 2019-01-14 17:40, Dima Pasechnik wrote: > > I am getting a Heisenbug: > > > > sage -t --long src/sage/geometry/polyhedron/library.py > >

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

I am getting a Heisenbug: sage -t --long src/sage/geometry/polyhedron/library.py ** File "src/sage/geometry/polyhedron/library.py", line 398, in sage.geometry.polyhedron.library.Polytopes.icosahedron Failed example:

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

Let us have the next release staring with merging all the positively reviewed py3 tickets. Right now it is very hard to see why a paricular change introduces a py3 problem, as there are so many changes that need be merged. On Sun, 13 Jan 2019 at 08:13, wrote: > This is the second consecutive

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

regarding GAP tests, they are fixed in #26856 On Mon, Dec 31, 2018 at 9:05 PM Emmanuel Charpentier wrote: > > Builds OK on Debian testing running on core i5 + 8 GB RAM ; fails two > doctests : > > -- > sage -t --long

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

see #26713 tldr; open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg On Fri, Dec 14, 2018 at 11:56 PM John H Palmieri wrote: > > Fails to build from scratch on some OS X Mojave machines. I think the issue > is that on the affected machine, there is no

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

On Thu, Nov 15, 2018 at 11:46 AM Erik Bray wrote: > > On Thu, Nov 15, 2018 at 8:39 AM Emmanuel Charpentier > wrote: > > > > > > > > Le mercredi 14 novembre 2018 12:29:36 UTC+1, Erik Bray a écrit : > > > >> > >> However, one thing I do find surprising about the global sqrt > >> function, which is

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

On Mon, 12 Nov 2018 at 06:22, Dima Pasechnik wrote: > > > On Mon, 12 Nov 2018 at 05:39, wrote: > >> well, my opinion would be to remove the doc building in sagenb >> spkg-install.. When I comment these lines, everything works fine. >> >> Because this tries to

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

On Mon, 12 Nov 2018 at 05:39, wrote: > well, my opinion would be to remove the doc building in sagenb > spkg-install.. When I comment these lines, everything works fine. > > Because this tries to import sage.all, this can only work if sage is > considered to be fully built.. > are you sure it

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

did you check md5sum of dmg? On Fri, 19 Oct 2018, 13:57 kcrisman, wrote: > > 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

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

On Thu, Oct 18, 2018 at 2:51 AM kcrisman wrote: >> >> > >> > 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

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

On Sunday, October 14, 2018 at 11:43:40 PM UTC+1, 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

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

Can you run this command interactively at sage: prompt? Does it 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.

[sage-release] Re: Sage 8.3.beta2 released

see https://trac.sagemath.org/ticket/25353 -- 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,

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

in this case doctest basically compares strings, obtained from the list of roots. Order of the latter is not important. By right, one should compare sets, not lists. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group

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

On Tuesday, May 15, 2018 at 9:34:55 PM UTC+1, Justin C. Walker wrote: > > > > On May 9, 2018, at 11:44 , 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

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

this is already fixed in https://trac.sagemath.org/ticket/25323 please review :-) On Tuesday, May 15, 2018 at 4:44:03 PM UTC+1, John H Palmieri wrote: > > For me on OS X, I get the same failures as in earlier versions (which may > be related somehow to my system). But if I then do "sage -i

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

On Tuesday, May 15, 2018 at 4:44:03 PM UTC+1, John H Palmieri wrote: > > For me on OS X, I get the same failures as in earlier versions (which may > be related somehow to my system). But if I then do "sage -i database_gap" > and run tests again, I get failures in permgroup.py and

Re: [sage-release] Re: Release process

More helpful would be the info which trac tickets in the integration branch cause these merge failures. While basing off the branch might be a no-no, adding some positively reviewed tickets as dependencies to a ticket does not break stuff, at least in my experience. I can discover these

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

On Thursday, May 10, 2018 at 9:22:06 AM UTC+1, François Bissey wrote: > > It is probably an oversight or a corner case in > https://trac.sagemath.org/ticket/20382 > > > Do

[sage-release] Re: Sage 8.2 released

Well, fire up gdb, look at the place it crashes... It is python3, right? So it would help to see what F28 does with python3, and why it works outside of sage. -- 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 8.3.beta0 released

there is nothing wrong in having more than one source tarball, one with essential stuff, and one with relatively little-used, such as curl etc. many systems do this, if only to save on storage and bandwidth. bedides, downloading big files might be slow, some IPs might trigger throttling... --

[sage-release] Re: Sage 8.2 released

You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known to Python people this this does not work... Can you install gcc-7 and make it the default compiler? On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote: > > I was unable to compile it in Fedora 28. I attach

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

I can't reproduce this on OSX 10.13 Xeon machine, with 8.2.rc3 + #23353 and + #24969 built from scratch with clang/clang++ Perhaps #24969 would fix your error? Or maybe it's because of $ ./sage SageMath version 8.2.rc3, Release Date: 2018-04-16 sage: from sage.doctest.external import

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

Does what they suggest, export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES before starting anything, help in Sage's case? Dima On Friday, April 20, 2018 at 10:26:57 AM UTC+1, Jeroen Demeyer wrote: > > On 2018-04-20 01:23, John H Palmieri wrote: > > objc[46054]: +[__NSPlaceholderDate initialize]

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

"objc_" error message might be a sign of a gcc runtime incompatibility, perhaps. -- 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 8.2.rc2 released

#25118 has a fix for the OSX issue on #25113, it would be great to get it in (and so clang default on OSX). On Wednesday, April 11, 2018 at 12:25:27 AM UTC+1, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the

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

All right, I've switched the default branch back to master. On Thursday, March 29, 2018 at 2:20:30 PM UTC+1, Eric Gourgoulhon wrote: > > > > Le jeudi 29 mars 2018 14:16:22 UTC+2, Dima Pasechnik a écrit : >> >> >> >> On Thursday, March 29, 2018 at 12:31

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

On Thursday, March 29, 2018 at 12:31:15 PM UTC+1, Eric Gourgoulhon wrote: > > Hi, > > If one performs > git clone https://github.com/sagemath/sage.git > one gets the develop branch, not the master one: > cd sage > git branch -v > returns > * develop e5c848a Updated SageMath version to 8.2.rc0 >

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

On Wednesday, March 14, 2018 at 9:06:08 PM UTC, vdelecroix wrote: > > Congratulations Erik! You found the field with one element in SageMath: > >https://en.wikipedia.org/wiki/Field_with_one_element > > I am really impressed. > I think Sagemath project should be awarded Fields Medal for

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

On Wednesday, March 14, 2018 at 3:34:20 PM UTC, Sébastien Labbé wrote: > > On Ubuntu 16.04, my first attempt at running make finishes with a problem > with giac (undefined reference to `png_set_longjmp_fn') > > The log finishes with: > > ... > [giac-1.4.9.45.p2] libtool: link: g++ -g -O2

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

On Saturday, February 10, 2018 at 2:09:58 PM UTC, Ralf Stephan wrote: > > Also clang-5.0.0 cannot compile ppl. clang-3.8 and 4.0.1 are fine. > https://trac.sagemath.org/ticket/24704 > I think I reported this on PPL bug tracker some time ago... > > > On Sat, Feb 10, 2018 at 2:52 PM Ralf

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

> > Justin > > > > > Seems signals are not caught on your system? > > > > On Sat, Dec 30, 2017 at 7:11 AM Dima Pasechnik <dim...@gmail.com > > wrote: > > I am getting a segfault in sage/matrix/matrix_integer_dense.pyx > > namely, at line 222.

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

> > Seems signals are not caught on your system? > Well, this is the only test in ptestlong that crashes for me. > > On Sat, Dec 30, 2017 at 7:11 AM Dima Pasechnik <dim...@gmail.com > > wrote: > >> I am getting a segfault in sage/matrix/matrix_integer_dense.pyx &g

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

I am getting a segfault in sage/matrix/matrix_integer_dense.pyx namely, at line 222. This also crashes at the console: sage: Matrix(ZZ, sys.maxsize, sys.maxsize) *** Error in `python': free(): invalid size: 0x04888190 ***

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

On Sat, Dec 16, 2017 at 4:41 AM, kcrisman wrote: > > > >> 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

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

branches that they (the pointers to them) should be kept in a database :-) On 15 Dec 2017 21:26, "Andrey Novoseltsev" <novos...@gmail.com> wrote: > On Friday, 15 December 2017 03:48:43 UTC-7, Dima Pasechnik wrote: >> >> >> >> On Friday, December 15, 2

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

On Friday, December 15, 2017 at 7:26:24 AM UTC, Dima Pasechnik wrote: > > On Fri, Dec 15, 2017 at 5:34 AM, Andrey Novoseltsev <novos...@gmail.com> > wrote: > > On Thursday, 14 December 2017 07:19:26 UTC-7, Dima Pasechnik wrote: > >> > >> On Thu, Dec 14

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

On Fri, Dec 15, 2017 at 5:34 AM, Andrey Novoseltsev <novos...@gmail.com> wrote: > On Thursday, 14 December 2017 07:19:26 UTC-7, Dima Pasechnik wrote: >> >> On Thu, Dec 14, 2017 at 12:38 PM, Volker Braun <vbrau...@gmail.com> wrote: >> > I thought we usually

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

On Thu, Dec 14, 2017 at 12:38 PM, Volker Braun wrote: > I thought we usually push to github as part of a git hook on trac, though I > haven't checked. on https://github.com/sagemath/sage we only have develop and master branches, rather than the full mirror. In fact, is

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

On Thursday, December 14, 2017 at 10:49:56 AM UTC, Erik Bray wrote: > > On Thu, Dec 14, 2017 at 11:36 AM, Dima Pasechnik <dim...@gmail.com > > wrote: > > > > > > On Thursday, December 14, 2017 at 9:53:11 AM UTC, François Bissey wrote: > >> > &

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

> that make sense to trac I guess. > > At some point I proposed to have such a mirror as I am running now privately to be in https://github.com/sagemath organisation, but have not heard back from anyone... > François > > > On 14/12/2017, at 22:30, Dima Pasec

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

On Wednesday, December 13, 2017 at 11:28:29 PM UTC, François Bissey wrote: > > Can we have an updated develop branch on github? > > in case, you can pull from here: https://github.com/dimpase/sagetrac-mirror > François > > > On 14/12/2017, at 12:03, Volker Braun >

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

? On Tuesday, December 5, 2017 at 5:24:19 PM UTC, Erik Bray wrote: > > On Tue, Dec 5, 2017 at 6:16 PM, Emmanuel Charpentier > <emanuel.c...@gmail.com > wrote: > > > > > > Le mardi 5 décembre 2017 18:03:19 UTC+1, Dima Pasechnik a écrit : > >> > >

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

In Oxford, a.t.m. the ping to the usual UK Sage mirror in 5ms from the university network; faster than usual. On Sunday, December 3, 2017 at 5:05:05 PM UTC, Eric Gourgoulhon wrote: > > > Le dimanche 3 décembre 2017 16:17:29 UTC+1, Ralf Stephan a écrit : >> >> What could be the reason that for me

[sage-release] Sage 8.1.rc3 released

Actually I think #24085 is fixed - pending final checks, but everything points in this direction for sure. -- 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 8.1.rc2 released

yes, this is a missing dependency of docbuilding on sympy. just restart the build... this is one of the current blocker tickets. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it,

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

math/sage/blob/develop/build/make/deps#L205 > > > >> On 19/11/2017, at 08:28, Dima Pasechnik <dim...@gmail.com > > wrote: > >> > >> so scipy is a missing dependency of docbuilding. > >> (not sure how to fix this) > >> > >> -

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

I've posted a branch there. Please review. On Saturday, November 18, 2017 at 10:05:03 PM UTC, Dima Pasechnik wrote: > > blocker : we need to support skylake. > the patch would be trivial, but how do I test it? Do we have a skylake > patchbot? > https://trac.sagemath.org/ticket

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

blocker : we need to support skylake. the patch would be trivial, but how do I test it? Do we have a skylake patchbot? https://trac.sagemath.org/ticket/24085 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and

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

so scipy is a missing dependency of docbuilding. (not sure how to fix 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

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

It might be that a dependency is missing somewhere. While building rc1, I had to start make for the 2nd time for no apparent reason. -- 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

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

I've tested this (with the necessary in the case of OSX 10.12) #12426+#23898 (thus, building with clang) and got one persistent timeout here: sage -t --long --warn-long 240.4 src/sage/rings/padics/padic_generic_element.pyx Namely, it is this test, and it takes over 10 minutes on my (old and

<    1   2   3   4   5   6   >