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 do

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

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

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 bet

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: ico.volume

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

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 <20100.delecr...@gmai

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

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

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 wrote

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

looks like a conflict with anaconda installation that you have... On Fri, 12 Apr 2019 19:32 darwin doppelganger, wrote: > Compiling sage-8.8.beta1 failed on my MacBook Pro (15-inch, 2017) running > MacOS 10.14.4, Xcode 10.2. > > I had previously compiled sage-8.8.beta0 with no problems, but > sa

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] 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 > http://www.sagemath.org/down

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

neither trac, nor the usual places on github or gitlab have the branch! On Wed, May 22, 2019 at 7:06 PM Timo Kaufmann wrote: > > There is no beta6 tag on github yet, is that still the canonical source? > > -- > You received this message because you are subscribed to the Google Groups > "sage-rel

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

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 th

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 releas

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

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] 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 - 10*

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 w

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 ha

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

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.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.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 > https://oeis.org/search?q=3

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 other

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

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

tached the output of ./configure --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,

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

ep 11, 2019 at 10:49 AM Mariel 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,

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

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

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 T

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 fil

Re: [sage-release] Sage 8.9 released

is package! 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

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

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

Fri, Oct 11, 2019 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

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

> On Wed, Oct 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, 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.

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

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

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

On Thu, Oct 24, 2019 at 9:42 PM Isuru Fernando wrote: > > Try adding `export SINGULAR_CONFIGURE="--without-python"` and then retry. > Looks like the system python installation is broken when building extensions. it's not even "system python", it's something in /usr/local/ > > Isuru > > On Thu

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

On Monday, October 7, 2019 at 5:24:07 PM UTC+3, Samuel Lelievre wrote: > > Volker wrote: > > > 533fd5d6cd (HEAD -> develop, tag: 9.0.beta0, trac/develop) Updated > SageMath version to 9.0.beta0 > > [...] > > > 93b86bfad3 Trac #24824: Update GLPK to 4.65 > > [...] > > On Cygwin64 on Windows

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

On Wed, Oct 30, 2019 at 2:27 AM Samuel Lelièvre wrote: > > Tue 2019-10-29 06:30 UTC, Dima Pasechnik: > > > > On Monday, October 7, 2019 at 5:24:07 PM UTC+3, Samuel Lelievre wrote: > >> > >> Volker wrote: > >> > >> > 533fd5d6c

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

it looks as if you did not install glpk package, for config.log says that glpk.h is not there. On Thu, 31 Oct 2019, 03:54 Samuel Lelièvre, wrote: > Thanks Dima for your suggestions. Following them, > I installed more cygwin packages, then ran > > git pull origin develop > make distclea

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

On Thu, 31 Oct 2019, 03:54 Samuel Lelièvre, wrote: > Thanks Dima for your suggestions. Following them, > I installed more cygwin packages, then ran > > git pull origin develop > make distclean > make configure > ./configure --with-python=3 > make -j4 > > The build, now aiming

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

On Tue, Nov 19, 2019 at 1:59 PM E. Madison Bray wrote: > > On Tue, Nov 19, 2019 at 2:55 PM E. Madison Bray wrote: > > > > On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé wrote: > > > > > > > > > > > > > > > The first try at running make gives me this: > > > > > > > > > [sagelib-9.0.beta6] make[4

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

Probably anaconda conflict, do you have pkg-config installed, so that pkg-config --libs libpng outputs a path to anaconda? I guess matplotlib does not use pkg-config, so it can't find libpng in an unusual location. On Wed, Nov 20, 2019 at 7:57 PM Paul Masson wrote: > > On macOS 10.15.1, after

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

please post config.log you have a mysterious copy of libpng somewhere... On Wed, Nov 20, 2019 at 9:36 PM Paul Masson wrote: > > I do not have anaconda installed. Building from the git repository with no > package managers. > > On Wednesday, November 20, 2019 at 1:31:10 PM UTC-8,

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

>> > package managers. >> > >> > On Wednesday, November 20, 2019 at 1:31:10 PM UTC-8, Dima Pasechnik wrote: >> >> >> >> Probably anaconda conflict, do you have pkg-config installed, so that >> >> >> >> pkg-config --libs lib

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

also please post the output of libpng-config --prefix On Wed, Nov 20, 2019 at 10:05 PM Dima Pasechnik wrote: > > hmm, strange. So it is found somewhere, not clear where. One way to > see is to check linking of libgd > > otool -L local/lib/libgd.dylib > > or perhaps i

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

patibility version 1.0.0, current version > 1281.0.0) > > > And the second: > > > libpng-config --prefix > > /usr/local/Cellar/libpng/1.6.34 > > > On Wednesday, November 20, 2019 at 2:12:17 PM UTC-8, Dima Pasechnik wrote: >> >> also please

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

