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

[Samuel Lelievre]

Le mardi 18 janvier 2022 à 02:37:20 UTC, Marc Culler on sage-release:

> That worked like a charm!
>
>   * frame #0: 0x83c0f9024900
> frame #1: 0x000153ff8b7c 
> _dop.cpython-39-darwin.so`PyFortranObject_New 
> + 40
> frame #2: 0x000153ff66fc _dop.cpython-39-darwin.so`PyInit__dop + 
> 1020
>
> [...]
>
> If anyone knows what dop stands for, I am all ears.
>

It seems "DOP" or "DOPRI" or "RKDP" stand for "Dormand & Prince"
or "Runge-Kutta-Dormand-Prince" and refer to a method, or family
of methods (of the Runge-Kutta family), devised  by these authors
for numerically solving ordinary differential equations.

See:

https://en.wikipedia.org/wiki/Dormand–Prince_method
https://docs.scipy.org/doc/scipy/reference/generated/scipy.integrate.DOP853.html
http://www.unige.ch/~hairer/prog/nonstiff/dop853.f

In particular, the file "dop853.f", linked to above, states  "DOP853"
is "an explicit Runge-Kutta method of order 8(5,3) due to Dormand
& Prince (with stepsize control and dense output)".

These abbreviation seem common in the world of numerical methods
for solving ordinary differential equations but so far that meaning
of DOP is missing from the wikipedia disambiguation page

https://en.wikipedia.org/wiki/DOP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/8ff24293-3a80-4d65-9275-46ed122a2950n%40googlegroups.com.

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

[Matthias Köppe]

Yes, the fortran runtime is needed. I've 
opened https://trac.sagemath.org/ticket/33203 for this...

On Monday, January 17, 2022 at 6:37:20 PM UTC-8 marc@gmail.com wrote:

> That worked like a charm!
>
>   * frame #0: 0x83c0f9024900
> frame #1: 0x000153ff8b7c 
> _dop.cpython-39-darwin.so`PyFortranObject_New 
> + 40
> frame #2: 0x000153ff66fc _dop.cpython-39-darwin.so`PyInit__dop + 
> 1020
>
> And it turns out that this problem was independently reported by William 
> Stein.  I used an external gfortran compiler installed in /usr/local to 
> build this sage.  So I need to also embed the fortran runtime library into 
> my Sage.framework and patch the load paths of all executable files that 
> load it.  This would be a lot easier if someone could get the gfortran spkg 
> to build on an M1 CPU.
>
> Anyway, thanks!  I think I am on track to make this work now.
>
> If anyone knows what dop stands for, I am all ears.
>
> - Marc
>
> On Mon, Jan 17, 2022 at 5:35 PM Matthias Köppe  
> wrote:
>
>> Use "./sage -sh" and run python / the debugger from there?
>>
>> On Monday, January 17, 2022 at 2:35:38 PM UTC-8 marc@gmail.com wrote:
>>
>>> I get the same exception on both Intel and Arm when I try to import 
>>> sage.all from the sage python.  There is no exception if I do the same 
>>> import in sage -python.  But that is no help in terms of running lldb.  
>>> However, perhaps if I knew how to set up the correct environment first I 
>>> would be able to start the sage python in lldb and then actually be able to 
>>> do the import.
>>>
>>> - Marc
>>>
>>>
>>> On Monday, January 17, 2022 at 3:18:05 PM UTC-6 matthia...@gmail.com 
>>> wrote:
>>>
 Try "import sage.all" first.

 On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com 
 wrote:

> While many things work in the binary macOS app for Arm CPU, I 
> discovered by accident that the following produces a segfault:
>
> sage: M = Manifold()
>
> In fact, even trying to import manifold from sage.manifolds 
> segfaults.  This does not happen on the Intel version of the app built 
> from 
> the same branch of the repository.
>
> I have not been able to run a debugger on sage at all.  Of course 
> cysignals cannot produce a backtrace on macOS.  With lldb -p I get an 
> error 
> saying that lldb is not allowed to attach to the process and referring me 
> to non-existent messages in system.log for explanations.  Running the 
> debugserver directly produces:
> error: failed to attach process 6619: unable to start the exception 
> thread
>
> This occurs even if I run sage directly in the repo after the build 
> finishes - it does not have anything to do with the app.  (And the 
> debugger 
> similarly refuses to attach to the process.)  I tried to run the debugger 
> as root and I also tried adding debugger entitlements and resigning the 
> app.  Neither make it possible for me to use lldb on sage itself.
>
> I am able to start the sage python3 in lldb.  If I knew how to import 
> the Manifold class from python I might be able to get somewhere.  But if 
> I 
> run
> >>> from sage.manifolds import manifold
> I get a python exception whose traceback ends with:
> File "sage/structure/category_object.pyx", line 60, in init 
> sage.structure.category_object 
> (build/cythonized/sage/structure/category_object.c:9914)
> ImportError: cannot import name Category
>
> - Marc
>
> On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:
>
>> Hi Matthias,
>>
>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm 
>> CPUs at 
>> https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>> There are two separate disk images.  You may recall that I do not use 
>> Homebrew or Conda, but I did have to use an experimental binary release 
>> of 
>> gfortran for M1 since I was not able to build the gfortran spkg.
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 
>> matthia...@gmail.com wrote:
>>
> Based on the runs on GH Actions, I have updated the summary of 
>>> platform support in 
>>> https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>>
>>> TL;DR: It's all good now on all platforms tested on GH Actions, 
>>> including Cygwin.
>>> But I would urge that 9.5 still merge the positively reviews tickets 
>>> marked "critical"/"blocker", such as 
>>> https://trac.sagemath.org/ticket/29285 (which fixes the build in 
>>> the presence of pyenv).
>>> Also *note we have absolutely no automatic testing for the Apple 
>>> Silicon (M1) platform.* So it would be good if users/developers who 
>>> have access to this platform test the release candidate.
>>>
>>>
>>>
>>> On Friday, January 14, 2022 at 

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

[Marc Culler]

That worked like a charm!

  * frame #0: 0x83c0f9024900
frame #1: 0x000153ff8b7c _dop.cpython-39-darwin.so`PyFortranObject_New
+ 40
frame #2: 0x000153ff66fc _dop.cpython-39-darwin.so`PyInit__dop +
1020

And it turns out that this problem was independently reported by William
Stein.  I used an external gfortran compiler installed in /usr/local to
build this sage.  So I need to also embed the fortran runtime library into
my Sage.framework and patch the load paths of all executable files that
load it.  This would be a lot easier if someone could get the gfortran spkg
to build on an M1 CPU.

Anyway, thanks!  I think I am on track to make this work now.

If anyone knows what dop stands for, I am all ears.

- Marc

On Mon, Jan 17, 2022 at 5:35 PM Matthias Köppe 
wrote:

> Use "./sage -sh" and run python / the debugger from there?
>
> On Monday, January 17, 2022 at 2:35:38 PM UTC-8 marc@gmail.com wrote:
>
>> I get the same exception on both Intel and Arm when I try to import
>> sage.all from the sage python.  There is no exception if I do the same
>> import in sage -python.  But that is no help in terms of running lldb.
>> However, perhaps if I knew how to set up the correct environment first I
>> would be able to start the sage python in lldb and then actually be able to
>> do the import.
>>
>> - Marc
>>
>>
>> On Monday, January 17, 2022 at 3:18:05 PM UTC-6 matthia...@gmail.com
>> wrote:
>>
>>> Try "import sage.all" first.
>>>
>>> On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com
>>> wrote:
>>>
 While many things work in the binary macOS app for Arm CPU, I
 discovered by accident that the following produces a segfault:

 sage: M = Manifold()

 In fact, even trying to import manifold from sage.manifolds segfaults.
 This does not happen on the Intel version of the app built from the same
 branch of the repository.

 I have not been able to run a debugger on sage at all.  Of course
 cysignals cannot produce a backtrace on macOS.  With lldb -p I get an error
 saying that lldb is not allowed to attach to the process and referring me
 to non-existent messages in system.log for explanations.  Running the
 debugserver directly produces:
 error: failed to attach process 6619: unable to start the exception
 thread

 This occurs even if I run sage directly in the repo after the build
 finishes - it does not have anything to do with the app.  (And the debugger
 similarly refuses to attach to the process.)  I tried to run the debugger
 as root and I also tried adding debugger entitlements and resigning the
 app.  Neither make it possible for me to use lldb on sage itself.

 I am able to start the sage python3 in lldb.  If I knew how to import
 the Manifold class from python I might be able to get somewhere.  But if I
 run
 >>> from sage.manifolds import manifold
 I get a python exception whose traceback ends with:
 File "sage/structure/category_object.pyx", line 60, in init
 sage.structure.category_object
 (build/cythonized/sage/structure/category_object.c:9914)
 ImportError: cannot import name Category

 - Marc

 On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:

> Hi Matthias,
>
> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm
> CPUs at
> https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.
> There are two separate disk images.  You may recall that I do not use
> Homebrew or Conda, but I did have to use an experimental binary release of
> gfortran for M1 since I was not able to build the gfortran spkg.
>
> - Marc
>
> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com
> wrote:
>
 Based on the runs on GH Actions, I have updated the summary of platform
>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions,
>> including Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets
>> marked "critical"/"blocker", such as
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple
>> Silicon (M1) platform.* So it would be good if users/developers who
>> have access to this platform test the release candidate.
>>
>>
>>
>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>
>>> On Thursday, January 13, 2022 at 3:22:03 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

 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, 

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

[Matthias Köppe]

Use "./sage -sh" and run python / the debugger from there?

On Monday, January 17, 2022 at 2:35:38 PM UTC-8 marc@gmail.com wrote:

> I get the same exception on both Intel and Arm when I try to import 
> sage.all from the sage python.  There is no exception if I do the same 
> import in sage -python.  But that is no help in terms of running lldb.  
> However, perhaps if I knew how to set up the correct environment first I 
> would be able to start the sage python in lldb and then actually be able to 
> do the import.
>
> - Marc
>
>
> On Monday, January 17, 2022 at 3:18:05 PM UTC-6 matthia...@gmail.com 
> wrote:
>
>> Try "import sage.all" first.
>>
>> On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com wrote:
>>
>>> While many things work in the binary macOS app for Arm CPU, I discovered 
>>> by accident that the following produces a segfault:
>>>
>>> sage: M = Manifold()
>>>
>>> In fact, even trying to import manifold from sage.manifolds segfaults.  
>>> This does not happen on the Intel version of the app built from the same 
>>> branch of the repository.
>>>
>>> I have not been able to run a debugger on sage at all.  Of course 
>>> cysignals cannot produce a backtrace on macOS.  With lldb -p I get an error 
>>> saying that lldb is not allowed to attach to the process and referring me 
>>> to non-existent messages in system.log for explanations.  Running the 
>>> debugserver directly produces:
>>> error: failed to attach process 6619: unable to start the exception 
>>> thread
>>>
>>> This occurs even if I run sage directly in the repo after the build 
>>> finishes - it does not have anything to do with the app.  (And the debugger 
>>> similarly refuses to attach to the process.)  I tried to run the debugger 
>>> as root and I also tried adding debugger entitlements and resigning the 
>>> app.  Neither make it possible for me to use lldb on sage itself.
>>>
>>> I am able to start the sage python3 in lldb.  If I knew how to import 
>>> the Manifold class from python I might be able to get somewhere.  But if I 
>>> run
>>> >>> from sage.manifolds import manifold
>>> I get a python exception whose traceback ends with:
>>> File "sage/structure/category_object.pyx", line 60, in init 
>>> sage.structure.category_object 
>>> (build/cythonized/sage/structure/category_object.c:9914)
>>> ImportError: cannot import name Category
>>>
>>> - Marc
>>>
>>> On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:
>>>
 Hi Matthias,

 I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm 
 CPUs at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
 There are two separate disk images.  You may recall that I do not use 
 Homebrew or Conda, but I did have to use an experimental binary release of 
 gfortran for M1 since I was not able to build the gfortran spkg.

 - Marc

 On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
 wrote:

