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

I'm curious: why is the 8.2.beta8 tarball so much smaller than previous versions? (According to http://files.sagemath.org/devel/index.html, 8.2beta8 is about 530MB, while 8.2.beta7 was just under 600MB.) John On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, Volker Braun wrote: > > As

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

2018-03-16 12:56 GMT+01:00 kcrisman : > > I guess Sage *is* under 40 as of yet! Depends how you count. The summarny at Openhub https://www.openhub.net/p/sage says it took an estimated 172 years of effort! This is according to an analysis using the Constructive Cost

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

> this is a typical symptom of trying to link a wrong version of libpng. > Yes, but why does the `sage -f libpng` was not forced since it was necessary? I am not an expert at all on this, but from my point of view, it is like if there was problem with dependencies of giac. > > But what

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

On Thu, Mar 15, 2018 at 7:26 AM, Jeroen Demeyer wrote: > On 2018-03-14 19:02, Erik Bray wrote: >> >> two Integers' mpz_t structs' _mp_d >> member (the array of limbs) is being set to the same memory address. > > > You really mean two different Integer objects with the same

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

On Wed, Mar 14, 2018 at 10:03 PM, Vincent Delecroix <20100.delecr...@gmail.com> 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. Hah! Yes, I was extremely confused as to why Sage

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

On Wed, Mar 14, 2018 at 8:33 PM, Jeroen Demeyer wrote: > On 2018-03-14 19:02, Erik Bray wrote: >> >> I see now--less likely a bug with MPIR/GMP itself, and more likely a >> bug with Sage's fast_tp_new stuff for Integer. > > > I don't know whether it will fix that bug or not,

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

On 2018-03-14 19:02, Erik Bray wrote: two Integers' mpz_t structs' _mp_d member (the array of limbs) is being set to the same memory address. You really mean two different Integer objects with the same _mp_d (as opposed to the same Integer object being used mistakenly in two different

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

Congratulations Erik! You found the field with one element in SageMath: https://en.wikipedia.org/wiki/Field_with_one_element I am really impressed. Vincent On 14/03/2018 16:49, Erik Bray wrote: I am now pretty consistently getting the following failure on Cygwin with 8.2beta8 (although

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

> On 15/03/2018, at 04:34, 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.beta8 released

On 2018-03-14 19:02, Erik Bray wrote: I see now--less likely a bug with MPIR/GMP itself, and more likely a bug with Sage's fast_tp_new stuff for Integer. I don't know whether it will fix that bug or not, but there is a long-standing ticket to improve those hacks at

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

On Wed, Mar 14, 2018 at 6:41 PM, Erik Bray wrote: > On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray wrote: >> I am now pretty consistently getting the following failure on Cygwin >> with 8.2beta8 (although strangely I've run the test once or twice with >>

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

On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray wrote: > I am now pretty consistently getting the following failure on Cygwin > with 8.2beta8 (although strangely I've run the test once or twice with > success too...): > > sage -t --warn-long 164.8

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

> ... still running. > > make ptestlong eventually finished with: -- All tests passed! -- -- You received this message because you are subscribed to the

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

I am now pretty consistently getting the following failure on Cygwin with 8.2beta8 (although strangely I've run the test once or twice with success too...): sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx ** File

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

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 -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -Wl,-rpath

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

It would be good to have a final review on #21828, as OpenSuSE systems still fail doctests and so cannot participate as patchbots. On Tue, 13 Mar 2018, 11:26 Ralf Stephan, wrote: > This is #24918 that was too late to be merged, apparently. > > On Tue, 13 Mar 2018, 11:19 Eric

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

This is #24918 that was too late to be merged, apparently. On Tue, 13 Mar 2018, 11:19 Eric Gourgoulhon, wrote: > On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + > pull develop, parallel (-j16) build OK and make ptestlong failed with one >

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

On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull develop, parallel (-j16) build OK and make ptestlong failed with one doctest in src/sage/interacts/test_jupyter.rst as already reported for 8.2.beta7. The doctest is passed when run standalone. Eric. -- You

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

FWIW, builds and passes ptestlong with no failure whatsoever on Debian running on Core I7 + 16 GB RAM. -- Emmanuel Charpentier Le dimanche 11 mars 2018 01:18:24 UTC+1, Volker Braun a écrit : > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the

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

On Saturday, March 10, 2018 at 7:17:24 PM UTC-8, John H Palmieri wrote: > > On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, 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] Re: Sage 8.2.beta8 released

Sage 8.2.beta8 is badly breaking the optional package meataxe. See https://trac.sagemath.org/ticket/24947 Vincent -- 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

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

> Built without any problem. However, I am no longer able to run doctests on > my system (Ubuntu 17.04) with 8.2.beta8: > > Actually, this seems to be an issue with system as I get a similar error with an older version of Sage. I will instead most the post to sage-devel. Sorry for the noise

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

On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > 9bf9f05f1f (tag: 8.2.beta8,