6.34/include/libpng16 > > > libpng-config --ldflags > > -L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 > > > Guess I'll do a manual install with Homebrew unless there is a better idea. > > > On Wednesday, November 20, 2019 at 2:38:21 PM UTC-8, Dima Pasechnik wrote:

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

bpng by doing ./configure --without-system-png before running make Hope this explains. > > On Wednesday, November 20, 2019 at 3:38:12 PM UTC-8, Dima Pasechnik wrote: >> >> you can do >> >> brew install libpng >> >> which would install libpng 1.6.37 int

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

On Thu, Nov 21, 2019 at 12:35 AM Dima Pasechnik wrote: > > On Wed, Nov 20, 2019 at 11:56 PM Paul Masson wrote: > > > > I'd like to understand why this is now necessary. I've been building Sage > > on this Mac for several years without having this happen. I thin

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

al/lib/libpng.dylib present? > On Wednesday, November 20, 2019 at 4:36:02 PM UTC-8, Dima Pasechnik wrote: >> >> On Wed, Nov 20, 2019 at 11:56 PM Paul Masson >> wrote: >> > >> > I'd like to understand why this is now necessary. I've been buildi

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

talling >> libpng and pkg-config? What does "brew list" say? >> >> >> On Thursday, November 21, 2019 at 1:43:05 PM UTC-8, Paul Masson wrote: >>> >>> Both are present as symlinks >>> >>> On Thursday, November 21, 2019 at 1:35:24 PM

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

IIRC this comes from Simon King's optional package. On Wed, 27 Nov 2019, 16:11 John Cremona, wrote: > I had this failure (I have gap_packages installed): > > sage -t --long --warn-long 59.7 src/sage/tests/gap_packages.py > ** >

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

Since https://trac.sagemath.org/ticket/28459 Sage can use GLPK from the system, if it's version 4.63 or newer. Sage has 4.65. The slight discrepancy in GLPK tests is due to this version difference, and it's harmless. (I set it to 4.63 to cover many more Linux distros) On Wed, Nov 27, 2019 at 9:28

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

there is also a small GLPK 4.65 discrepancy coming from a patch that Sage applies, but most distros don't. On Wed, Nov 27, 2019 at 9:39 PM Dima Pasechnik wrote: > > Since https://trac.sagemath.org/ticket/28459 > Sage can use GLPK from the system, if it's version 4.63 or newe

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

emigroups/issues/615 nothing to do with your package. Best Dima > > Best regards, > Simon > > On 2019-11-27, Dima Pasechnik wrote: > > IIRC this comes from Simon King's optional package. > > > > On Wed, 27 Nov 2019, 16:11 John Cremona, wrote: > > > >&

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

what does happen if you run sage: from sage.graphs.strongly_regular_db import SRG_280_135_70_60 sage: SRG_280_135_70_60() Does it print J_2 on cosets of 3.PGL(2,9): Graph on 280 vertices ? On Thu, 28 Nov 2019, 19:06 Emmanuel Charpentier, < emanuel.charpent...@gmail.com> wrote: > After rebuil

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

On Thu, Nov 28, 2019 at 7:45 PM Dima Pasechnik wrote: > > what does happen if you run > > sage: from sage.graphs.strongly_regular_db import SRG_280_135_70_60 > sage: SRG_280_135_70_60() > > Does it print > > J_2 on cosets of 3.PGL(2,9): Graph on 280 vertices here is

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

be >> fast...). >> >> Le vendredi 29 novembre 2019 00:52:43 UTC+1, Dima Pasechnik a écrit : >>> >>> On Thu, Nov 28, 2019 at 7:45 PM Dima Pasechnik wrote: >>> > >>> > what does happen if you run >>> > >>> > sage:

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

On Fri, Nov 29, 2019 at 1:36 PM Emmanuel Charpentier wrote: > > > > Le vendredi 29 novembre 2019 12:43:55 UTC+1, Dima Pasechnik a écrit : >> >> on that machine, could you >> >> ./sage -f gap_packages >> >> and try again? > > > Done. No rel

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

the easiest might be to build pythonX if --with-python=X is specified. On Mon, Dec 2, 2019 at 6:42 AM François Bissey wrote: > > Yes. sagenb is no a real optional package even with python2. We overlooked > the test suite when we made some test depending on it just “# py2”. > That was in https://t

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

On Monday, December 2, 2019 at 6:01:36 PM UTC, Emmanuel Charpentier wrote: > > On a slightly larger machine (Debian testing running on core i7 + 16 GB > RAM, slightly different packages), ptestalllong gets 9 transient and 3 > permanent failures: > > Running doctests with ID 2019-12-02-17-03-31

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