>>> Based on the runs on GH Actions, I have updated the summary of platform 
> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>
> TL;DR: It's all good now on all platforms tested on GH Actions, 
> including Cygwin.
> But I would urge that 9.5 still merge the positively reviews tickets 
> marked "critical"/"blocker", such as 
> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
> presence of pyenv).
> Also *note we have absolutely no automatic testing for the Apple 
> Silicon (M1) platform.* So it would be good if users/developers who 
> have access to this platform test the release candidate.
>
>
>
> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>
>> On Thursday, January 13, 2022 at 3:22:03 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
>>>
>>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
>>> SageMath version to 9.5.rc1
>>>
>>
>> Thanks for the new rc. Tests are running at 
>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, 
>> macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 
>> (Cygwin).
>>
>>
>>
>>
>>
>>  
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/8124ca5a-7893-4f48-b3cc-af37c51d144cn%40googlegroups.com.

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

[Marc Culler]

I get the same exception on both Intel and Arm when I try to import 
sage.all from the sage python.  There is no exception if I do the same 
import in sage -python.  But that is no help in terms of running lldb.  
However, perhaps if I knew how to set up the correct environment first I 
would be able to start the sage python in lldb and then actually be able to 
do the import.

- Marc


On Monday, January 17, 2022 at 3:18:05 PM UTC-6 matthia...@gmail.com wrote:

> Try "import sage.all" first.
>
> On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com wrote:
>
>> While many things work in the binary macOS app for Arm CPU, I discovered 
>> by accident that the following produces a segfault:
>>
>> sage: M = Manifold()
>>
>> In fact, even trying to import manifold from sage.manifolds segfaults.  
>> This does not happen on the Intel version of the app built from the same 
>> branch of the repository.
>>
>> I have not been able to run a debugger on sage at all.  Of course 
>> cysignals cannot produce a backtrace on macOS.  With lldb -p I get an error 
>> saying that lldb is not allowed to attach to the process and referring me 
>> to non-existent messages in system.log for explanations.  Running the 
>> debugserver directly produces:
>> error: failed to attach process 6619: unable to start the exception thread
>>
>> This occurs even if I run sage directly in the repo after the build 
>> finishes - it does not have anything to do with the app.  (And the debugger 
>> similarly refuses to attach to the process.)  I tried to run the debugger 
>> as root and I also tried adding debugger entitlements and resigning the 
>> app.  Neither make it possible for me to use lldb on sage itself.
>>
>> I am able to start the sage python3 in lldb.  If I knew how to import the 
>> Manifold class from python I might be able to get somewhere.  But if I run
>> >>> from sage.manifolds import manifold
>> I get a python exception whose traceback ends with:
>> File "sage/structure/category_object.pyx", line 60, in init 
>> sage.structure.category_object 
>> (build/cythonized/sage/structure/category_object.c:9914)
>> ImportError: cannot import name Category
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:
>>
>>> Hi Matthias,
>>>
>>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm 
>>> CPUs at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>>> There are two separate disk images.  You may recall that I do not use 
>>> Homebrew or Conda, but I did have to use an experimental binary release of 
>>> gfortran for M1 since I was not able to build the gfortran spkg.
>>>
>>> - Marc
>>>
>>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
>>> wrote:
>>>
>> Based on the runs on GH Actions, I have updated the summary of platform 
 support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources

 TL;DR: It's all good now on all platforms tested on GH Actions, 
 including Cygwin.
 But I would urge that 9.5 still merge the positively reviews tickets 
 marked "critical"/"blocker", such as 
 https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
 presence of pyenv).
 Also *note we have absolutely no automatic testing for the Apple 
 Silicon (M1) platform.* So it would be good if users/developers who 
 have access to this platform test the release candidate.



 On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:

> On Thursday, January 13, 2022 at 3:22:03 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
>>
>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
>> SageMath version to 9.5.rc1
>>
>
> Thanks for the new rc. Tests are running at 
> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, 
> macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 
> (Cygwin).
>
>
>
>
>
>  
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/2e287aba-ffb9-41bb-bcc3-9ef25348da99n%40googlegroups.com.

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

[Marc Culler]

(lldb) r
Process 6983 launched: 
'/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/bin/python3.9'
 
(arm64)
Python 3.9.9 (main, Jan 16 2022, 17:10:52) 
[Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sage.all
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/all.py",
 
line 131, in 
from sage.rings.all  import *
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/rings/all.py",
 
line 87, in 
from .qqbar import (AlgebraicRealField, AA,
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/rings/qqbar.py",
 
line 2810, in 
QQxy = QQ['x', 'y']
  File "sage/structure/parent.pyx", line 1276, in 
sage.structure.parent.Parent.__getitem__ 
(build/cythonized/sage/structure/parent.c:11409)
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/categories/rings.py",
 
line 1177, in __getitem__
return PolynomialRing(self, elts)
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/rings/polynomial/polynomial_ring_constructor.py",
 
line 647, in PolynomialRing
return _multi_variate(base_ring, names, **kwds)
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/site-packages/sage/rings/polynomial/polynomial_ring_constructor.py",
 
line 775, in _multi_variate
from sage.rings.polynomial.multi_polynomial_libsingular import 
MPolynomialRing_libsingular
  File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", line 1, in 
init sage.rings.polynomial.multi_polynomial_libsingular 
(build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:50026)
  File "sage/libs/singular/singular.pyx", line 1558, in init 
sage.libs.singular.singular 
(build/cythonized/sage/libs/singular/singular.cpp:15752)
  File "sage/libs/singular/singular.pyx", line 1525, in 
sage.libs.singular.singular.init_libsingular 
(build/cythonized/sage/libs/singular/singular.cpp:12870)
  File 
"/Users/culler/programs/Sage_macOS/Sage_framework/bigrepo/sage/venv/lib/python3.9/posixpath.py",
 
line 152, in dirname
p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType
>>> 


On Monday, January 17, 2022 at 3:18:05 PM UTC-6 matthia...@gmail.com wrote:

> Try "import sage.all" first.
>
> On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com wrote:
>
>> While many things work in the binary macOS app for Arm CPU, I discovered 
>> by accident that the following produces a segfault:
>>
>> sage: M = Manifold()
>>
>> In fact, even trying to import manifold from sage.manifolds segfaults.  
>> This does not happen on the Intel version of the app built from the same 
>> branch of the repository.
>>
>> I have not been able to run a debugger on sage at all.  Of course 
>> cysignals cannot produce a backtrace on macOS.  With lldb -p I get an error 
>> saying that lldb is not allowed to attach to the process and referring me 
>> to non-existent messages in system.log for explanations.  Running the 
>> debugserver directly produces:
>> error: failed to attach process 6619: unable to start the exception thread
>>
>> This occurs even if I run sage directly in the repo after the build 
>> finishes - it does not have anything to do with the app.  (And the debugger 
>> similarly refuses to attach to the process.)  I tried to run the debugger 
>> as root and I also tried adding debugger entitlements and resigning the 
>> app.  Neither make it possible for me to use lldb on sage itself.
>>
>> I am able to start the sage python3 in lldb.  If I knew how to import the 
>> Manifold class from python I might be able to get somewhere.  But if I run
>> >>> from sage.manifolds import manifold
>> I get a python exception whose traceback ends with:
>> File "sage/structure/category_object.pyx", line 60, in init 
>> sage.structure.category_object 
>> (build/cythonized/sage/structure/category_object.c:9914)
>> ImportError: cannot import name Category
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:
>>
>>> Hi Matthias,
>>>
>>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm 
>>> CPUs at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>>> There are two separate disk images.  You may recall that I do not use 
>>> Homebrew or Conda, but I did have to use an experimental binary release of 
>>> gfortran for M1 since I was not able to build the gfortran spkg.
>>>
>>> - Marc
>>>
>>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
>>> wrote:
>>>
>> Based on the runs on GH Actions, I have updated the summary of platform 
 support in 

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

[Marc Culler]

I was able to get a bit further in python by running:

>>> from sage.structure import *

Then when I tried

>>> from sage.manifolds import manifold

I get an exception whose traceback ends with

AttributeError: module 'sage.structure' has no attribute 'sage_object'

This seems strange, since there is no exception when I run

>>> from sage.structure import sage_object
>>> dir(sage_object)
['LazyImport', 'SageObject', '__all__', '__builtins__', '__doc__', 
'__file__', '__loader__', '__name__', '__package__', '__spec__', 
'_base_dumps', '_base_save', '_interface_init_with_interface', 'dumps', 
'load', 'loads', 'make_None', 'register_unpickle_override', 'save', 
'unpickle_all', 'unpickle_global', 'unpickle_override']

But it seems consistent with:

>>> dir(sage.structure)
['__builtins__', '__cached__', '__doc__', '__file__', '__loader__', 
'__name__', '__package__', '__path__', '__spec__', 'category_object', 
'coerce', 'coerce_actions', 'coerce_dict', 'coerce_exceptions', 
'coerce_maps', 'dynamic_class', 'element', 'parent', 'richcmp', 'sage', 
'unique_representation']

I suppose there is some opaque monkey-patching going on.  So, I am not sure 
where to go next ...

- Marc

On Saturday, January 15, 2022 at 4:49:42 PM UTC-6 matthia...@gmail.com 
wrote:

> Hi Marc,
> Awesome! I've added it to 
> https://wiki.sagemath.org/ReleaseTours/sage-9.5#Binaries
> Matthias
>
> On Saturday, January 15, 2022 at 2:30:08 PM UTC-8 marc@gmail.com 
> wrote:
>
>> Hi Matthias,
>>
>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
>> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>> There are two separate disk images.  You may recall that I do not use 
>> Homebrew or Conda, but I did have to use an experimental binary release of 
>> gfortran for M1 since I was not able to build the gfortran spkg.
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
>> wrote:
>>
>>> Based on the runs on GH Actions, I have updated the summary of platform 
>>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>>
>>> TL;DR: It's all good now on all platforms tested on GH Actions, 
>>> including Cygwin.
>>> But I would urge that 9.5 still merge the positively reviews tickets 
>>> marked "critical"/"blocker", such as 
>>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>>> presence of pyenv).
>>> Also *note we have absolutely no automatic testing for the Apple 
>>> Silicon (M1) platform.* So it would be good if users/developers who 
>>> have access to this platform test the release candidate.
>>>
>>>
>>>
>>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>>
 On Thursday, January 13, 2022 at 3:22:03 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
>
> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
> SageMath version to 9.5.rc1
>

 Thanks for the new rc. Tests are running at 
 https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, 
 macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 
 (Cygwin).





  

>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e2321f27-8360-43da-a2f3-9cff2826147fn%40googlegroups.com.

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

[Matthias Köppe]

Try "import sage.all" first.

On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc@gmail.com wrote:

> While many things work in the binary macOS app for Arm CPU, I discovered 
> by accident that the following produces a segfault:
>
> sage: M = Manifold()
>
> In fact, even trying to import manifold from sage.manifolds segfaults.  
> This does not happen on the Intel version of the app built from the same 
> branch of the repository.
>
> I have not been able to run a debugger on sage at all.  Of course 
> cysignals cannot produce a backtrace on macOS.  With lldb -p I get an error 
> saying that lldb is not allowed to attach to the process and referring me 
> to non-existent messages in system.log for explanations.  Running the 
> debugserver directly produces:
> error: failed to attach process 6619: unable to start the exception thread
>
> This occurs even if I run sage directly in the repo after the build 
> finishes - it does not have anything to do with the app.  (And the debugger 
> similarly refuses to attach to the process.)  I tried to run the debugger 
> as root and I also tried adding debugger entitlements and resigning the 
> app.  Neither make it possible for me to use lldb on sage itself.
>
> I am able to start the sage python3 in lldb.  If I knew how to import the 
> Manifold class from python I might be able to get somewhere.  But if I run
> >>> from sage.manifolds import manifold
> I get a python exception whose traceback ends with:
> File "sage/structure/category_object.pyx", line 60, in init 
> sage.structure.category_object 
> (build/cythonized/sage/structure/category_object.c:9914)
> ImportError: cannot import name Category
>
> - Marc
>
> On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:
>
>> Hi Matthias,
>>
>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
>> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>> There are two separate disk images.  You may recall that I do not use 
>> Homebrew or Conda, but I did have to use an experimental binary release of 
>> gfortran for M1 since I was not able to build the gfortran spkg.
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
>> wrote:
>>
> Based on the runs on GH Actions, I have updated the summary of platform 
>>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>>
>>> TL;DR: It's all good now on all platforms tested on GH Actions, 
>>> including Cygwin.
>>> But I would urge that 9.5 still merge the positively reviews tickets 
>>> marked "critical"/"blocker", such as 
>>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>>> presence of pyenv).
>>> Also *note we have absolutely no automatic testing for the Apple 
>>> Silicon (M1) platform.* So it would be good if users/developers who 
>>> have access to this platform test the release candidate.
>>>
>>>
>>>
>>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>>
 On Thursday, January 13, 2022 at 3:22:03 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
