Sage 8.8.rc1 released

[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 

8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1

8555a05c7d Trac #27467: weak order of permutations broken

82e9b286db Trac #27883: AsymptoticRing: pass log-function more systematically

2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0

[E. Madison Bray]

Could somebody please review the following ticket: https://trac.sagemath.org/ticket/27721

It has been stalled for weeks now for no good reason other than, I presume, lack of availability for someone to review it. 

I would really like this ticket to be resolved and merged before making an 8.8 release because it's a regression that was introduced earlier in the 8.8 development. 

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[E. Madison Bray]

(Accidentally sent before completing the message)

Could somebody please review the following ticket: https://trac.sagemath.org/ticket/27721

It has been stalled for weeks now for no good reason other than, I presume, lack of availability for someone to review it. 

I would really like this ticket to be resolved and merged before making an 8.8 release because it's a regression that was introduced earlier in the 8.8 development.

I don't think we should be making a release with a known regression that IMO has a perfectly good fix that has only not been merged due to lacking a final sign-off by someone. I marked the issue as "critical" and not "blocker" only because I can technically work around it, but shouldn't have to.

Unless there's a serious reason to rush this release please resolve this issue first. 

[Volker Braun]

I reviewed the ticket but rather not merge it at the last minute. Imho its quite possible that it breaks something on lesser-used platforms so we should merge it at the beginning of a release cycle, not the end.

On Friday, June 14, 2019 at 10:59:37 AM UTC+2, E. Madison Bray wrote:

Could somebody please review the following ticket: https://trac.sagemath.org/ticket/27721

It has been stalled for weeks now for no good reason other than, I presume, lack of availability for someone to review it. 

I would really like this ticket to be resolved and merged before making an 8.8 release because it's a regression that was introduced earlier in the 8.8 development. 

On Fri, Jun 14, 2019, 08:40 Volker Braun <vbrau...@gmail.com> 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 

8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1

8555a05c7d Trac #27467: weak order of permutations broken

82e9b286db Trac #27883: AsymptoticRing: pass log-function more systematically

2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0

--
You received this message because you are subscribed to the Google Groups "sage-release" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

[E. Madison Bray]

Perhaps we could try it anyways. Is there any concrete reason this is the "end of a release cycle"?

It's not my fault if my ticket goes unreviewed for weeks and then suddenly it's just seemingly arbitrarily the end of the release cycle that wasn't communicated. 

To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/63e45eb6-fb07-4fb9-b272-83d16d674862%40googlegroups.com.

[Dima Pasechnik]

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.

[Eric Gourgoulhon]

On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:

- python2:

  - incremental build (from 8.8.rc0, with -j16) completed, with Sphinx complaining during the doc build:

     formatargspec() is now deprecated.  Please use sphinx.util.inspect.Signature instead

  - all tests from ptestlong passed

- python3:

  - incremental build (from 8.8.rc0, with -j16) completed, with the same Sphinx deprecation warning as with python 2.

  - all tests from ptest-python3 passed, except for 2 transient (i.e. passed when run standalone) doctests

    in src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py

Eric.

[E. Madison Bray]

This ticket has also been languishing for no particular reason:
https://trac.sagemath.org/ticket/27724

It was previously looked upon favorably: It is a patch to GAP that has
already been accepted upstream by the GAP developers. For a time it
was only held up for me to update the patch to the exact version
accepted upstream which I did a week ago. By all rights it could have
been included in the first release candidate; just no one got around
to giving it a positive review explicitly.

I would have prodded people to do so immediately if I had known that a
"release candidate" would be created a day after but how could I have?

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAAWYfq2S%3DkMgY3Bb7dLEE7Vp_3zt94XPYVbq22fL8BvW-03j%3DQ%40mail.gmail.com.

[darwin doppelganger]

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 some sluggishness in this respect before, but this seems exceptional.

I thought it was high time that I suck it up and actually use GitHub, so I timidly waded in by choosing the "Download ZIP" option. Then I went to the directory and typed "make" as usual, but it failed (patch-2.7.5.log enclosed). Maybe this doesn't even matter, because then I tried doing this the "right way(?)" by cloning it. The build is running now and it looks like everything is running smoothly.

None of this is really a problem for me, but I thought you might want to know. Cheers!

[Volker Braun]

thanks, fixed!

[Dima Pasechnik]

On Sat, Jun 15, 2019 at 10:51 PM darwin doppelganger <dan...@gmail.com> 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 some sluggishness in this respect before, but this seems exceptional.
>
> I thought it was high time that I suck it up and actually use GitHub, so I timidly waded in by choosing the "Download ZIP" option. Then I went to the directory and typed "make" as usual, but it failed (patch-2.7.5.log enclosed).

This seems to be a particular "feature" of your OS/unzip program
combination, at least on Linux permissions of the file mentioned in
the log are as they should be.

> Maybe this doesn't even matter, because then I tried doing this the "right way(?)" by cloning it. The build is running now and it looks like everything is running smoothly.
>
> None of this is really a problem for me, but I thought you might want to know. Cheers!
>
> On Friday, June 14, 2019 at 1:40:03 AM UTC-5, 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
>>
>>
>> 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
>> 8555a05c7d Trac #27467: weak order of permutations broken
>> 82e9b286db Trac #27883: AsymptoticRing: pass log-function more systematically
>> 2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0
>>

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/0aaa90aa-924d-4da2-a98e-46e4841187c6%40googlegroups.com.

[darwin doppelganger]

On Sunday, June 16, 2019 at 3:39:46 AM UTC-5, Dima Pasechnik wrote:

On Sat, Jun 15, 2019 at 10:51 PM darwin doppelganger <dan...@gmail.com> 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 some sluggishness in this respect before, but this seems exceptional.
>
> I thought it was high time that I suck it up and actually use GitHub, so I timidly waded in by choosing the "Download ZIP" option. Then I went to the directory and typed "make" as usual, but it failed (patch-2.7.5.log enclosed).

This seems to be a particular "feature" of your OS/unzip program
combination, at least on Linux permissions of the file mentioned in
the log are as they should be.

I had double-clicked on the .zip archive on my Mac, but I tried again just using the unzip command in the terminal and everything worked fine. Thanks!

I also grabbed the self-contained source tarball for Sage 8.8.rc1 that Volker posted in response to my earlier comment, and that also worked for me as per usual.

However, the build I had running from the GitHub clone eventually failed. It seems that the old Mac Mojave problem with /usr/include has resurfaced for me. I am running Mac OSX 10.14.4 with Xcode 10.2.1. Google Groups won't allow me to attach the whole 25MB gfortran-7.2.0.log file, but here is the section where the problem occurred:

[gfortran-7.2.0] /bin/sh ../../src/gcc/../move-if-change tmp-fixinc_list fixinc_list
[gfortran-7.2.0] echo timestamp > s-fixinc_list
[gfortran-7.2.0] rm -rf include-fixed; mkdir include-fixed
[gfortran-7.2.0] chmod a+rx include-fixed
[gfortran-7.2.0] if [ -d ../prev-gcc ]; then \
[gfortran-7.2.0] cd ../prev-gcc && \
[gfortran-7.2.0] make real-install-headers-tar DESTDIR=`pwd`/../gcc/ \
[gfortran-7.2.0] libsubdir=. ; \
[gfortran-7.2.0] else \
[gfortran-7.2.0] set -e; for ml in `cat fixinc_list`; do \
[gfortran-7.2.0] sysroot_headers_suffix=`echo ${ml} | sed -e 's/;.*$//'`; \
[gfortran-7.2.0] multi_dir=`echo ${ml} | sed -e 's/^[^;]*;//'`; \
[gfortran-7.2.0] fix_dir=include-fixed${multi_dir}; \
[gfortran-7.2.0] if ! false && test ! -d `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`; then \
[gfortran-7.2.0] echo The directory that should contain system headers does not exist: >&2 ; \
[gfortran-7.2.0] echo " `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" >&2 ; \
[gfortran-7.2.0] tooldir_sysinc=`echo "/Applications/sage/local/lib/gcc/x86_64-apple-darwin18.5.0/7.2.0/../../../../x86_64-apple-darwin18.5.0/sys-include" | sed -e :a -e "s,[^/]*/\.\.\/,," -e ta`; \
[gfortran-7.2.0] if test "x`echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" = "x${tooldir_sysinc}"; \
[gfortran-7.2.0] then sleep 1; else exit 1; fi; \
[gfortran-7.2.0] fi; \
[gfortran-7.2.0] /bin/sh ../../src/gcc/../mkinstalldirs ${fix_dir}; \
[gfortran-7.2.0] chmod a+rx ${fix_dir} || true; \
[gfortran-7.2.0] (TARGET_MACHINE='x86_64-apple-darwin18.5.0'; srcdir=`cd ../../src/gcc; ${PWDCMD-pwd}`; \
[gfortran-7.2.0] SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \
[gfortran-7.2.0] gcc_dir=`${PWDCMD-pwd}` ; \
[gfortran-7.2.0] export TARGET_MACHINE srcdir SHELL MACRO_LIST && \
[gfortran-7.2.0] cd ../build-x86_64-apple-darwin18.5.0/fixincludes && \
[gfortran-7.2.0] /bin/sh ./fixinc.sh "${gcc_dir}/${fix_dir}" \
[gfortran-7.2.0] `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta` ); \
[gfortran-7.2.0] rm -f ${fix_dir}/syslimits.h; \
[gfortran-7.2.0] if [ -f ${fix_dir}/limits.h ]; then \
[gfortran-7.2.0] mv ${fix_dir}/limits.h ${fix_dir}/syslimits.h; \
[gfortran-7.2.0] else \
[gfortran-7.2.0] cp ../../src/gcc/gsyslimits.h ${fix_dir}/syslimits.h; \
[gfortran-7.2.0] fi; \
[gfortran-7.2.0] chmod a+r ${fix_dir}/syslimits.h; \
[gfortran-7.2.0] done; \
[gfortran-7.2.0] fi
[gfortran-7.2.0] The directory that should contain system headers does not exist:
[gfortran-7.2.0] /usr/include
[gfortran-7.2.0] make[6]: *** [stmp-fixinc] Error 1
[gfortran-7.2.0] make[5]: *** [all-gcc] Error 2
[gfortran-7.2.0] make[4]: *** [all] Error 2
[gfortran-7.2.0] ********************************************************************************
[gfortran-7.2.0] Error building gfortran-7.2.0

When I built Sage 8.8.rc1 from the GitHub .zip file, the gfortran-7.2.0.log file (at the same point) says:

Fixing headers into /Applications/sage-develop/local/var/tmp/sage/build/gfortran-7.2.0/gcc-build/gcc/include-fixed for x86_64-apple-darwin18.5.0 target
No forbidden identifiers defined by this target
Finding directories and links to directories
...

And then the build successfully runs to completion.

This is not really a problem for me, because I can always use the tarball or the GitHub .zip file. I just thought I would record it for future reference. Thanks for everything!