Volker, can we please get #28883 and #27870 (highly anticipated, allows the use of openblas from the system, modifies ./configure) in 9.0? On Sunday, December 8, 2019 at 9:41:25 PM UTC, Volker Braun wrote: > > As always, you can get the latest beta versi

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

In flint log there are errors about "unknown type constexpr", which seem to indicate that c++ compiler needs "-std=c++11", which did not make it through somehow, and Apple's clang has a weird default -std= value. Try building flint as follows: CXXFLAGS="$CXXFLAGS -std=c++" ./sage -i flint (or p

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

On Mon, 30 Dec 2019, 18:23 Harald Schilly, wrote: > I'm not sure how interesting this is, but still ... I made a clean build > from the git sources. I got many doctests failures, and each one I checked > failed due to additional lines "Long-step dual simplex will be used" -- > see: https://trac.s

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

On Mon, Dec 30, 2019 at 10:43 PM Timo Kaufmann wrote: > > Am Montag, 30. Dezember 2019 12:59:36 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Mon, 30 Dec 2019, 18:23 Harald Schilly, wrote: >>> >>> I'm not sure how interesting this is, but sti

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

On Tue, Dec 31, 2019 at 12:00 AM E. Madison Bray wrote: > > On Sat, Dec 28, 2019 at 8:41 PM Samuel Lelièvre > wrote: > > > > Le sam. 28 déc. 2019 à 02:12, Samuel Lelièvre: > > > > > > Computer, OS, build choices: > > > > > > - iMac, Mid 2015 > > > - macOS 10.14.6 Mojave > > > - build for Python 2

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

On Tue, Dec 31, 2019 at 6:39 AM Volker Braun wrote: > > Is that running with 4 threads and the 4GB model? 10h wall time is long but > just about fast enough that we could set up a buildbot if it just needs to be an ARM 64, there are more powerful SoC boards, e.g. https://www.seeedstudio.com/

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

you might have remains of unmerged tickets with spkg-configure for openblas etc. Check that you don't have links to *blas.pc files in local/lib/pkgconfig/ On Tue, 31 Dec 2019, 18:13 Frédéric Chapoton, wrote: > Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-70-generic x86_64) > > This fails in t

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

019 11:36:21 UTC+1, Dima Pasechnik a écrit : >> >> you might have remains of unmerged tickets with spkg-configure for >> openblas etc. Check that you don't have links to *blas.pc files in >> local/lib/pkgconfig/ >> >> On Tue, 31 Dec 2019, 18:13 Frédéric Chapot

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

lding R still fails > in the same way. > > F > > Le mardi 31 décembre 2019 12:14:15 UTC+1, Frédéric Chapoton a écrit : >> >> I have launched "sage -f openblas", and this is re-building many things. Now >> building giac, so probably succedeed in building ope

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

Le mardi 31 décembre 2019 16:18:34 UTC+1, Dima Pasechnik a écrit : >> >> It's probably >> https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/index.html >> - and you have a slightly broken "new" gfortran... >> >> Sorr

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

On Tue, Dec 31, 2019 at 11:32 PM Dima Pasechnik wrote: > > On Tue, Dec 31, 2019 at 11:23 PM Frédéric Chapoton > wrote: > > > > So what would be a practical solution in my case ? > > > on a developent box (thsi won't do for buildbots etc, naturally) you can pu

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

On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich wrote: > > > > make build after pulling 9.1.beta0 produces an error below. I have no > problems compiling 9.0. > This is on centos 7 with devtoolset-4 enabled. > Sorry if this is noise produced by me making an error. Happy to provide any > other in

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

On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich wrote: > > > > make build after pulling 9.1.beta0 produces an error below. I have no > problems compiling 9.0. > This is on centos 7 with devtoolset-4 enabled. https://www.softwarecollections.org/en/scls/rhscl/devtoolset-4/ says that devtoolset-4 i

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

On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release wrote: > > Dear all, > > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build (incremental > from a relatiively recent release, but I don't remember which) on Ubuntu > 18.04.3, and I have absolutely no clue. The last bit of t

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

ks for your help - unfortunately it didn't work though. > > I am attaching the new config.log > > Martin > > Am Mittwoch, 15. Januar 2020 10:19:35 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release >> wrote:

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

r-clean > > The new config.log is attached. > > Sorry and thank you! > > Am Mittwoch, 15. Januar 2020 11:13:09 UTC+1 schrieb Dima Pasechnik: >> >> It seems you have remains of an old R installation in local/ >> So you need >> rm -rf local/lib/R

  1   2   3   4   5   6   7   >