>
> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
> SageMath version to 9.5.rc1
>

 Thanks for the new rc. Tests are running at 
 https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, 
 macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 
 (Cygwin).





  

>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a9e30c7a-b245-49b4-a472-8fd4b0431e9fn%40googlegroups.com.

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

[Marc Culler]

While many things work in the binary macOS app for Arm CPU, I discovered by 
accident that the following produces a segfault:

sage: M = Manifold()

In fact, even trying to import manifold from sage.manifolds segfaults.  
This does not happen on the Intel version of the app built from the same 
branch of the repository.

I have not been able to run a debugger on sage at all.  Of course cysignals 
cannot produce a backtrace on macOS.  With lldb -p I get an error saying 
that lldb is not allowed to attach to the process and referring me to 
non-existent messages in system.log for explanations.  Running the 
debugserver directly produces:
error: failed to attach process 6619: unable to start the exception thread

This occurs even if I run sage directly in the repo after the build 
finishes - it does not have anything to do with the app.  (And the debugger 
similarly refuses to attach to the process.)  I tried to run the debugger 
as root and I also tried adding debugger entitlements and resigning the 
app.  Neither make it possible for me to use lldb on sage itself.

I am able to start the sage python3 in lldb.  If I knew how to import the 
Manifold class from python I might be able to get somewhere.  But if I run
>>> from sage.manifolds import manifold
I get a python exception whose traceback ends with:
File "sage/structure/category_object.pyx", line 60, in init 
sage.structure.category_object 
(build/cythonized/sage/structure/category_object.c:9914)
ImportError: cannot import name Category

- Marc

On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote:

> Hi Matthias,
>
> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
> There are two separate disk images.  You may recall that I do not use 
> Homebrew or Conda, but I did have to use an experimental binary release of 
> gfortran for M1 since I was not able to build the gfortran spkg.
>
> - Marc
>
> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
> wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of platform 
>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions, including 
>> Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets 
>> marked "critical"/"blocker", such as 
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple Silicon 
>> (M1) platform.* So it would be good if users/developers who have access 
>> to this platform test the release candidate.
>>
>>
>>
>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>
>>> On Thursday, January 13, 2022 at 3:22:03 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

 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
 SageMath version to 9.5.rc1

>>>
>>> Thanks for the new rc. Tests are running at 
>>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS) 
>>> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>>>
>>>
>>>
>>>
>>>
>>>  
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/80693d55-6492-40c7-806a-8630a3b5d3bbn%40googlegroups.com.

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

[Matthias Köppe]

Regarding the iml build failure, could you run "otool -lL 
/usr/local/opt/openblas/lib/libopenblas.0.dylib " please


On Sunday, January 16, 2022 at 6:46:59 PM UTC-8 list...@gmail.com wrote:

>
> Yes, of course.
>
> I have restarted the whole process again (modifying and sourcing  
> .homebrew-build-env), and it does not go further than iml:
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 17 03:43
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
> On Mon, 17 Jan 2022 at 03:24, Matthias Köppe  wrote:
>
>> Did you use ". .homebrew-build-env" before the latest build?
>>
>> On Sunday, January 16, 2022 at 5:30:12 PM UTC-8 list...@gmail.com wrote:
>>
>>>
>>> Here is what I have done.
>>>
>>> $ brew uninstall openblas
>>>
>>> Error: Refusing to uninstall /opt/homebrew/Cellar/openblas/0.3.19
>>>
>>> because it is required by arpack, cbc, cgl, clp, coinutils, igraph, osi, 
>>> r and suite-sparse, which are currently installed.
>>>
>>> You can override this and force removal with:
>>>
>>>   brew uninstall --ignore-dependencies openblas
>>>
>>> $ brew uninstall --ignore-dependencies openblas
>>>
>>> Uninstalling /opt/homebrew/Cellar/openblas/0.3.19... (23 files, 51.9MB)
>>>
>>> $ brew install openblas
>>>
>>> ==> *Auto-updated Homebrew!*
>>>
>>> Updated 1 tap (homebrew/core).
>>>
>>> ==> *Updated Formulae*
>>>
>>> Updated 10 formulae.
>>>
>>> Running `brew update --preinstall`...
>>>
>>>
>>> ==> *Downloading 
>>> https://ghcr.io/v2/homebrew/core/openblas/manifests/0.3.19 
>>> *
>>>
>>> Already downloaded: 
>>> /Users/gms/Library/Caches/Homebrew/downloads/b47e3d834a9c52d0772b21372a675e3496a8480baa2f3e9b72d60def08682c3f--openblas-0.3.19.bottle_manifest.json
>>>
>>> ==> *Downloading 
>>> https://ghcr.io/v2/homebrew/core/openblas/blobs/sha256:33e6385102e69ddd716d8eb818861e2e2e2c08de20e06d189ffd69115131ed03
>>>  
>>> *
>>>
>>> Already downloaded: 
>>> /Users/gms/Library/Caches/Homebrew/downloads/82003eb6c8dd0091f8465e8203b39d67e81d7db4c9e4d790e71f6b2e8445ab3f--openblas--0.3.19.arm64_big_sur.bottle.tar.gz
>>>
>>> ==> *Pouring openblas--0.3.19.arm64_big_sur.bottle.tar.gz*
>>>
>>> ==> *Caveats*
>>>
>>> openblas is keg-only, which means it was not symlinked into 
>>> /opt/homebrew,
>>>
>>> because macOS provides BLAS in Accelerate.framework.
>>>
>>>
>>> For compilers to find openblas you may need to set:
>>>
>>>   export LDFLAGS="-L/opt/homebrew/opt/openblas/lib"
>>>
>>>   export CPPFLAGS="-I/opt/homebrew/opt/openblas/include"
>>>
>>>
>>> For pkg-config to find openblas you may need to set:
>>>
>>>   export PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig"
>>>
>>>
>>> ==> *Summary*
>>>
>>>   /opt/homebrew/Cellar/openblas/0.3.19: 23 files, 51.9MB
>>>
>>> ==> *Running `brew cleanup openblas`...*
>>>
>>> Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
>>>
>>> Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
>>>
>>> $ 
>>>
>>> then the modification for .homebrew-build-env, followed by make -k.
>>>
>>> And now the only remaining problem is openblas:
>>>
>>> * package: openblas-0.3.18
>>>
>>>   last build time: Jan 17 02:24
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>>>
>>> Logs attached (sorry for the wrong log before).  The one for openblas is 
>>> zipped as it is too large.
>>>
>>> On Mon, 17 Jan 2022 at 00:34, Matthias Köppe  
>>> wrote:
>>>
 Also worth checking whether "brew install openblas" installs something 
 new
 (see messages at the end of the configure run)

 On Sunday, January 16, 2022 at 2:34:48 PM UTC-8 Matthias Köppe wrote:

> There is no error in the zn_poly log file; but could you post the 
> openblas log file please?
>
> On Sunday, January 16, 2022 at 2:17:38 PM UTC-8 Matthias Köppe wrote:
>
>> Thanks for testing and posting the logs. I'll dissect the logs at 
>> https://trac.sagemath.org/ticket/30592
>>
>>
>> On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com 
>> wrote:
>>
>>>
>>> I started afresh (delete sage-9.5.rc1, untar, etc.)
>>>
>>> make -k gives
>>>
>>> The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make tachyon'):
>>>
>>>
>>> * package: primecountpy-0.1.0
>>>
>>>   last build time: Jan 16 21:55
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>>>
>>>
>>> * package: libhomfly-1.02r6
>>>
>>>   last build time: Jan 

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

[Matthias Köppe]

The latest config.log now shows "will use system package and not install 
SPKG openblas", so there's progress.

I'll take the new version of the iml log to 
https://trac.sagemath.org/ticket/30592
On Sunday, January 16, 2022 at 6:46:59 PM UTC-8 list...@gmail.com wrote:

>
> Yes, of course.
>
> I have restarted the whole process again (modifying and sourcing  
> .homebrew-build-env), and it does not go further than iml:
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 17 03:43
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
> On Mon, 17 Jan 2022 at 03:24, Matthias Köppe  wrote:
>
>> Did you use ". .homebrew-build-env" before the latest build?
>>
>> On Sunday, January 16, 2022 at 5:30:12 PM UTC-8 list...@gmail.com wrote:
>>
>>>
>>> Here is what I have done.
>>>
>>> $ brew uninstall openblas
>>>
>>> Error: Refusing to uninstall /opt/homebrew/Cellar/openblas/0.3.19
>>>
>>> because it is required by arpack, cbc, cgl, clp, coinutils, igraph, osi, 
>>> r and suite-sparse, which are currently installed.
>>>
>>> You can override this and force removal with:
>>>
>>>   brew uninstall --ignore-dependencies openblas
>>>
>>> $ brew uninstall --ignore-dependencies openblas
>>>
>>> Uninstalling /opt/homebrew/Cellar/openblas/0.3.19... (23 files, 51.9MB)
>>>
>>> $ brew install openblas
>>>
>>> ==> *Auto-updated Homebrew!*
>>>
>>> Updated 1 tap (homebrew/core).
>>>
>>> ==> *Updated Formulae*
>>>
>>> Updated 10 formulae.
>>>
>>> Running `brew update --preinstall`...
>>>
>>>
>>> ==> *Downloading 
>>> https://ghcr.io/v2/homebrew/core/openblas/manifests/0.3.19 
>>> *
>>>
>>> Already downloaded: 
>>> /Users/gms/Library/Caches/Homebrew/downloads/b47e3d834a9c52d0772b21372a675e3496a8480baa2f3e9b72d60def08682c3f--openblas-0.3.19.bottle_manifest.json
>>>
>>> ==> *Downloading 
>>> https://ghcr.io/v2/homebrew/core/openblas/blobs/sha256:33e6385102e69ddd716d8eb818861e2e2e2c08de20e06d189ffd69115131ed03
>>>  
>>> *
>>>
>>> Already downloaded: 
>>> /Users/gms/Library/Caches/Homebrew/downloads/82003eb6c8dd0091f8465e8203b39d67e81d7db4c9e4d790e71f6b2e8445ab3f--openblas--0.3.19.arm64_big_sur.bottle.tar.gz
>>>
>>> ==> *Pouring openblas--0.3.19.arm64_big_sur.bottle.tar.gz*
>>>
>>> ==> *Caveats*
>>>
>>> openblas is keg-only, which means it was not symlinked into 
>>> /opt/homebrew,
>>>
>>> because macOS provides BLAS in Accelerate.framework.
>>>
>>>
>>> For compilers to find openblas you may need to set:
>>>
>>>   export LDFLAGS="-L/opt/homebrew/opt/openblas/lib"
>>>
>>>   export CPPFLAGS="-I/opt/homebrew/opt/openblas/include"
>>>
>>>
>>> For pkg-config to find openblas you may need to set:
>>>
>>>   export PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig"
>>>
>>>
>>> ==> *Summary*
>>>
>>>   /opt/homebrew/Cellar/openblas/0.3.19: 23 files, 51.9MB
>>>
>>> ==> *Running `brew cleanup openblas`...*
>>>
>>> Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
>>>
>>> Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
>>>
>>> $ 
>>>
>>> then the modification for .homebrew-build-env, followed by make -k.
>>>
>>> And now the only remaining problem is openblas:
>>>
>>> * package: openblas-0.3.18
>>>
>>>   last build time: Jan 17 02:24
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>>>
>>> Logs attached (sorry for the wrong log before).  The one for openblas is 
>>> zipped as it is too large.
>>>
>>> On Mon, 17 Jan 2022 at 00:34, Matthias Köppe  
>>> wrote:
>>>
 Also worth checking whether "brew install openblas" installs something 
 new
 (see messages at the end of the configure run)

 On Sunday, January 16, 2022 at 2:34:48 PM UTC-8 Matthias Köppe wrote:

> There is no error in the zn_poly log file; but could you post the 
> openblas log file please?
>
> On Sunday, January 16, 2022 at 2:17:38 PM UTC-8 Matthias Köppe wrote:
>
>> Thanks for testing and posting the logs. I'll dissect the logs at 
>> https://trac.sagemath.org/ticket/30592
>>
>>
>> On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com 
>> wrote:
>>
>>>
>>> I started afresh (delete sage-9.5.rc1, untar, etc.)
>>>
>>> make -k gives
>>>
>>> The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make tachyon'):
>>>
>>>
>>> * package: primecountpy-0.1.0
>>>
>>>   last build time: Jan 16 21:55
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>>>
>>>

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

[Matthias Köppe]

Did you use ". .homebrew-build-env" before the latest build?

On Sunday, January 16, 2022 at 5:30:12 PM UTC-8 list...@gmail.com wrote:

>
> Here is what I have done.
>
> $ brew uninstall openblas
>
> Error: Refusing to uninstall /opt/homebrew/Cellar/openblas/0.3.19
>
> because it is required by arpack, cbc, cgl, clp, coinutils, igraph, osi, r 
> and suite-sparse, which are currently installed.
>
> You can override this and force removal with:
>
>   brew uninstall --ignore-dependencies openblas
>
> $ brew uninstall --ignore-dependencies openblas
>
> Uninstalling /opt/homebrew/Cellar/openblas/0.3.19... (23 files, 51.9MB)
>
> $ brew install openblas
>
> ==> *Auto-updated Homebrew!*
>
> Updated 1 tap (homebrew/core).
>
> ==> *Updated Formulae*
>
> Updated 10 formulae.
>
> Running `brew update --preinstall`...
>
>
> ==> *Downloading 
> https://ghcr.io/v2/homebrew/core/openblas/manifests/0.3.19 
> *
>
> Already downloaded: 
> /Users/gms/Library/Caches/Homebrew/downloads/b47e3d834a9c52d0772b21372a675e3496a8480baa2f3e9b72d60def08682c3f--openblas-0.3.19.bottle_manifest.json
>
> ==> *Downloading 
> https://ghcr.io/v2/homebrew/core/openblas/blobs/sha256:33e6385102e69ddd716d8eb818861e2e2e2c08de20e06d189ffd69115131ed03
>  
> *
>
> Already downloaded: 
> /Users/gms/Library/Caches/Homebrew/downloads/82003eb6c8dd0091f8465e8203b39d67e81d7db4c9e4d790e71f6b2e8445ab3f--openblas--0.3.19.arm64_big_sur.bottle.tar.gz
>
> ==> *Pouring openblas--0.3.19.arm64_big_sur.bottle.tar.gz*
>
> ==> *Caveats*
>
> openblas is keg-only, which means it was not symlinked into /opt/homebrew,
>
> because macOS provides BLAS in Accelerate.framework.
>
>
> For compilers to find openblas you may need to set:
>
>   export LDFLAGS="-L/opt/homebrew/opt/openblas/lib"
>
>   export CPPFLAGS="-I/opt/homebrew/opt/openblas/include"
>
>
> For pkg-config to find openblas you may need to set:
>
>   export PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig"
>
>
> ==> *Summary*
>
>   /opt/homebrew/Cellar/openblas/0.3.19: 23 files, 51.9MB
>
> ==> *Running `brew cleanup openblas`...*
>
> Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
>
> Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
>
> $ 
>
> then the modification for .homebrew-build-env, followed by make -k.
>
> And now the only remaining problem is openblas:
>
> * package: openblas-0.3.18
>
>   last build time: Jan 17 02:24
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>
> Logs attached (sorry for the wrong log before).  The one for openblas is 
> zipped as it is too large.
>
> On Mon, 17 Jan 2022 at 00:34, Matthias Köppe  wrote:
>
>> Also worth checking whether "brew install openblas" installs something new
>> (see messages at the end of the configure run)
>>
>> On Sunday, January 16, 2022 at 2:34:48 PM UTC-8 Matthias Köppe wrote:
>>
>>> There is no error in the zn_poly log file; but could you post the 
>>> openblas log file please?
>>>
>>> On Sunday, January 16, 2022 at 2:17:38 PM UTC-8 Matthias Köppe wrote:
>>>
 Thanks for testing and posting the logs. I'll dissect the logs at 
 https://trac.sagemath.org/ticket/30592


 On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com 
 wrote:

>
> I started afresh (delete sage-9.5.rc1, untar, etc.)
>
> make -k gives
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make tachyon'):
>
>
> * package: primecountpy-0.1.0
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>
>
> * package: libhomfly-1.02r6
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/libhomfly-1.02r6.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/libhomfly-1.02r6
>
>
> * package: m4ri-20200115
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/m4ri-20200115.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/m4ri-20200115
>
>
> * package: openblas-0.3.18
>
>   last build time: Jan 16 21:58
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>
>
> * package: tachyon-0.98.9.p7
>
>   last build time: Jan 16 21:59
>
>   log file:
> 

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

[Matthias Köppe]

Also worth checking whether "brew install openblas" installs something new
(see messages at the end of the configure run)

On Sunday, January 16, 2022 at 2:34:48 PM UTC-8 Matthias Köppe wrote:

> There is no error in the zn_poly log file; but could you post the openblas 
> log file please?
>
> On Sunday, January 16, 2022 at 2:17:38 PM UTC-8 Matthias Köppe wrote:
>
>> Thanks for testing and posting the logs. I'll dissect the logs at 
>> https://trac.sagemath.org/ticket/30592
>>
>>
>> On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com wrote:
>>
>>>
>>> I started afresh (delete sage-9.5.rc1, untar, etc.)
>>>
>>> make -k gives
>>>
>>> The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make tachyon'):
>>>
>>>
>>> * package: primecountpy-0.1.0
>>>
>>>   last build time: Jan 16 21:55
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>>>
>>>
>>> * package: libhomfly-1.02r6
>>>
>>>   last build time: Jan 16 21:55
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/libhomfly-1.02r6.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/libhomfly-1.02r6
>>>
>>>
>>> * package: m4ri-20200115
>>>
>>>   last build time: Jan 16 21:55
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/m4ri-20200115.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/m4ri-20200115
>>>
>>>
>>> * package: openblas-0.3.18
>>>
>>>   last build time: Jan 16 21:58
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>>>
>>>
>>> * package: tachyon-0.98.9.p7
>>>
>>>   last build time: Jan 16 21:59
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>>>
>>> Logs attached.
>>>
>>> On Sun, 16 Jan 2022 at 18:25, G. M.-S.  wrote:
>>>

 Here it is. Before:

 $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*

 -rw-r--r--  1 gms  staff  13933 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h

 -rw-r--r--  1 gms  staff  14714 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h

 -rw-r--r--  1 gms  staff   4726 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h

 -rw-r--r--  1 gms  staff   4947 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h

 -rw-r--r--  1 gms  staff  10953 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h

 -rw-r--r--  1 gms  staff  11307 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h

 -rw-r--r--  1 gms  staff   1373 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h

 -rw-r--r--  1 gms  staff609 Jan 16 11:08 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h

 $ 
 and after make cddlib-clean cddlib:

 $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*

 -rw-r--r--  1 gms  staff  13933 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h

 -rw-r--r--  1 gms  staff  14714 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h

 -rw-r--r--  1 gms  staff   4726 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h

 -rw-r--r--  1 gms  staff   4947 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h

 -rw-r--r--  1 gms  staff  10953 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h

 -rw-r--r--  1 gms  staff  11307 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h

 -rw-r--r--  1 gms  staff   1373 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h

 -rw-r--r--  1 gms  staff609 Jan 16 18:21 
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h

 $ 

 Logs attached.

 Trying to make again, will report.

 On Sun, 16 Jan 2022 at 18:12, Matthias Köppe  
 wrote:

> From singularlog:
>
> In file included from bbfan.cc:17:
> In file included from ./gfan.h:18:
> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h:26:10: fatal 
> error: 'cdd_f.h' file not found
> #include "cdd_f.h"
>  ^
> 1 error generated.
> make[10]: *** [gfanlib_la-bbfan.lo] Error 1
>
> This is very strange. Could you (1) check what's in 
> local/include/cddlib/ and (2) reinstall cddlib using "make cddlib-clean 
> cddlib"?
>
>
> On Sunday, 

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

[Matthias Köppe]

I have a possible fix for these at https://trac.sagemath.org/ticket/33191; 
to test without git, just make the changes shown 
in 
https://git.sagemath.org/sage.git/diff?id2=f9b2db94f675ff16963ccdefba4f1a3393b3fe0d=aee855a78b42ab4b726995a9e22f23e3bec08b8b
 
to the file .homebrew-build-env and then source this file again

On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com wrote:

>
> I started afresh (delete sage-9.5.rc1, untar, etc.)
>
> make -k gives
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make tachyon'):
>
>
> * package: primecountpy-0.1.0
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>
>
> * package: libhomfly-1.02r6
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/libhomfly-1.02r6.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/libhomfly-1.02r6
>
>
> * package: m4ri-20200115
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/m4ri-20200115.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/m4ri-20200115
>
>
> * package: openblas-0.3.18
>
>   last build time: Jan 16 21:58
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>
>
> * package: tachyon-0.98.9.p7
>
>   last build time: Jan 16 21:59
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>
> Logs attached.
>
> On Sun, 16 Jan 2022 at 18:25, G. M.-S.  wrote:
>
>>
>> Here it is. Before:
>>
>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>
>> -rw-r--r--  1 gms  staff  13933 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>
>> -rw-r--r--  1 gms  staff  14714 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>
>> -rw-r--r--  1 gms  staff   4726 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>
>> -rw-r--r--  1 gms  staff   4947 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>
>> -rw-r--r--  1 gms  staff  10953 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>
>> -rw-r--r--  1 gms  staff  11307 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>
>> -rw-r--r--  1 gms  staff   1373 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>
>> -rw-r--r--  1 gms  staff609 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>
>> $ 
>> and after make cddlib-clean cddlib:
>>
>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>
>> -rw-r--r--  1 gms  staff  13933 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>
>> -rw-r--r--  1 gms  staff  14714 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>
>> -rw-r--r--  1 gms  staff   4726 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>
>> -rw-r--r--  1 gms  staff   4947 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>
>> -rw-r--r--  1 gms  staff  10953 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>
>> -rw-r--r--  1 gms  staff  11307 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>
>> -rw-r--r--  1 gms  staff   1373 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>
>> -rw-r--r--  1 gms  staff609 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>
>> $ 
>>
>> Logs attached.
>>
>> Trying to make again, will report.
>>
>> On Sun, 16 Jan 2022 at 18:12, Matthias Köppe  
>> wrote:
>>
>>> From singularlog:
>>>
>>> In file included from bbfan.cc:17:
>>> In file included from ./gfan.h:18:
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h:26:10: fatal 
>>> error: 'cdd_f.h' file not found
>>> #include "cdd_f.h"
>>>  ^
>>> 1 error generated.
>>> make[10]: *** [gfanlib_la-bbfan.lo] Error 1
>>>
>>> This is very strange. Could you (1) check what's in 
>>> local/include/cddlib/ and (2) reinstall cddlib using "make cddlib-clean 
>>> cddlib"?
>>>
>>>
>>> On Sunday, January 16, 2022 at 2:17:58 AM UTC-8 list...@gmail.com wrote:
>>>

 There was no /usr/local/opt.
 I eliminated all references to /usr/local/opt in .bash_profile.
 Uninstalled homebrew and reinstalled it.

 I get

 make[2]: *** [all-start] Error 2


 real 4m27.295s

 user 12m14.754s

 sys 3m20.702s

 ***

 Error building Sage.

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

[Matthias Köppe]

There is no error in the zn_poly log file; but could you post the openblas 
log file please?

On Sunday, January 16, 2022 at 2:17:38 PM UTC-8 Matthias Köppe wrote:

> Thanks for testing and posting the logs. I'll dissect the logs at 
> https://trac.sagemath.org/ticket/30592
>
>
> On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com wrote:
>
>>
>> I started afresh (delete sage-9.5.rc1, untar, etc.)
>>
>> make -k gives
>>
>> The following package(s) may have failed to build (not necessarily
>>
>> during this run of 'make tachyon'):
>>
>>
>> * package: primecountpy-0.1.0
>>
>>   last build time: Jan 16 21:55
>>
>>   log file:
>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>>
>>
>> * package: libhomfly-1.02r6
>>
>>   last build time: Jan 16 21:55
>>
>>   log file:
>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/libhomfly-1.02r6.log
>>
>>   build directory: 
>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/libhomfly-1.02r6
>>
>>
>> * package: m4ri-20200115
>>
>>   last build time: Jan 16 21:55
>>
>>   log file:
>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/m4ri-20200115.log
>>
>>   build directory: 
>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/m4ri-20200115
>>
>>
>> * package: openblas-0.3.18
>>
>>   last build time: Jan 16 21:58
>>
>>   log file:
>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>>
>>   build directory: 
>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>>
>>
>> * package: tachyon-0.98.9.p7
>>
>>   last build time: Jan 16 21:59
>>
>>   log file:
>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>>
>>   build directory: 
>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>>
>> Logs attached.
>>
>> On Sun, 16 Jan 2022 at 18:25, G. M.-S.  wrote:
>>
>>>
>>> Here it is. Before:
>>>
>>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>>
>>> -rw-r--r--  1 gms  staff  13933 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>>
>>> -rw-r--r--  1 gms  staff  14714 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>>
>>> -rw-r--r--  1 gms  staff   4726 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>>
>>> -rw-r--r--  1 gms  staff   4947 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>>
>>> -rw-r--r--  1 gms  staff  10953 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>>
>>> -rw-r--r--  1 gms  staff  11307 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>>
>>> -rw-r--r--  1 gms  staff   1373 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>>
>>> -rw-r--r--  1 gms  staff609 Jan 16 11:08 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>>
>>> $ 
>>> and after make cddlib-clean cddlib:
>>>
>>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>>
>>> -rw-r--r--  1 gms  staff  13933 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>>
>>> -rw-r--r--  1 gms  staff  14714 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>>
>>> -rw-r--r--  1 gms  staff   4726 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>>
>>> -rw-r--r--  1 gms  staff   4947 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>>
>>> -rw-r--r--  1 gms  staff  10953 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>>
>>> -rw-r--r--  1 gms  staff  11307 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>>
>>> -rw-r--r--  1 gms  staff   1373 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>>
>>> -rw-r--r--  1 gms  staff609 Jan 16 18:21 
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>>
>>> $ 
>>>
>>> Logs attached.
>>>
>>> Trying to make again, will report.
>>>
>>> On Sun, 16 Jan 2022 at 18:12, Matthias Köppe  
>>> wrote:
>>>
 From singularlog:

 In file included from bbfan.cc:17:
 In file included from ./gfan.h:18:
 /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h:26:10: fatal 
 error: 'cdd_f.h' file not found
 #include "cdd_f.h"
  ^
 1 error generated.
 make[10]: *** [gfanlib_la-bbfan.lo] Error 1

 This is very strange. Could you (1) check what's in 
 local/include/cddlib/ and (2) reinstall cddlib using "make cddlib-clean 
 cddlib"?


 On Sunday, January 16, 2022 at 2:17:58 AM UTC-8 list...@gmail.com 
 wrote:

>
> There was no /usr/local/opt.
> I eliminated all references to /usr/local/opt in .bash_profile.
> Uninstalled homebrew and reinstalled it.
>
> I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 4m27.295s
>
> user 12m14.754s

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

[Matthias Köppe]

Thanks for testing and posting the logs. I'll dissect the logs 
at https://trac.sagemath.org/ticket/30592


On Sunday, January 16, 2022 at 1:06:58 PM UTC-8 list...@gmail.com wrote:

>
> I started afresh (delete sage-9.5.rc1, untar, etc.)
>
> make -k gives
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make tachyon'):
>
>
> * package: primecountpy-0.1.0
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/primecountpy-0.1.0.log
>
>
> * package: libhomfly-1.02r6
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/libhomfly-1.02r6.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/libhomfly-1.02r6
>
>
> * package: m4ri-20200115
>
>   last build time: Jan 16 21:55
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/m4ri-20200115.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/m4ri-20200115
>
>
> * package: openblas-0.3.18
>
>   last build time: Jan 16 21:58
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/openblas-0.3.18.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/openblas-0.3.18
>
>
> * package: tachyon-0.98.9.p7
>
>   last build time: Jan 16 21:59
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>
> Logs attached.
>
> On Sun, 16 Jan 2022 at 18:25, G. M.-S.  wrote:
>
>>
>> Here it is. Before:
>>
>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>
>> -rw-r--r--  1 gms  staff  13933 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>
>> -rw-r--r--  1 gms  staff  14714 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>
>> -rw-r--r--  1 gms  staff   4726 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>
>> -rw-r--r--  1 gms  staff   4947 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>
>> -rw-r--r--  1 gms  staff  10953 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>
>> -rw-r--r--  1 gms  staff  11307 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>
>> -rw-r--r--  1 gms  staff   1373 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>
>> -rw-r--r--  1 gms  staff609 Jan 16 11:08 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>
>> $ 
>> and after make cddlib-clean cddlib:
>>
>> $ ls -al ~/sage/sage-9.5.rc1/local/include/cddlib/*
>>
>> -rw-r--r--  1 gms  staff  13933 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h
>>
>> -rw-r--r--  1 gms  staff  14714 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd_f.h
>>
>> -rw-r--r--  1 gms  staff   4726 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp.h
>>
>> -rw-r--r--  1 gms  staff   4947 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddmp_f.h
>>
>> -rw-r--r--  1 gms  staff  10953 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes.h
>>
>> -rw-r--r--  1 gms  staff  11307 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cddtypes_f.h
>>
>> -rw-r--r--  1 gms  staff   1373 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/setoper.h
>>
>> -rw-r--r--  1 gms  staff609 Jan 16 18:21 
>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/splitmix64.h
>>
>> $ 
>>
>> Logs attached.
>>
>> Trying to make again, will report.
>>
>> On Sun, 16 Jan 2022 at 18:12, Matthias Köppe  
>> wrote:
>>
>>> From singularlog:
>>>
>>> In file included from bbfan.cc:17:
>>> In file included from ./gfan.h:18:
>>> /Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h:26:10: fatal 
>>> error: 'cdd_f.h' file not found
>>> #include "cdd_f.h"
>>>  ^
>>> 1 error generated.
>>> make[10]: *** [gfanlib_la-bbfan.lo] Error 1
>>>
>>> This is very strange. Could you (1) check what's in 
>>> local/include/cddlib/ and (2) reinstall cddlib using "make cddlib-clean 
>>> cddlib"?
>>>
>>>
>>> On Sunday, January 16, 2022 at 2:17:58 AM UTC-8 list...@gmail.com wrote:
>>>

 There was no /usr/local/opt.
 I eliminated all references to /usr/local/opt in .bash_profile.
 Uninstalled homebrew and reinstalled it.

 I get

 make[2]: *** [all-start] Error 2


 real 4m27.295s

 user 12m14.754s

 sys 3m20.702s

 ***

 Error building Sage.


 The following package(s) may have failed to build (not necessarily

 during this run of 'make all-start'):


 * package: iml-1.0.4p1.p2

   last build time: Jan 16 

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

['axio...@yahoo.de' via sage-release]

The findstat fixes (all trivial) are ready at 
https://trac.sagemath.org/ticket/33190.

On Saturday, 15 January 2022 at 08:09:30 UTC+1 Samuel Lelievre wrote:

> 2022-01-14 21:49 UTC, Sébastien Labbé:
> >
> > The failures with the following files are new and are copied below:
> >
> > SEED=115792415560373440200802359516411195501
> > alias sagetest="./sage -t --long --random-seed=$SEED"
> > sagetest src/sage/databases/findstat.py # 12 doctests failed
> > sagetest src/sage/databases/oeis.py # 1 doctest failed
> > sagetest src/sage/interfaces/mathematica.py # 1 doctest failed
>
> These might be a fallout of #32938, merged in Sage 9.5.rc0.
>
> - Sage Trac ticket #32938
> deactivation of the u-prefix doctest handler
> https://trac.sagemath.org/ticket/32938
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/97b73f4d-e166-40c3-bf5c-297342b10626n%40googlegroups.com.

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

[Matthias Köppe]

>From singularlog:

In file included from bbfan.cc:17:
In file included from ./gfan.h:18:
/Users/gms/sage/sage-9.5.rc1/local/include/cddlib/cdd.h:26:10: fatal error: 
'cdd_f.h' file not found
#include "cdd_f.h"
 ^
1 error generated.
make[10]: *** [gfanlib_la-bbfan.lo] Error 1

This is very strange. Could you (1) check what's in local/include/cddlib/ 
and (2) reinstall cddlib using "make cddlib-clean cddlib"?


On Sunday, January 16, 2022 at 2:17:58 AM UTC-8 list...@gmail.com wrote:

>
> There was no /usr/local/opt.
> I eliminated all references to /usr/local/opt in .bash_profile.
> Uninstalled homebrew and reinstalled it.
>
> I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 4m27.295s
>
> user 12m14.754s
>
> sys 3m20.702s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>
>
> * package: singular-4.2.1p3
>
>   last build time: Jan 16 00:18
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>
>
> * package: tachyon-0.98.9.p7
>
>   last build time: Jan 16 11:08
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>
>
> [...]
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> Logs attached.
>
> On Sun, 16 Jan 2022 at 01:38, Matthias Köppe  wrote:
>
>> It looks like you have homebrew installed both for x86_64 (in /usr/local) 
>> and for arm64 (in /opt/homebrew). Could you check if moving /usr/local out 
>> of the way fixes the build errors?
>>
>> On Saturday, January 15, 2022 at 4:25:49 PM UTC-8 list...@gmail.com 
>> wrote:
>>
>>>
>>> Here it is.
>>>
>>> On Sun, 16 Jan 2022 at 01:23, Matthias Köppe  
>>> wrote:
>>>
 config.log please

 On Saturday, January 15, 2022 at 3:24:58 PM UTC-8 list...@gmail.com 
 wrote:

>
> Trying to build on an M1 Mac under macOS 11.6.2, I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 3m36.733s
>
> user 4m58.426s
>
> sys 1m2.949s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: zn_poly-0.9.2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/zn_poly-0.9.2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/zn_poly-0.9.2
>
>
> * package: ratpoints-2.1.3.p5
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/ratpoints-2.1.3.p5.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/ratpoints-2.1.3.p5
>
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>
>
> * package: singular-4.2.1p3
>
>   last build time: Jan 16 00:18
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>
>
> [...]
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> Logs attached.
>
> HTH
>
> Guillermo
>
> On Sat, 15 Jan 2022 at 22:01, Matthias Köppe  
> wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of 
>> platform support in 
>> https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions, 
>> including Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets 
>> marked "critical"/"blocker", such as 
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple 
>> Silicon (M1) platform.* So it would be good if users/developers who 
>> have access to this platform test the release 

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

[G. M.-S.]

I should add that this failed:

$ brew install apaffenholz/polymake/polymake

[...]

==> *./configure --prefix=/opt/homebrew/Cellar/polymake/4.5 --without-bliss
--without-java --without-scip --without-soplex --without-singular
--with-brew=bottle*

Last 15 lines from /Users/gms/Library/Logs/Homebrew/polymake/219.configure:

2022-01-16 10:22:51 +


./configure

--prefix=/opt/homebrew/Cellar/polymake/4.5

--without-bliss

--without-java

--without-scip

--without-soplex

--without-singular

--with-brew=bottle


checking C++ compiler ... ok (clang++ is Apple CLANG (roughly 10.0) from
Xcode 13.0.0)

checking C++ library ... ok (libc++ 12000, C++ 201402)

checking for package manager ... Homebrew installation seems corrupt: no
shared libraries found in /usr/local/lib


If reporting this issue please do so at (not Homebrew/brew or
Homebrew/core):

  https://github.com/apaffenholz/homebrew-polymake/issues


These open issues may also help:

Brewing polymake on Apple Silicon / M1 / arm
https://github.com/apaffenholz/homebrew-polymake/issues/2

and I could not find anything relevant about this.

On Sun, 16 Jan 2022 at 11:17, G. M.-S.  wrote:

>
> There was no /usr/local/opt.
> I eliminated all references to /usr/local/opt in .bash_profile.
> Uninstalled homebrew and reinstalled it.
>
> I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 4m27.295s
>
> user 12m14.754s
>
> sys 3m20.702s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>
>
> * package: singular-4.2.1p3
>
>   last build time: Jan 16 00:18
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>
>
> * package: tachyon-0.98.9.p7
>
>   last build time: Jan 16 11:08
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/tachyon-0.98.9.p7.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/tachyon-0.98.9.p7
>
>
> [...]
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> Logs attached.
>
> On Sun, 16 Jan 2022 at 01:38, Matthias Köppe 
> wrote:
>
>> It looks like you have homebrew installed both for x86_64 (in /usr/local)
>> and for arm64 (in /opt/homebrew). Could you check if moving /usr/local out
>> of the way fixes the build errors?
>>
>> On Saturday, January 15, 2022 at 4:25:49 PM UTC-8 list...@gmail.com
>> wrote:
>>
>>>
>>> Here it is.
>>>
>>> On Sun, 16 Jan 2022 at 01:23, Matthias Köppe 
>>> wrote:
>>>
 config.log please

 On Saturday, January 15, 2022 at 3:24:58 PM UTC-8 list...@gmail.com
 wrote:

>
> Trying to build on an M1 Mac under macOS 11.6.2, I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 3m36.733s
>
> user 4m58.426s
>
> sys 1m2.949s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: zn_poly-0.9.2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/zn_poly-0.9.2.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/zn_poly-0.9.2
>
>
> * package: ratpoints-2.1.3.p5
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/ratpoints-2.1.3.p5.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/ratpoints-2.1.3.p5
>
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>
>
> * package: singular-4.2.1p3
>
>   last build time: Jan 16 00:18
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>
>   build directory:
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>
>
> [...]
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> Logs attached.
>
> HTH
>
> Guillermo
>
> On Sat, 15 Jan 2022 at 22:01, Matthias Köppe 
> wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of
>> platform support in
>> 

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

[Matthias Köppe]

It looks like you have homebrew installed both for x86_64 (in /usr/local) 
and for arm64 (in /opt/homebrew). Could you check if moving /usr/local out 
of the way fixes the build errors?

On Saturday, January 15, 2022 at 4:25:49 PM UTC-8 list...@gmail.com wrote:

>
> Here it is.
>
> On Sun, 16 Jan 2022 at 01:23, Matthias Köppe  wrote:
>
>> config.log please
>>
>> On Saturday, January 15, 2022 at 3:24:58 PM UTC-8 list...@gmail.com 
>> wrote:
>>
>>>
>>> Trying to build on an M1 Mac under macOS 11.6.2, I get
>>>
>>> make[2]: *** [all-start] Error 2
>>>
>>>
>>> real 3m36.733s
>>>
>>> user 4m58.426s
>>>
>>> sys 1m2.949s
>>>
>>> ***
>>>
>>> Error building Sage.
>>>
>>>
>>> The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make all-start'):
>>>
>>>
>>> * package: zn_poly-0.9.2
>>>
>>>   last build time: Jan 16 00:17
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/zn_poly-0.9.2.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/zn_poly-0.9.2
>>>
>>>
>>> * package: ratpoints-2.1.3.p5
>>>
>>>   last build time: Jan 16 00:17
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/ratpoints-2.1.3.p5.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/ratpoints-2.1.3.p5
>>>
>>>
>>> * package: iml-1.0.4p1.p2
>>>
>>>   last build time: Jan 16 00:17
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>>>
>>>
>>> * package: singular-4.2.1p3
>>>
>>>   last build time: Jan 16 00:18
>>>
>>>   log file:
>>> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>>>
>>>   build directory: 
>>> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>>>
>>>
>>> [...]
>>>
>>>
>>> make[1]: *** [all-start] Error 1
>>>
>>> make: *** [all] Error 2
>>>
>>> Logs attached.
>>>
>>> HTH
>>>
>>> Guillermo
>>>
>>> On Sat, 15 Jan 2022 at 22:01, Matthias Köppe  
>>> wrote:
>>>
 Based on the runs on GH Actions, I have updated the summary of platform 
 support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources

 TL;DR: It's all good now on all platforms tested on GH Actions, 
 including Cygwin.
 But I would urge that 9.5 still merge the positively reviews tickets 
 marked "critical"/"blocker", such as 
 https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
 presence of pyenv).
 Also *note we have absolutely no automatic testing for the Apple 
 Silicon (M1) platform.* So it would be good if users/developers who 
 have access to this platform test the release candidate.

>>>  
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/aab6b03b-e723-4d83-a5e0-484ded41c3d3n%40googlegroups.com.

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

[Matthias Köppe]

config.log please

On Saturday, January 15, 2022 at 3:24:58 PM UTC-8 list...@gmail.com wrote:

>
> Trying to build on an M1 Mac under macOS 11.6.2, I get
>
> make[2]: *** [all-start] Error 2
>
>
> real 3m36.733s
>
> user 4m58.426s
>
> sys 1m2.949s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: zn_poly-0.9.2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/zn_poly-0.9.2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/zn_poly-0.9.2
>
>
> * package: ratpoints-2.1.3.p5
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/ratpoints-2.1.3.p5.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/ratpoints-2.1.3.p5
>
>
> * package: iml-1.0.4p1.p2
>
>   last build time: Jan 16 00:17
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/iml-1.0.4p1.p2.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/iml-1.0.4p1.p2
>
>
> * package: singular-4.2.1p3
>
>   last build time: Jan 16 00:18
>
>   log file:
> /Users/gms/sage/sage-9.5.rc1/logs/pkgs/singular-4.2.1p3.log
>
>   build directory: 
> /Users/gms/sage/sage-9.5.rc1/local/var/tmp/sage/build/singular-4.2.1p3
>
>
> [...]
>
>
> make[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
> Logs attached.
>
> HTH
>
> Guillermo
>
> On Sat, 15 Jan 2022 at 22:01, Matthias Köppe  wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of platform 
>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions, including 
>> Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets 
>> marked "critical"/"blocker", such as 
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple Silicon 
>> (M1) platform.* So it would be good if users/developers who have access 
>> to this platform test the release candidate.
>>
>  
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/0fe6d937-9204-4d2f-b2a1-d8a5ef80c476n%40googlegroups.com.

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

[Matthias Köppe]

https://github.com/3-manifolds/Sage_macOS/blob/main/SETUP may need 
updating...

On Saturday, January 15, 2022 at 2:49:42 PM UTC-8 Matthias Köppe wrote:

> Hi Marc,
> Awesome! I've added it to 
> https://wiki.sagemath.org/ReleaseTours/sage-9.5#Binaries
> Matthias
>
> On Saturday, January 15, 2022 at 2:30:08 PM UTC-8 marc@gmail.com 
> wrote:
>
>> Hi Matthias,
>>
>> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
>> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
>> There are two separate disk images.  You may recall that I do not use 
>> Homebrew or Conda, but I did have to use an experimental binary release of 
>> gfortran for M1 since I was not able to build the gfortran spkg.
>>
>> - Marc
>>
>> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
>> wrote:
>>
>>> Based on the runs on GH Actions, I have updated the summary of platform 
>>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>>
>>> TL;DR: It's all good now on all platforms tested on GH Actions, 
>>> including Cygwin.
>>> But I would urge that 9.5 still merge the positively reviews tickets 
>>> marked "critical"/"blocker", such as 
>>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>>> presence of pyenv).
>>> Also *note we have absolutely no automatic testing for the Apple 
>>> Silicon (M1) platform.* So it would be good if users/developers who 
>>> have access to this platform test the release candidate.
>>>
>>>
>>>
>>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>>
 On Thursday, January 13, 2022 at 3:22:03 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
>
> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
> SageMath version to 9.5.rc1
>

 Thanks for the new rc. Tests are running at 
 https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, 
 macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 
 (Cygwin).





  

>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c90da3b5-05e7-4468-b536-1078262efb0cn%40googlegroups.com.

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

[Matthias Köppe]

Hi Marc,
Awesome! I've added it 
to https://wiki.sagemath.org/ReleaseTours/sage-9.5#Binaries
Matthias

On Saturday, January 15, 2022 at 2:30:08 PM UTC-8 marc@gmail.com wrote:

> Hi Matthias,
>
> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  
> There are two separate disk images.  You may recall that I do not use 
> Homebrew or Conda, but I did have to use an experimental binary release of 
> gfortran for M1 since I was not able to build the gfortran spkg.
>
> - Marc
>
> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
> wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of platform 
>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions, including 
>> Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets 
>> marked "critical"/"blocker", such as 
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple Silicon 
>> (M1) platform.* So it would be good if users/developers who have access 
>> to this platform test the release candidate.
>>
>>
>>
>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>
>>> On Thursday, January 13, 2022 at 3:22:03 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

 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
 SageMath version to 9.5.rc1

>>>
>>> Thanks for the new rc. Tests are running at 
>>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS) 
>>> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>>>
>>>
>>>
>>>
>>>
>>>  
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/29397142-4776-4dea-8ec7-236ea147ba1bn%40googlegroups.com.

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

[Marc Culler]

Hi Matthias,

I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs 
at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1.  There 
are two separate disk images.  You may recall that I do not use Homebrew or 
Conda, but I did have to use an experimental binary release of gfortran for 
M1 since I was not able to build the gfortran spkg.

- Marc

On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com 
wrote:

> Based on the runs on GH Actions, I have updated the summary of platform 
> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>
> TL;DR: It's all good now on all platforms tested on GH Actions, including 
> Cygwin.
> But I would urge that 9.5 still merge the positively reviews tickets 
> marked "critical"/"blocker", such as 
> https://trac.sagemath.org/ticket/29285 (which fixes the build in the 
> presence of pyenv).
> Also *note we have absolutely no automatic testing for the Apple Silicon 
> (M1) platform.* So it would be good if users/developers who have access 
> to this platform test the release candidate.
>
>
>
> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>
>> On Thursday, January 13, 2022 at 3:22:03 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
>>>
>>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated 
>>> SageMath version to 9.5.rc1
>>>
>>
>> Thanks for the new rc. Tests are running at 
>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS) 
>> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>>
>>
>>
>>
>>
>>  
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/80a15099-33d4-4e5a-8b86-ccd6d47c2d55n%40googlegroups.com.

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

[Thierry Dumont]

Le 15/01/2022 à 14:03, Markus Wageringel a écrit :

I have also seen this error, but it disappeared after a distclean.


Yes ! thanks.
t.d.

tdumont schrieb am Freitag, 14. Januar 2022 um 14:18:30 UTC+1:


Upgrading to 9.5rc1 on Ubuntu 21-10:

- compilation ok.

- make ptestlong:
 ERRORS

_ ERROR collecting sage/structure/sage_object_test.py
__
ImportError while importing test module
'/usr/local/sages/dev/sage/src/sage/structure/sage_object_test.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
src/sage/structure/sage_object_test.py:3: in 
from .sage_object import SageObject
E ImportError: attempted relative import with no known parent package
=== short test summary info
===

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/53419cfa-a623-4c35-8f96-ab898e51bc02n%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9e696fc1-9b9a-b2a3-301c-9c5148002289%40math.univ-lyon1.fr.

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

[G. M.-S.]

I found it. Sorry for the noise.

Guillermo

On Sat, 15 Jan 2022 at 22:12, G. M.-S.  wrote:

>
> Hello Matthias.
>
> I can try to build 9.5rc1 on an M1 Mac, but I need to know how to get the
> source tarball (I am not familiar with git).
>
> Guillermo
>
> On Sat, 15 Jan 2022 at 22:01, Matthias Köppe 
> wrote:
>
>> Based on the runs on GH Actions, I have updated the summary of platform
>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>>
>> TL;DR: It's all good now on all platforms tested on GH Actions, including
>> Cygwin.
>> But I would urge that 9.5 still merge the positively reviews tickets
>> marked "critical"/"blocker", such as
>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the
>> presence of pyenv).
>> Also *note we have absolutely no automatic testing for the Apple Silicon
>> (M1) platform.* So it would be good if users/developers who have access
>> to this platform test the release candidate.
>>
>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>>
>>> On Thursday, January 13, 2022 at 3:22:03 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

 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated
 SageMath version to 9.5.rc1

>>>
>>> Thanks for the new rc. Tests are running at
>>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS)
>>> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>>>
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CANnG1895aS%2BcTquuwLBiwyxDbS-toKbY2fGuTdY1HwRaWhWy_Q%40mail.gmail.com.

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

[G. M.-S.]

Hello Matthias.

I can try to build 9.5rc1 on an M1 Mac, but I need to know how to get the
source tarball (I am not familiar with git).

Guillermo

On Sat, 15 Jan 2022 at 22:01, Matthias Köppe 
wrote:

> Based on the runs on GH Actions, I have updated the summary of platform
> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources
>
> TL;DR: It's all good now on all platforms tested on GH Actions, including
> Cygwin.
> But I would urge that 9.5 still merge the positively reviews tickets
> marked "critical"/"blocker", such as
> https://trac.sagemath.org/ticket/29285 (which fixes the build in the
> presence of pyenv).
> Also *note we have absolutely no automatic testing for the Apple Silicon
> (M1) platform.* So it would be good if users/developers who have access
> to this platform test the release candidate.
>
> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:
>
>> On Thursday, January 13, 2022 at 3:22:03 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
>>>
>>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated
>>> SageMath version to 9.5.rc1
>>>
>>
>> Thanks for the new rc. Tests are running at
>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS)
>> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CANnG189fJDOdyJvnQK-hLATmvSjh14t6Cx6Q9sW3ac-9Zfk8%2BA%40mail.gmail.com.

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

[Matthias Köppe]

Based on the runs on GH Actions, I have updated the summary of platform 
support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources

TL;DR: It's all good now on all platforms tested on GH Actions, including 
Cygwin.
But I would urge that 9.5 still merge the positively reviews tickets marked 
"critical"/"blocker", such as https://trac.sagemath.org/ticket/29285 (which 
fixes the build in the presence of pyenv).
Also *note we have absolutely no automatic testing for the Apple Silicon 
(M1) platform.* So it would be good if users/developers who have access to 
this platform test the release candidate.



On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote:

> On Thursday, January 13, 2022 at 3:22:03 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
>>
>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated SageMath 
>> version to 9.5.rc1
>>
>
> Thanks for the new rc. Tests are running at 
> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS) 
> and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).
>
>
>
>
>
>  
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f06d3236-612b-4fe3-aa9a-8958bb7a7ef0n%40googlegroups.com.

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

[Markus Wageringel]

I have also seen this error, but it disappeared after a distclean.

tdumont schrieb am Freitag, 14. Januar 2022 um 14:18:30 UTC+1:

>
> Upgrading to 9.5rc1 on Ubuntu 21-10:
>
> - compilation ok.
>
> - make ptestlong:
>  ERRORS 
> 
> _ ERROR collecting sage/structure/sage_object_test.py 
> __
> ImportError while importing test module 
> '/usr/local/sages/dev/sage/src/sage/structure/sage_object_test.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> src/sage/structure/sage_object_test.py:3: in 
> from .sage_object import SageObject
> E ImportError: attempted relative import with no known parent package
> === short test summary info 
> ===
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/53419cfa-a623-4c35-8f96-ab898e51bc02n%40googlegroups.com.

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

[Emmanuel Charpentier]

FWIW, upgrading 9.5.rc0 to 9.5.rc1 and running ptestlong gives *exactly*  
the same results as those reported for 9.5.rc0.

HTH,
​
Le vendredi 14 janvier 2022 à 00:22:03 UTC+1, Volker Braun a écrit :

> 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
>
> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated SageMath 
> version to 9.5.rc1
> 8e7a22529e  Trac #33145: fedora-{26,27,28,...}-minimal: pyzmq build failure
> 92bd273637 Trac #33138: Fix SAGE_FAT_BINARY regression for numpy 
> ("Ignoring --build-option when building numpy using PEP 517")
> 164685913f Trac #32744: composite elliptic-curve isogenies
> 9a48a8a4cb Trac #32502: make WeierstrassIsomorphism behave (more) like 
> EllipticCurveIsogeny
> 2846293836 Trac #33014: Update ore_algebra to latest version
> de2bfc6269 Trac #33111: Update installation manual section "Setting up 
> SageMath as a Jupyter kernel"
> 91cdefb5ce Trac #33130: Fix silent "sage -b" after #32759
> 2e4b8bef73 Trac #33135: Filter out some distutils deprecation warnings 
> with python 3.10
> cee501534d Trac #33143: Matplotlib update breaks build on debian buster
> 38323507f6 (tag: 9.5.rc0) Updated SageMath version to 9.5.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/110ce7b6-4a11-4aec-8247-188af098e56dn%40googlegroups.com.

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

[Samuel Lelièvre]

2022-01-14 21:49 UTC, Sébastien Labbé:
>
> The failures with the following files are new and are copied below:
>
> SEED=115792415560373440200802359516411195501
> alias sagetest="./sage -t --long --random-seed=$SEED"
> sagetest src/sage/databases/findstat.py  # 12 doctests failed
> sagetest src/sage/databases/oeis.py  # 1 doctest failed
> sagetest src/sage/interfaces/mathematica.py  # 1 doctest failed

These might be a fallout of #32938, merged in Sage 9.5.rc0.

- Sage Trac ticket #32938
  deactivation of the u-prefix doctest handler
  https://trac.sagemath.org/ticket/32938

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAEcArF1aSu9dm6%2BB6iEkzRis4_uKG75gDms71wmLW8dxeAHn2w%40mail.gmail.com.

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

[Sébastien Labbé]

On Ubuntu 20.04, running tests with various optional and external packages 
(including internet optional tag), I obtain:


Using 
--optional=4ti2,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_spkg
Features to be detected: 
4ti2,benzene,bliss,buckygen,conway_polynomials,cplex,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,gurobi,imagemagick,internet,jupymake,kenzo,latex,latex_package_tkz_graph,latte_int,lrslib,lualatex,macaulay2,magma,maple,mathematica,matlab,mcqd,meataxe,octave,pandoc,pdf2svg,pdflatex,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,scilab,sphinx,tdlib,xelatex

[...]

--
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/doc/en/reference/sat/index.rst  # 2 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/combinat/designs/incidence_structures.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/combinat/matrices/dancing_links.pyx  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/databases/findstat.py  # 12 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/graphs/generic_graph.py  # 2 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/graphs/graph.py  # 3 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/interfaces/mathematica.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/interfaces/octave.py  # 3 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/rings/polynomial/multi_polynomial_sequence.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/sat/boolean_polynomials.py  # 18 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/sat/solvers/cryptominisat.py  # 38 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/sat/solvers/satsolver.pyx  # 5 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/tests/cmdline.py  # 1 doctest failed
--
Features detected for doctesting: 
dvipng,ffmpeg,graphviz,imagemagick,internet,latex,latex_package_tkz_graph,lualatex,octave,pandoc,pdf2svg,pdflatex,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sagemath_doc_html,sphinx,xelatex


The failures of the following 6 six files are known from a long time, see 
https://trac.sagemath.org/ticket/25536 ::

sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/combinat/designs/incidence_structures.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/tests/cmdline.py  # 1 doctest failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/graphs/generic_graph.py  # 2 doctests failed
sage -t --long --random-seed=115792415560373440200802359516411195501 
src/sage/graphs/graph.py  # 3 doctests failed

The failures of the following 6 six files are related to cryptominisat, see 
https://trac.sagemath.org/ticket/33162:

sage -t --long --random-seed=277349812120896257585806851727004727044 
src/sage/sat/boolean_polynomials.py  # 18 doctests failed
sage -t --long --random-seed=277349812120896257585806851727004727044 
src/sage/rings/polynomial/multi_polynomial_sequence.py  # 1 doctest failed
sage -t --long --random-seed=277349812120896257585806851727004727044 
src/sage/combinat/matrices/dancing_links.pyx  # 1 doctest failed
sage -t --long --random-seed=277349812120896257585806851727004727044 
src/doc/en/reference/sat/index.rst  # 2 doctests failed
sage -t --long --random-seed=277349812120896257585806851727004727044 
src/sage/sat/solvers/satsolver.pyx  # 5 doctests failed
sage -t --long --random-seed=277349812120896257585806851727004727044 
src/sage/sat/solvers/cryptominisat.py  # 38 doctests failed

The failures 

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

[Matthias Köppe]

On Thursday, January 13, 2022 at 3:22:03 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
>
> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated SageMath 
> version to 9.5.rc1
>

Thanks for the new rc. Tests are running 
at https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, macOS) 
and https://github.com/sagemath/sage/actions/runs/1690315874 (Cygwin).





 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9827bf2a-73c3-47b7-afe2-5e03f80c10bbn%40googlegroups.com.

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

[Thierry Dumont]

Upgrading to  9.5rc1 on Ubuntu 21-10:

- compilation ok.

- make ptestlong:
 ERRORS 

_ ERROR collecting sage/structure/sage_object_test.py 
__
ImportError while importing test module 
'/usr/local/sages/dev/sage/src/sage/structure/sage_object_test.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
src/sage/structure/sage_object_test.py:3: in 
from .sage_object import SageObject
E   ImportError: attempted relative import with no known parent package
=== short test summary info 
===


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/994144ae-0dac-fd92-1fe4-fe569dd54363%40math.univ-lyon1.fr.

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

[Eric Gourgoulhon]

Le vendredi 14 janvier 2022 à 11:54:23 UTC+1, Sébastien Labbé a écrit :

> On Friday, January 14, 2022 at 10:10:00 AM UTC+1 egourg...@gmail.com 
> wrote:
>
>> This is a permanent failure:
>> sage -t --long --warn-long 67.0 
>> --random-seed=127661401430613686989226810121136436198 
>> src/sage/game_theory/parser.py
>>
>
> A ticket exists for this issue: 
> https://trac.sagemath.org/ticket/33101 
>

Indeed! Thanks for pointing it out.

Eric.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/672d91d7-55a8-4d07-91f9-c2cfb851b3e3n%40googlegroups.com.

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

[Eric Gourgoulhon]

Le vendredi 14 janvier 2022 à 11:00:31 UTC+1, Dima Pasechnik a écrit :

>
> is this system-wide lrslib? 
>

Yes this is from Ubuntu package lrslib 0.70-3.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/2e1101de-5016-4faf-ad95-57d7a3158614n%40googlegroups.com.

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

[Henri Girard]

I just compiled it without any problems... rc0 I couldn't compile doc 
rc1 works fine in ubuntu 22.04 (out in april) rizen 16 16Go RAM ubuntu 22.04



Le 14/01/2022 à 11:41, Samuel Lelièvre a écrit :

2022-01-14 10:00 UTC, Dima Pasechnik:

On Fri, Jan 14, 2022 at 9:10 AM Eric Gourgoulhon:

On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from 9.5.beta8, with system python (3.8.10): OK
- make ptestlong --> 2 doctests failed in src/sage/game_theory/parser.py

This is a permanent failure:
[...]

is this system-wide lrslib?
I'd say it's Ubuntu's bug then.

The problem is more likely with our doctest framework and its
articulation with our feature detection, more specifically doctests
marked "optional - lrslib" are run as soon as lrslib is detected,
even in the case when the detected lrslib would not be deemed
good enough to use for Sage.

Similar problems have been reported recently with other optional
packages, such as ffmpeg and imagemagick. See

- #33092: ffmpeg/imagemagick features need feature checks
- #33114: Feature.require vs. is_present, is_functional



--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c1f3300c-f869-b34b-ddc9-9db3014f3d7e%40gmail.com.

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

[Sébastien Labbé]

On Friday, January 14, 2022 at 10:10:00 AM UTC+1 egourg...@gmail.com wrote:

> This is a permanent failure:
> sage -t --long --warn-long 67.0 
> --random-seed=127661401430613686989226810121136436198 
> src/sage/game_theory/parser.py
>

A ticket exists for this issue: 
https://trac.sagemath.org/ticket/33101 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d2247cd2-3865-4a7c-a72b-7a4730a66a99n%40googlegroups.com.

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

[Samuel Lelièvre]

2022-01-14 10:00 UTC, Dima Pasechnik:
>
> On Fri, Jan 14, 2022 at 9:10 AM Eric Gourgoulhon:
> >
> > On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
> > - incremental build (-j16) from 9.5.beta8, with system python (3.8.10): OK
> > - make ptestlong --> 2 doctests failed in src/sage/game_theory/parser.py
> >
> > This is a permanent failure:
> > [...]
>
> is this system-wide lrslib?
> I'd say it's Ubuntu's bug then.

The problem is more likely with our doctest framework and its
articulation with our feature detection, more specifically doctests
marked "optional - lrslib" are run as soon as lrslib is detected,
even in the case when the detected lrslib would not be deemed
good enough to use for Sage.

Similar problems have been reported recently with other optional
packages, such as ffmpeg and imagemagick. See

- #33092: ffmpeg/imagemagick features need feature checks
- #33114: Feature.require vs. is_present, is_functional

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAEcArF3QObgCfcdNwk%2B6wZRZ5APp_d%3DAqbeNR6OKAhzaRS4LAw%40mail.gmail.com.

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

[Dima Pasechnik]

On Fri, Jan 14, 2022 at 9:10 AM Eric Gourgoulhon  wrote:
>
> On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
> - incremental build (-j16) from 9.5.beta8, with system python (3.8.10): OK
> - make ptestlong --> 2 doctests failed in src/sage/game_theory/parser.py
>
> This is a permanent failure:
>
> sage -t --long --warn-long 67.0 
> --random-seed=127661401430613686989226810121136436198 
> src/sage/game_theory/parser.py
> **
> File "src/sage/game_theory/parser.py", line 75, in 
> sage.game_theory.parser.Parser.format_lrs
> Failed example:
> lrs_output[:-2]# 
> optional - lrslib
> Expected:
> [...,
>  '2  0  1  2 \n',
>  '1  1/2  1/2 -2 \n',
>  '\n',
>  '2  0  1  2 \n',
>  '1  0  1 -2 \n',
>  '\n',
>  '*Number of equilibria found: 2\n',
>  '*Player 1: vertices=3 bases=3 pivots=5\n',
>  '*Player 2: vertices=2 bases=1 pivots=6\n',
>  '\n']
> Got:
> ['*lrsnash:lrslib v.7.0 2018.7.1(64bit,lrsgmp.h,hybrid arithmetic) gmp 
> v.6.1\n',
>  '2  0  1  2 \n',
>  '1  1/2  1/2 -2 \n',
>  '\n',
>  '2  0  1  2 \n',
>  '1  0  1 -2 \n',
>  '\n',
>  '*Number of equilibria found: 2\n',
>  '*Player 1: vertices=3 bases=3 pivots=5\n',
>  '*Player 2: vertices=2 bases=1 pivots=6\n',
>  '\n',
>  '*lrsnash:lrslib v.7.0 2018.7.1(64bit,lrsgmp.h,hybrid arithmetic)\n']
> **

is this system-wide lrslib?
I'd say it's Ubuntu's bug then.

>
> On another Ubuntu 20.04 computer, but with lrslib not installed, no error is 
> reported, certainly because the doctest is skipped due to the marker 
> "optional - lrslib".
>
> Eric.
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/fa6a174e-357a-4119-8eea-f22b28735997n%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq1KXb0_G2neXt0HChrcqjDBt_LCJzrmWdU4tfBERo7Apg%40mail.gmail.com.

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

[Eric Gourgoulhon]

On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from 9.5.beta8, with system python (3.8.10): OK
- make ptestlong --> 2 doctests failed in src/sage/game_theory/parser.py

This is a permanent failure:

sage -t --long --warn-long 67.0 
--random-seed=127661401430613686989226810121136436198 
src/sage/game_theory/parser.py
**
File "src/sage/game_theory/parser.py", line 75, in 
sage.game_theory.parser.Parser.format_lrs
Failed example:
lrs_output[:-2]# 
optional - lrslib
Expected:
[...,
 '2  0  1  2 \n',
 '1  1/2  1/2 -2 \n',
 '\n',
 '2  0  1  2 \n',
 '1  0  1 -2 \n',
 '\n',
 '*Number of equilibria found: 2\n',
 '*Player 1: vertices=3 bases=3 pivots=5\n',
 '*Player 2: vertices=2 bases=1 pivots=6\n',
 '\n']
Got:
['*lrsnash:lrslib v.7.0 2018.7.1(64bit,lrsgmp.h,hybrid arithmetic) gmp 
v.6.1\n',
 '2  0  1  2 \n',
 '1  1/2  1/2 -2 \n',
 '\n',
 '2  0  1  2 \n',
 '1  0  1 -2 \n',
 '\n',
 '*Number of equilibria found: 2\n',
 '*Player 1: vertices=3 bases=3 pivots=5\n',
 '*Player 2: vertices=2 bases=1 pivots=6\n',
 '\n',
 '*lrsnash:lrslib v.7.0 2018.7.1(64bit,lrsgmp.h,hybrid arithmetic)\n']
**

On another Ubuntu 20.04 computer, but with lrslib not installed, no error 
is reported, certainly because the doctest is skipped due to the marker 
"optional - lrslib".

Eric.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/fa6a174e-357a-4119-8eea-f22b28735997n%40googlegroups.com.