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

[Dima Pasechnik]

I guess you might be missing gmp-c++ system package.
Please install it and try again. It seems we need to look at what ppl does in 
its gmp detection code and do the same in our configure.

<https://packages.fedoraproject.org/pkgs/gmp/gmp-c++/fedora-40.html>



On 4 May 2024 12:16:22 BST, Jaap Spies  wrote:
>Here it is.
>
>Jaap
>
>On Sat, May 4, 2024 at 1:03 PM Dima Pasechnik  wrote:
>
>> hmm, no, your system GMP looks fine,  it was duly detected by the top
>> level configure.
>>
>> It is however rejected by ppl.
>> Can you post the appropriate logs/pkgs/ppl... log file?
>>
>>
>> On 4 May 2024 11:31:11 BST, Jaap Spies  wrote:
>>
>>> Sorry wrong attachment!
>>>
>>>
>>>
>>> On Sat, May 4, 2024 at 12:26 PM Jaap Spies  wrote:
>>>
>>>>
>>>> Last metadata expiration check: 3:24:12 ago on za 04 mei 2024 08:57:46
>>>> CEST.
>>>> Package gmp-1:6.2.1-8.fc40.x86_64 is already installed.
>>>> Package gmp-devel-1:6.2.1-8.fc40.x86_64 is already installed.
>>>> Package gmp-ecm-7.0.5-5.fc40.x86_64 is already installed.
>>>> Package gmp-ecm-devel-7.0.5-5.fc40.x86_64 is already installed.
>>>> Dependencies resolved.
>>>> Nothing to do.
>>>> Complete!
>>>>
>>>> The config.log attached.
>>>>
>>>> Jaap
>>>>
>>>> On Sat, May 4, 2024 at 12:09 PM Dima Pasechnik 
>>>> wrote:
>>>>
>>>>> You probably have an incomplete install of system GMP packages, or/and,
>>>>> perhaps, a spurious install of GMP in /usr/local ...
>>>>>
>>>>>
>>>>> Please post top-level config.log
>>>>>
>>>>>
>>>>>
>>>>> On 4 May 2024 10:27:09 BST, Jaap Spies  wrote:
>>>>>
>>>>>> On Fedora 40 building fails with
>>>>>> * package: ppl-1.2.p1
>>>>>>  last build time: mei 3 22:09
>>>>>>  log file:
>>>>>>/home/jaap/sagemath/sage-10.4.beta5/logs/pkgs/ppl-1.2.p1.log
>>>>>> From the log file:
>>>>>> [spkg-install] config.lt: creating libtool
>>>>>> [spkg-install] checking for the GMP library version 4.1.3 or above...
>>>>>> no
>>>>>> [spkg-install] configure: error: Cannot find GMP version 4.1.3 or
>>>>>> higher.
>>>>>>
>>>>>> But Fedora 40 comes with gmp version 6.2.1
>>>>>>
>>>>>> Jaap
>>>>>>
>>>>>>
>>>>>> On Fri, May 3, 2024 at 1:08 AM 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
>>>>>>>
>>>>>>>
>>>>>>> 744939e037a (github/develop, tag: 10.4.beta5) Updated SageMath
>>>>>>> version to 10.4.beta5
>>>>>>> e77b3df44ad gh-37915: Replace doctests from jacobian_khuri_makdisi.py
>>>>>>> taking too long time
>>>>>>> 422c59e95ce gh-37911: Fix overflow in hypergeometric trace
>>>>>>> 67f26757bcb gh-37904: Change `SetSystem` representation
>>>>>>> a1354a74b91 gh-37883: gap: don't use deprecated LaTeX() and LaTeXObj()
>>>>>>> 53566be0ca2 gh-37882: eclib: fix doctests after 20240408 update
>>>>>>> 31cf6d3b0fa gh-37872: sage.{topology,homology}: Remove deprecated
>>>>>>> chomp interface
>>>>>>> 75c86c8f28c gh-37870: `sage.ext`: Remove deprecated code
>>>>>>> c46302c3a6d gh-37868: `sage.misc.misc`: Remove deprecated code
>>>>>>> b14d3ec8dc3 gh-37856: `sage.misc.dist`: Remove; deprecated in #30207
>>>>>>> (2022)
>>>>>>> 6753fbdecdc gh-37855: `sage.misc.package`: Remove deprecated code
>>>>>>> 9ce51d09089 gh-37853: Work around inconsistent iteration in
>>>>>>> `multi_polynomial_sequence.py`
>>>>>>> 969b687c5f6 gh-37851: Fix issue 37587 regarding the Link class plot
>>>>>>> method
>>>>>>> 620babd49fb gh-37841: `.ci/write-dockerfile.sh`: Move here from
>>>>>>> build/bin/
>>>>>&

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

[Dima Pasechnik]

hmm, no, your system GMP looks fine,  it was duly detected by the top level 
configure.

It is however rejected by ppl.
Can you post the appropriate logs/pkgs/ppl... log file?

On 4 May 2024 11:31:11 BST, Jaap Spies  wrote:
>Sorry wrong attachment!
>
>
>
>On Sat, May 4, 2024 at 12:26 PM Jaap Spies  wrote:
>
>>
>> Last metadata expiration check: 3:24:12 ago on za 04 mei 2024 08:57:46
>> CEST.
>> Package gmp-1:6.2.1-8.fc40.x86_64 is already installed.
>> Package gmp-devel-1:6.2.1-8.fc40.x86_64 is already installed.
>> Package gmp-ecm-7.0.5-5.fc40.x86_64 is already installed.
>> Package gmp-ecm-devel-7.0.5-5.fc40.x86_64 is already installed.
>> Dependencies resolved.
>> Nothing to do.
>> Complete!
>>
>> The config.log attached.
>>
>> Jaap
>>
>> On Sat, May 4, 2024 at 12:09 PM Dima Pasechnik  wrote:
>>
>>> You probably have an incomplete install of system GMP packages, or/and,
>>> perhaps, a spurious install of GMP in /usr/local ...
>>>
>>>
>>> Please post top-level config.log
>>>
>>>
>>>
>>> On 4 May 2024 10:27:09 BST, Jaap Spies  wrote:
>>>
>>>> On Fedora 40 building fails with
>>>> * package: ppl-1.2.p1
>>>>  last build time: mei 3 22:09
>>>>  log file:
>>>>/home/jaap/sagemath/sage-10.4.beta5/logs/pkgs/ppl-1.2.p1.log
>>>> From the log file:
>>>> [spkg-install] config.lt: creating libtool
>>>> [spkg-install] checking for the GMP library version 4.1.3 or above... no
>>>> [spkg-install] configure: error: Cannot find GMP version 4.1.3 or
>>>> higher.
>>>>
>>>> But Fedora 40 comes with gmp version 6.2.1
>>>>
>>>> Jaap
>>>>
>>>>
>>>> On Fri, May 3, 2024 at 1:08 AM 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
>>>>>
>>>>>
>>>>> 744939e037a (github/develop, tag: 10.4.beta5) Updated SageMath version
>>>>> to 10.4.beta5
>>>>> e77b3df44ad gh-37915: Replace doctests from jacobian_khuri_makdisi.py
>>>>> taking too long time
>>>>> 422c59e95ce gh-37911: Fix overflow in hypergeometric trace
>>>>> 67f26757bcb gh-37904: Change `SetSystem` representation
>>>>> a1354a74b91 gh-37883: gap: don't use deprecated LaTeX() and LaTeXObj()
>>>>> 53566be0ca2 gh-37882: eclib: fix doctests after 20240408 update
>>>>> 31cf6d3b0fa gh-37872: sage.{topology,homology}: Remove deprecated chomp
>>>>> interface
>>>>> 75c86c8f28c gh-37870: `sage.ext`: Remove deprecated code
>>>>> c46302c3a6d gh-37868: `sage.misc.misc`: Remove deprecated code
>>>>> b14d3ec8dc3 gh-37856: `sage.misc.dist`: Remove; deprecated in #30207
>>>>> (2022)
>>>>> 6753fbdecdc gh-37855: `sage.misc.package`: Remove deprecated code
>>>>> 9ce51d09089 gh-37853: Work around inconsistent iteration in
>>>>> `multi_polynomial_sequence.py`
>>>>> 969b687c5f6 gh-37851: Fix issue 37587 regarding the Link class plot
>>>>> method
>>>>> 620babd49fb gh-37841: `.ci/write-dockerfile.sh`: Move here from
>>>>> build/bin/
>>>>> af6c2085804 gh-37836: fricas/do not get inputform twice
>>>>> ac9c1b07203 gh-37835: Optimize `DisjointSet`
>>>>> 6e58d87dcc1 gh-37833: `build/pkgs/{python3,setuptools}`: Update fedora
>>>>> distro info
>>>>> 5ab5dc3c3fe gh-37829: src/sage/manifolds/differentiable:
>>>>> Docstring/doctest edits
>>>>> db630cdf2d9 gh-37827: `sage.tensor`: Tiny doc fixes
>>>>> 7d0a347f99b gh-37826: FreeModuleAutomorphism: Add more invariants
>>>>> 698774f5289 gh-37825: `FiniteRankFreeModuleMorphism.display`: Show
>>>>> matrix decorated with basis element names
>>>>> 3041aac4a21 gh-37823: Fix LaTeX output of FreeModuleTensor.display_comp
>>>>> 8296cec240f gh-37822: Fix bug in TensorField.apply_map
>>>>> 71d2a96e0d7 gh-37810: build/pkgs/gambit: Remove
>>>>> f87f3e3581e gh-37808: Removed non-working and utterly old
>>>>> @rename_keyword in farey_symbol.pyx
>>>>> d64f1a8accb gh-37807: Added some documentation in the developer

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

[Dima Pasechnik]

You probably have an incomplete install of system GMP packages, or/and, 
perhaps, a spurious install of GMP in /usr/local ...


Please post top-level config.log



On 4 May 2024 10:27:09 BST, Jaap Spies  wrote:
>On Fedora 40 building fails with
>* package: ppl-1.2.p1
> last build time: mei 3 22:09
> log file:
>   /home/jaap/sagemath/sage-10.4.beta5/logs/pkgs/ppl-1.2.p1.log
>From the log file:
>[spkg-install] config.lt: creating libtool
>[spkg-install] checking for the GMP library version 4.1.3 or above... no
>[spkg-install] configure: error: Cannot find GMP version 4.1.3 or higher.
>
>But Fedora 40 comes with gmp version 6.2.1
>
>Jaap
>
>
>On Fri, May 3, 2024 at 1:08 AM 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
>>
>>
>> 744939e037a (github/develop, tag: 10.4.beta5) Updated SageMath version to
>> 10.4.beta5
>> e77b3df44ad gh-37915: Replace doctests from jacobian_khuri_makdisi.py
>> taking too long time
>> 422c59e95ce gh-37911: Fix overflow in hypergeometric trace
>> 67f26757bcb gh-37904: Change `SetSystem` representation
>> a1354a74b91 gh-37883: gap: don't use deprecated LaTeX() and LaTeXObj()
>> 53566be0ca2 gh-37882: eclib: fix doctests after 20240408 update
>> 31cf6d3b0fa gh-37872: sage.{topology,homology}: Remove deprecated chomp
>> interface
>> 75c86c8f28c gh-37870: `sage.ext`: Remove deprecated code
>> c46302c3a6d gh-37868: `sage.misc.misc`: Remove deprecated code
>> b14d3ec8dc3 gh-37856: `sage.misc.dist`: Remove; deprecated in #30207 (2022)
>> 6753fbdecdc gh-37855: `sage.misc.package`: Remove deprecated code
>> 9ce51d09089 gh-37853: Work around inconsistent iteration in
>> `multi_polynomial_sequence.py`
>> 969b687c5f6 gh-37851: Fix issue 37587 regarding the Link class plot method
>> 620babd49fb gh-37841: `.ci/write-dockerfile.sh`: Move here from build/bin/
>> af6c2085804 gh-37836: fricas/do not get inputform twice
>> ac9c1b07203 gh-37835: Optimize `DisjointSet`
>> 6e58d87dcc1 gh-37833: `build/pkgs/{python3,setuptools}`: Update fedora
>> distro info
>> 5ab5dc3c3fe gh-37829: src/sage/manifolds/differentiable: Docstring/doctest
>> edits
>> db630cdf2d9 gh-37827: `sage.tensor`: Tiny doc fixes
>> 7d0a347f99b gh-37826: FreeModuleAutomorphism: Add more invariants
>> 698774f5289 gh-37825: `FiniteRankFreeModuleMorphism.display`: Show matrix
>> decorated with basis element names
>> 3041aac4a21 gh-37823: Fix LaTeX output of FreeModuleTensor.display_comp
>> 8296cec240f gh-37822: Fix bug in TensorField.apply_map
>> 71d2a96e0d7 gh-37810: build/pkgs/gambit: Remove
>> f87f3e3581e gh-37808: Removed non-working and utterly old @rename_keyword
>> in farey_symbol.pyx
>> d64f1a8accb gh-37807: Added some documentation in the developer's guide
>> regarding deprecation
>> 68e657c09c3 gh-37802: Add the downward monotonic cone to the cone catalogue
>> abad24ff15f gh-37800: some cython-lint suggestions fixed in real rings
>> 106c0d76be6 gh-37799: little details in quadratic_forms (pep8, ruff, etc)
>> 2406c159c81 gh-37798: some ruff C4 fixes in combinat
>> ac8792fc3d2 gh-37797: fix the category of quasi-modular form rings
>> 1b5a3450555 gh-37793: add links to standard errors in various places
>> ca3d59a8f09 gh-37792: remove a stray leftover in in sa2si_ZZmod()
>> e9e3a3db928 gh-37750: CI Build: Fix "test modularized distributions"
>> after #37022
>> 9097fa25d4b gh-37738: CI Build: Show segfaults using GitHub
>> annotations
>> 46b7ec223c3 gh-37722: Remove `CombinatorialClass`
>> 19b06ac7387 gh-37715: `sage.{calculus,functions,numerical,symbolic}`:
>> Docstring/doctest cosmetics, `# needs`
>> e4e33257ab6 gh-37693: Implement the hypercenter and upper central series
>> for finite dimensional Lie algebras
>> f0a28504d47 gh-37692: `matrix`, `Graph.incidence_matrix`,
>> `LinearMatroid.representation`: Support constructing
>> `Hom(CombinatorialFreeModule)` elements
>> 9783f965806 gh-37681: Quaternion Ideal Pushforwards and Pullbacks
>> 0a75254c9ea gh-37650: src/sage/features/sagemath.py: Add feature SAGE_SRC
>> 721fc792a23 gh-37492: make sagelib work with singular>=4.3.2.p15 (future
>> 4.4)
>> 2d77ac5ea3c gh-37277: pip 24, setuptools 69.5.1, hatchling 1.22.5,
>> hatch_fancy_pypi_readme 24.1.0, platformdirs 4.2.0, packaging 24.0,
>> trove_classifiers 2024.4.10, wheel 0.43.0
>> 248fde327ef gh-37099: GH Actions: Build platform-independent wheels of
>> sagemath-environment, sage-setup, sage-sws2rst for PyPI
>> 90e08c88c60 gh-37057: deprecated functions is_Cone, is_Polyhedron,
>> is_LatticePolytope
>> ca1b5e6ea0d gh-37041: update FriCAS to 1.3.10, allow building with sbcl
>> f19f431d095 gh-36982: Make pyproject.toml the source for build dependencies
>> 23ba3d8f174 gh-36768: Retrieve more information of fundamental groups of
>> plane curves
>> f633de0146a gh-36498: CI build, doc-build: Run containers explicitly,
>> separate jobs for pyright, build, modularized 

[sage-release] Re: xz/liblzma has been compromised

[Dima Pasechnik]

and Homebrew.
Please upgrade your Homebrew. It should do a downgrade:

`brew upgrade` now "upgrades" xz from 5.6.1 -> 5.4.6

On Fri, Mar 29, 2024 at 7:36 PM Dima Pasechnik  wrote:
>
> aand Conda: https://anaconda.org/anaconda/xz shows version 5.6.1
>
> On Fri, Mar 29, 2024 at 7:18 PM Dima Pasechnik  wrote:
> >
> > https://www.openwall.com/lists/oss-security/2024/03/29/4
> >
> > if your have xz 5.6.0 or 5.6.1 installed (e.g. Debian testing/unstable)
> > you have a backdoored xz.

-- 
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/CAAWYfq3%3DOQprCMf%3Dv2ubAoZVhFEHBSjf52LT9XHAR8nRiOR3GA%40mail.gmail.com.

[sage-release] Re: xz/liblzma has been compromised

[Dima Pasechnik]

aand Conda: https://anaconda.org/anaconda/xz shows version 5.6.1

On Fri, Mar 29, 2024 at 7:18 PM Dima Pasechnik  wrote:
>
> https://www.openwall.com/lists/oss-security/2024/03/29/4
>
> if your have xz 5.6.0 or 5.6.1 installed (e.g. Debian testing/unstable)
> you have a backdoored xz.

-- 
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/CAAWYfq3TfwUtW%2B4ZV0GMr4egCUsrgjHTrTtzuVeKi5ARj4tuUA%40mail.gmail.com.

[sage-release] xz/liblzma has been compromised

[Dima Pasechnik]

https://www.openwall.com/lists/oss-security/2024/03/29/4

if your have xz 5.6.0 or 5.6.1 installed (e.g. Debian testing/unstable)
you have a backdoored xz.

-- 
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/CAAWYfq0T0eMogYB0K6isVEQy%3DL2JGfQMPrQwEXF_ECMmtiA4%2Bw%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.3 released

[Dima Pasechnik]

To explain the error you were getting, your log has

configure: WARNING: Could not find a terminal library among tinfo ncurses 
curses termlib termcap terminfo

which explains the linking error you get at the end.
I think info (texinfo) should just become a pre-req for all the systems we 
support (just as well as g++ and gfortran, by the way),
and not something one might get into building from source for the only 
reason that it's not installed, and get stuck.
There is 0 value digging out more details on this and adjusting build 
scripts accordingly, possibly (re)introducting curses or another
equally cursed package into Sage deps. 

A recent fight over these issues happened on
https://github.com/sagemath/sage/pull/36726 (and I was shouted down - as 
the enemy had the numbers on that occasion)

But I am ready for a re-match...

Dima




On Wednesday, March 20, 2024 at 11:23:01 AM UTC John Cremona wrote:

> On Wed, 20 Mar 2024 at 10:13, Dima Pasechnik  wrote:
>
>>
>>
>> On Wed, Mar 20, 2024 at 9:53 AM John Cremona  wrote:
>>
>>> Thanks for the new release.  On a ubuntu machine which I had literally 
>>> only hust upgraded from 20.04 LTS to 22.04.LTS, by build failed here:
>>> * package: info-6.8
>>>   last build time: Mar 20 09:39
>>>   log file:/usr/local/sage/sage-10.3/logs/pkgs/info-6.8.log
>>>   build directory: 
>>> /usr/local/sage/sage-10.3/local/var/tmp/sage/build/info-6.8
>>>
>>> I could not tell from the log (attached) just what the problem is -- any 
>>> suggestions?
>>>
>>
>> Just install texinfo - then this package should not be needed. Building 
>> (tex)info is tricky, as you see here...
>>
>
> Thanks Dima, you are very helpful as always.  I installed texinfo, forgot 
> to rerun ./configure, reran make, stuck at the same place, remebered to 
> rerun ./configure, and am continuing the build.  Luckily this machine has 
> 72 cores and since I only just did the system upgrade, no-one else is using 
> it!
>
> I don't always install all the packages suggested by ./configure since 
> sometimes I have more recent versions than are in ubuntu.  But that is not 
> relevant for texinfo (it can be for pari, flint, ntl, and of course eclib).
>
> John
>
>
>
>> (IMHO this should have never been made a standard Sage package - but 
>> rather Sage should require info from the OS, as it's literally available in 
>> every sane environment)
>>
>> Dima
>>  
>>
>>>
>>> John
>>>
>>> On Wed, 20 Mar 2024 at 05:03, Matthias Köppe  
>>> wrote:
>>>
>>>> Thanks a lot, Volker!
>>>>
>>>> Many thanks to all who contributed to this release, and welcome to all 
>>>> new contributors!
>>>>
>>>> It's not too late to expand our release notes: 
>>>> https://github.com/sagemath/sage/wiki/Sage-10.3-Release-Tour
>>>>
>>>> On Tuesday, March 19, 2024 at 5:36:30 PM UTC-7 Volker Braun wrote:
>>>>
>>>>> The "master" git branch has been updated to Sage-10.3. 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
>>>>>
>>>>> There was no change over 10.3.rc4
>>>>>
>>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "sage-release" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to sage-release...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/sage-release/dddbd588-b3fe-464d-8fb8-359fb5e2b33fn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/sage-release/dddbd588-b3fe-464d-8fb8-359fb5e2b33fn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-release" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-release...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-release/CAD0p0K4sbjS-3ojpYLjioMZU-ZYe2kM8wKBb4wNGoNiV2r8nsA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/sage-release/CAD0p0K4sbjS-3ojpYLjioMZU-ZYe2kM8wKBb4wNGoN

Re: [sage-release] Re: Sage 10.3 released

[Dima Pasechnik]

On Wed, Mar 20, 2024 at 9:53 AM John Cremona  wrote:

> Thanks for the new release.  On a ubuntu machine which I had literally
> only hust upgraded from 20.04 LTS to 22.04.LTS, by build failed here:
> * package: info-6.8
>   last build time: Mar 20 09:39
>   log file:/usr/local/sage/sage-10.3/logs/pkgs/info-6.8.log
>   build directory:
> /usr/local/sage/sage-10.3/local/var/tmp/sage/build/info-6.8
>
> I could not tell from the log (attached) just what the problem is -- any
> suggestions?
>

Just install texinfo - then this package should not be needed. Building
(tex)info is tricky, as you see here...

(IMHO this should have never been made a standard Sage package - but rather
Sage should require info from the OS, as it's literally available in every
sane environment)

Dima


>
> John
>
> On Wed, 20 Mar 2024 at 05:03, Matthias Köppe 
> wrote:
>
>> Thanks a lot, Volker!
>>
>> Many thanks to all who contributed to this release, and welcome to all
>> new contributors!
>>
>> It's not too late to expand our release notes:
>> https://github.com/sagemath/sage/wiki/Sage-10.3-Release-Tour
>>
>> On Tuesday, March 19, 2024 at 5:36:30 PM UTC-7 Volker Braun wrote:
>>
>>> The "master" git branch has been updated to Sage-10.3. 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
>>>
>>> There was no change over 10.3.rc4
>>>
>>> --
>> 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/dddbd588-b3fe-464d-8fb8-359fb5e2b33fn%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/CAD0p0K4sbjS-3ojpYLjioMZU-ZYe2kM8wKBb4wNGoNiV2r8nsA%40mail.gmail.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/CAAWYfq3JunSS8oy2e2hz429qShuaf%2B8sp2-rwCj0YzHD-HpK%3DA%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Mar 18, 2024 at 6:42 PM Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:

>
>
> Le lundi 18 mars 2024 à 15:26:41 UTC+1, Dima Pasechnik a écrit :
>
> Probably you got libprimesieve updated in your OS, you'd need to rebuild
> the corresponding parts of Sage.
>
>
> Indeed. Fortunately, `sudo apt install libprimesieve11` w enough to
> obtain a reassuring  `All tests passed` when re-running `ptestlong`.
>
> However, souldn't this dependency be tested by `./configure` ?
>

we don't test whether it works, we only test that it's present, and the
version is at least 8.0
It can be done, though.

Does anyone know where in saglib it is used?
It's a dependency of primecount, which is only consumed via python package
primecountpy.

Perhaps it can just be dropped as a dependency of sagelib?
(along with primecount)






>
> Thank you very much, Dima !
>
> On Mon, Mar 18, 2024 at 12:22 PM Emmanuel Charpentier 
> wrote:
>
> On Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.rc3 to
> 10.3.rc4 presents no problem. But the resulting installation fails *a lot*
> (56, if I counted them correctly) of ptestlong tests :
> --
> sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/dynamics/arithmetic_dynamics/projective_ds.py # 6 doctests failed
> sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720 src/sage/plot/plot.py
> # 2 doctests failed sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modform/element.py # 28 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/rings/number_field/number_field.py # 1 doctest failed sage -t
> --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/algebras/fusion_rings/f_matrix.py # 2 doctests failed sage -t
> --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/algebras/fusion_rings/fusion_ring.py # 4 doctests failed sage -t
> --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/modular/local_comp/local_comp.py # 1 doctest failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/groups/cubic_braid.py # 1 doctest failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/arith/misc.py # 1 doctest failed sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/modular/local_comp/type_space.py # 3 doctests failed sage -t
> --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/matrix/matrix2.pyx # 11 doctests failed sage -t --long --warn-long
> 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modform/cuspidal_submodule.py # 15 doctests failed sage -t
> --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modsym/ambient.py # 9 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/tests/book_stein_ent.py # 6 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/matrix/matrix_integer_dense.pyx # 6 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modform/constructor.py # 4 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/schemes/toric/sheaf/klyachko.py # 2 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modsym/space.py # 6 doctests failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modform/space.py # 1 doctest failed sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/interfaces/gp.py # Timed out after testing finished sage -t --long
> --warn-long 231.2 --random-seed=43747312386968059852741665308429742720
> src/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py # Timed out
> after testing finished sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/combinat/free_dendriform_algebra.py # Timed out after testing
> finished sage -t --long --warn-long 231.2
> --random-seed=43747312386968059852741665308429742720
> src/sage/modular/modform_hecketriangle/subspace.py # Timed out after
> testing finished sage -t --long --warn-long 2

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

[Dima Pasechnik]

Probably you got libprimesieve updated in your OS, you'd need to rebuild
the corresponding parts of Sage.

On Mon, Mar 18, 2024 at 12:22 PM Emmanuel Charpentier <
emm.charpent...@free.fr> wrote:

> On Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.rc3 to
> 10.3.rc4 presents no problem. But the resulting installation fails *a lot*
> (56, if I counted them correctly) of ptestlong tests :
>
> --
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/dynamics/arithmetic_dynamics/projective_ds.py  # 6 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 src/sage/plot/plot.py  # 
> 2 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modform/element.py  # 28 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/rings/number_field/number_field.py  # 1 doctest failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/algebras/fusion_rings/f_matrix.py  # 2 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/algebras/fusion_rings/fusion_ring.py  # 4 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/local_comp/local_comp.py  # 1 doctest failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/groups/cubic_braid.py  # 1 doctest failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 src/sage/arith/misc.py  
> # 1 doctest failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/local_comp/type_space.py  # 3 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/matrix/matrix2.pyx  # 11 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modform/cuspidal_submodule.py  # 15 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modsym/ambient.py  # 9 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/tests/book_stein_ent.py  # 6 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/matrix/matrix_integer_dense.pyx  # 6 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modform/constructor.py  # 4 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/schemes/toric/sheaf/klyachko.py  # 2 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modsym/space.py  # 6 doctests failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modform/space.py  # 1 doctest failed
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/interfaces/gp.py  # Timed out after testing finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py  # Timed out after 
> testing finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/combinat/free_dendriform_algebra.py  # Timed out after testing 
> finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/modular/modform_hecketriangle/subspace.py  # Timed out after testing 
> finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/graphs/hypergraph_generators.py  # Timed out after testing finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/repl/ipython_extension.py  # Timed out after testing finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/combinat/posets/moebius_algebra.py  # Timed out after testing 
> finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/combinat/species/generating_series.py  # Timed out after testing 
> finished
> sage -t --long --warn-long 231.2 
> --random-seed=43747312386968059852741665308429742720 
> src/sage/matrix/matrix_space.py  # 1 doctest failed
> sage -t --long --warn-long 231.2 
> 

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

[Dima Pasechnik]

On Mon, Mar 11, 2024 at 12:11 PM Enrique Artal 
wrote:

> In rc2 and Fedora 39, I had the same issue. With rc3 and Fedora 39, also,
> but with python 3.11, it is OK. May it be related to python 3.12 from
> system?
>

Are you on Python 3.12.2 ? Or an earlier release?


>  Enrique
> El miércoles, 6 de marzo de 2024 a las 13:02:02 UTC+1, jaap...@gmail.com
> escribió:
>
>> Operating System: Fedora Linux 39
>> Kernel Version: 6.7.3-200.fc39.x86_64 (64-bit)
>> Processors: 24 × 13th Gen Intel® Core™ i7-13700KF
>> Memory: 31,2 GiB of RAM
>>
>> make ptestlong
>> same error as expected:
>> --
>> sage -t --long --warn-long 29.6
>> --random-seed=230234824358800765306206065889005137096
>> src/sage/libs/gap/element.pyx  # Killed due to segmentation fault
>>
>> Jaap
>> --
>>
>> On Tue, Mar 5, 2024 at 7:08 PM Matthias Köppe 
>> wrote:
>>
>>> Thanks for the report!
>>> https://github.com/sagemath/sage/pull/37543 adds the missing dependency
>>> declaration.
>>>
>>> On Tuesday, March 5, 2024 at 1:10:30 AM UTC-8 furutaka@gmail.com
>>> wrote:
>>>
 On a PC running Fedora-39 (x86_64): failed in building
 "sagemath_doc_html-none",
 needed to do `./sage -i graphs` and then make again to finish building.

 Procedure:
 1. copy the git source.
 2. `make configure && ./configure && dnf install 
 && make reconfigure`.
 3. make -> stopped in building "sagemath_doc_html-none".
 4. `./sage -i graphs && make` to finish the build.

 Kazuyoshi


 2024年3月5日(火) 8:40 Volker Braun :

> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
>
> cb8e15b4769 (tag: 10.3.rc2, github/develop) Updated SageMath version
> to 10.3.rc2
> 872ca39ec42 gh-37504: `cmake`, `ninja_build`: Reject installations in
> inaccessible user schemes
> fc0d3399a69 gh-37495: build/pkgs/flint: Reject FLINT >= 3.1.0
> 4ac7152b170 (tag: 10.3.rc1) Updated SageMath version to 10.3.rc1
>
> --
> You received this message because you are subscribed to the Google
> Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/cc8e19ba-ee2a-49c9-b4c5-d3ed3b54e222n%40googlegroups.com
> 
> .
>


 --
 Kazuyoshi Furutaka

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-release" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-release...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-release/a55493b6-cc3c-49f5-9e8b-d26d5f09942cn%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/bdb34528-738f-4798-b4b3-509956c366cbn%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/CAAWYfq1pHjf6TsCBybPK_ird8F%3Dj5Aio-wt9XQtFfTvE%3DJXx6Q%40mail.gmail.com.

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

[Dima Pasechnik]

On Wed, Mar 6, 2024 at 12:02 PM Jaap Spies  wrote:

> Operating System: Fedora Linux 39
> Kernel Version: 6.7.3-200.fc39.x86_64 (64-bit)
> Processors: 24 × 13th Gen Intel® Core™ i7-13700KF
> Memory: 31,2 GiB of RAM
>
> make ptestlong
> same error as expected:
> --
> sage -t --long --warn-long 29.6
> --random-seed=230234824358800765306206065889005137096
> src/sage/libs/gap/element.pyx  # Killed due to segmentation fault
>

getting back to this error:
So running something like

./sage -tp 24 --long  --random-seed=230234824358800765306206065889005137096
src/sage/libs/gap/element.pyx

still leads to the segfault, right?

If so, could you add "print(rnd)" after "rnd = [...]" in the test in
question
and re-run the above command?

(The idea is to print the actual value of rnd that causes the segfault)

--- a/src/sage/libs/gap/element.pyx
+++ b/src/sage/libs/gap/element.pyx
@@ -2488,6 +2488,7 @@ cdef class GapElement_Function(GapElement):

 sage: for i in range(100):
 : rnd = [ randint(-10,10) for i in range(randint(0,7))
]
+: print(rnd)
 : # compute the sum in GAP
 : _ = libgap.Sum(rnd)
 : try:

It's most probably related to the fact that you're apparently using Python
3.12, installed on your OS,
to build and run sage (judging from libpython3.12.so mentioned in the log
you posted few days ago, for an earllier rc or beta).
I tried reproducing this by using a built from source Python 3.12 on Fedora
38, but all is good there.

Officially we still only support Python 3.11.
We have similar issues open:
https://github.com/sagemath/sage/issues/37026
https://github.com/sagemath/sage/issues/37289

Dima


> Jaap
> --
>
> On Tue, Mar 5, 2024 at 7:08 PM Matthias Köppe 
> wrote:
>
>> Thanks for the report!
>> https://github.com/sagemath/sage/pull/37543 adds the missing dependency
>> declaration.
>>
>> On Tuesday, March 5, 2024 at 1:10:30 AM UTC-8 furutaka@gmail.com
>> wrote:
>>
>>> On a PC running Fedora-39 (x86_64): failed in building
>>> "sagemath_doc_html-none",
>>> needed to do `./sage -i graphs` and then make again to finish building.
>>>
>>> Procedure:
>>> 1. copy the git source.
>>> 2. `make configure && ./configure && dnf install  &&
>>> make reconfigure`.
>>> 3. make -> stopped in building "sagemath_doc_html-none".
>>> 4. `./sage -i graphs && make` to finish the build.
>>>
>>> Kazuyoshi
>>>
>>>
>>> 2024年3月5日(火) 8:40 Volker Braun :
>>>
 As always, you can get the latest beta version from the "develop" git
 branch. Alternatively, the self-contained source tarball is at
 http://www.sagemath.org/download-latest.html


 cb8e15b4769 (tag: 10.3.rc2, github/develop) Updated SageMath version to
 10.3.rc2
 872ca39ec42 gh-37504: `cmake`, `ninja_build`: Reject installations in
 inaccessible user schemes
 fc0d3399a69 gh-37495: build/pkgs/flint: Reject FLINT >= 3.1.0
 4ac7152b170 (tag: 10.3.rc1) Updated SageMath version to 10.3.rc1

 --
 You received this message because you are subscribed to the Google
 Groups "sage-release" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to sage-release...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-release/cc8e19ba-ee2a-49c9-b4c5-d3ed3b54e222n%40googlegroups.com
 
 .

>>>
>>>
>>> --
>>> Kazuyoshi Furutaka
>>>
>> --
>> 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/a55493b6-cc3c-49f5-9e8b-d26d5f09942cn%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/CAK0%3DbK11NHhRuiXrBkJ%2BiOgXFAbbFRWYmLJQJ70TT5Tgmye3-A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop 

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

[Dima Pasechnik]

Goedemiddag Jaap,

would you be so kind to look at logs/tests.log and see where exactly the
crash occurs (lines before the crash are printed, so it can be put down to
the exact place it).
And post the relevant lines of logs/tests.log here.

Dima



On Tue, Feb 27, 2024 at 11:02 AM Jaap Spies  wrote:

> Operating System: Fedora Linux 39
>
> Kernel Version: 6.7.3-200.fc39.x86_64 (64-bit)
>
> Processors: 24 × 13th Gen Intel® Core™ i7-13700KF
> Memory: 31,2 GiB of RAM
>
> Same persistent error:
> Unhandled SIGSEGV: A segmentation fault occurred.
> This probably occurred because a *compiled* module has a bug
> in it and is not properly wrapped with sig_on(), sig_off().
> Python will now terminate.
> 
>
> **
> --
> sage -t --long --warn-long 30.7
> --random-seed=154226370660111014259536820846081862386
> src/sage/libs/gap/element.pyx  # Killed due to segmentation fault
>
> Jaap Spies
>
> On Mon, Feb 26, 2024 at 11:09 PM Emmanuel Charpentier <
> emanuel.charpent...@gmail.com> wrote:
>
>> Thanks a lot ! I'll have to ((re-)^n)read the Developer's Guide and the
>> Installation Guide...
>>
>> Le lundi 26 février 2024 à 21:44:27 UTC+1, matthia...@gmail.com a écrit :
>>
>> On Monday, February 26, 2024 at 12:26:04 PM UTC-8 emanuel.c...@gmail.com
>> wrote:
>>
>> Question : how to modify Sage’s configuration (as used by make
>> reconfigure) without having to re-state *all* the configuration ?
>>
>> eval ./configure $(./config.status --config) --without-system-brial
>>
>> --
>> 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/744757ca-0e2d-4e55-9ac8-ee01672b6889n%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/CAK0%3DbK3-vXM764ri439U5sfBxWob7VUF8YznRuU7wqE2ZNgtqg%40mail.gmail.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/CAAWYfq1_Ks-_bNda%3Dt-P8TGb3iUjsaR6RzVOdVYPUPyZGxFHWA%40mail.gmail.com.

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

[Dima Pasechnik]

On 15 February 2024 09:17:00 GMT, Kazuyoshi Furutaka 
 wrote:
>Hi,
>
>I've tried to build 10.3-beta8 on two Fedora-39 machines, one at home (AMD
>Ryzen 7 Cezanne) and the other at work (Intel Sandy Bridge(Core i7)).
>The build on the former was successful w/o any problem,  but failed on
>the latter (and it was also the case for 10.3-beta7).
>
>1. Failure in building scipy-1.11.4: needed to set "MKL_ENABLE_INSTRUCTIONS=
>SSE4_2" (the log was attached).
>c.f.
>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/CPU-Deprecation-Warning/m-p/1550243?profile.language=ja
>
>2. Failure in building sagemath_doc_html-none: needed to do `./sage -i
>graphs` (the log when building 10.3-beta7 was attached).
>After issuing the command to avoid the problem for 10.3-beta7, I have to do
>it again for 10.3-beta8.

Are you using Intel MKL is this build, rather than OpeBLAS?

Or it's only scipy that uses MKL ?

>
>Kazuyoshi
>
>
>
>
>2024年2月14日(水) 8:40 Volker Braun :
>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> We should soon start with a release candidate, so if you have any ticket
>> that you really want to get merged then now is the time to get it in!
>>
>>
>> 30b3d78fac8 (origin/develop, tag: 10.3.beta8) Updated SageMath version to
>> 10.3.beta8
>> 81a374dc4da gh-37290: sagemath-standard: don't require Cython to create
>> sdist
>> f71381c36f1 gh-37279: Fix some doctest warnings
>> 36bf4afd280 gh-37272: enable the generation of acyclic orientations with
>> `nauty_directg`
>> 75afadb1669 gh-37270: Allow python 3.12 and scipy 1.12
>> d3deb285e50 gh-37269: sage_docbuild: add needs sphinx tags
>> 5f9ac40378b gh-37258: add type annotations to gens methods
>> df5e77e5bf5 gh-37256: general cleanup of words/paths.py
>> 2fd33b964b0 gh-37252: CI: Fix for failure in maximize-build-space
>> 1cd7585c3c2 gh-37246: minor details in modular
>> 1ac73d8adca gh-37245: a few details in combinat folder
>> 46ef3fd7ac4 gh-37240: add one method to integer-valued polynomials
>> b33cb7515ae gh-37234: make a category of Dedekind domains, remove code
>> from ring.pyx
>> 4f78a5f3012 gh-37233: fix small mistake in BQFClassGroupQuotientMorphism
>> documentation
>> cd61411b653 gh-37232: Still less use of isinstance of old-parents
>> 3d38254edba gh-37230: some cython-lint fixes in ecl lib
>> 1b02deb7f03 gh-37229: some pep8 fixes in coding, in particular E275
>> 6b3e7642126 gh-37228: some pep8 fixes in rings, and activate E221
>> 705cab1188f gh-37226: unit group of number field: do not expand product
>> when S is empty
>> 76b1a92acd3 gh-37225: splitting_field: polred -> polredbest
>> cdd42d4af9a gh-37223: Remove invariants commands in global namespace
>> 9e9acfea423 gh-37222: CI Linux Incremental: Do not require label "c:
>> packages: ..." to be set
>> 81a23e1d96d gh-37218: Fix to ncsym.ncsym.nesting
>> 23586cf4085 gh-37215: Remove unnecessary bullet point
>> 15abc09a456 gh-37210: unify alias substitute for subs
>> d548c0023f7 gh-37209: Added rational Tamari lattices
>> bf1c793ecd6 gh-37207: allow algorithm=pari in LLL
>> f396146fe81 gh-37199: make FreeAlgebra graded and provide is_unit and
>> __invert__
>> d1bbb83ef3f gh-37195: general LU: gather several calls to field inversion
>> into a single call
>> adee77d9f49 gh-37193: Some fixes & improvements to autogenerated flint .pxd
>> 0319fbba80f gh-37185: Fix `sage_setup.clean` doctest
>> 43686380ed7 gh-37182: Implement Auslander-Reiten quivers
>> 7c0a5ecd0cb gh-37170: Total refactor of `any_root()` to solve issue in
>> characteristic two and clean up the code
>> 49505110153 gh-37148: Add class CircuitsMatroid
>> dd9abe40439 gh-37143: special subs for fractions
>> 53c3468f59a gh-37113: Define behaviour of < and > for fractional ideals in
>> a quaternion algebra
>> 138b265e5ad gh-37096: Fix `.multiplication_by_m` when m is not coprime to
>> characteristic (#6413)
>> ed119f6d025 gh-37073: `build/pkgs/free_fonts`: Fix fedora system package
>> information
>> 60ffcefe9ac gh-37065: Installation guide: Use `.. envvar::` to define
>> environment variables
>> 96cb4849aa9 gh-37014: Upgrade database_knotinfo to version 2024.2.1
>> fe375288d78 gh-37007: normalize projective points over (quotients of)
>> Euclidean domains
>> d4b28e18831 gh-36997: `build/pkgs/{givaro,fflas_ffpack,linbox}`: Accept
>> matching set of new versions
>> 647ec811c57 gh-36983: Prepare python3 `spkg-configure.m4` for Python 3.12
>> (setuptools instead of distutils)
>> 20a6fde8fa0 gh-36927: src/sage/combinat/designs/subhypergraph_search.pyx:
>> constness fix for clang 16
>> 3942b62a2f0 gh-36915: `configure.ac`: Remove tests for outdated platforms
>> 6ad8584b4d6 gh-36881: Fix cardinality of special linear group
>> bbe70e7a14e gh-36805: fast path for Vélu isogenies with a single kernel
>> generator
>> 5a3f8eb0af3 gh-36171: Implement Chevalley-Eilenberg complexes with module
>> coefficients

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

[Dima Pasechnik]

On Wed, Jan 24, 2024 at 4:53 AM Clemens Heuberger
 wrote:
>
> On one machine, I encountered persistent doctest errors with a specific 
> random seed:
>
> sage -t --long --warn-long 51.5
> --random-seed=218399045362864612956198671406486371465 src/sage/plot/plot.py  
> # 1
> doctest failed
> sage -t --long --warn-long 51.5
> --random-seed=218399045362864612956198671406486371465
> src/sage/schemes/elliptic_curves/ell_field.py  # 2 doctests failed
>
> With another random seed, tests passed.

the 2nd might be the one reported in
https://github.com/sagemath/sage/issues/36832



>
> Log is attached.
>
>
>
> Am 22.01.24 um 01:23 schrieb Volker Braun:
> > As always, you can get the latest beta version from the "develop" git 
> > branch.
> > Alternatively, the self-contained source tarball is at
> > http://www.sagemath.org/download-latest.html
> >
> > 3dd953c3aa6 (tag: 10.3.beta6, github/develop) Updated SageMath version to 
> > 10.3.beta6
> > ...
>
> --
> 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/0a7205e5-e856-4f11-8af4-0624d45243ac%40aau.at.

-- 
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/CAAWYfq04qSxFfNSBVFpLG-t5XTqy0Z8t5-FdhrJTKYYTuP1mZQ%40mail.gmail.com.

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

[Dima Pasechnik]

On Thursday, December 14, 2023 at 4:05:31 PM UTC John H Palmieri wrote:

On OS X (both Intel and Apple Silicon) I'm getting a lot of new failures, 
many of the form "Killed due to alarm":

sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/libs/flint/nmod_poly_linkage.pxi  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/data_structures/bounded_integer_sequences.pyx  # Killed due to 
alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/libs/gap/element.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/interfaces/gap.py  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/geometry/integral_points.pxi  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/libs/libecm.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/coding/linear_code.py  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/factorint_pari.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/integer.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/complex_arb.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/parallel/decorate.py  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/polynomial/polynomial_element.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/polynomial/polynomial_zmod_flint.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/sets/recursively_enumerated_set.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/structure/coerce_actions.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/matrix/matrix_integer_dense.pyx  # Killed due to alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx  # Killed due to 
alarm
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/doctest/forker.py  # 5 doctests failed
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/doctest/control.py  # 8 doctests failed

Plus some doctests that have been failing for a while:

sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/rings/polynomial/multi_polynomial_ideal.py  # Killed due to 
segmentation fault
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/libs/giac/__init__.py  # Timed out
sage -t --long --random-seed=144845266083009760424007645487960076680 
src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py 
 # 1 doctest failed


yes, I  also see quite a few # Killed due to alarm on Apple M1 Studio box 
(hosted by William).
This is with quite a few Homebrew packages.

However, it's a Heisenbug: running these tests separately works.

Darwin studio.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 
21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64
--
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/libs/flint/nmod_poly_linkage.pxi  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/libs/gap/element.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/libs/libecm.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/geometry/integral_points.pxi  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/rings/factorint_pari.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/rings/complex_arb.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/coding/linear_code.py  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/rings/polynomial/polynomial_element.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/sets/recursively_enumerated_set.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/structure/coerce_actions.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 
src/sage/rings/integer.pyx  # Killed due to alarm
sage -t --random-seed=216456570840224251681732656912784587240 

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

[Dima Pasechnik]

On Sat, Dec 9, 2023 at 7:39 PM Dima Pasechnik  wrote:
>
> On Sat, Dec 9, 2023 at 5:41 PM David Coudert  wrote:
> >
> > I will ask for an upgrade of the desktop to a newer Fedora (may be 39) and 
> > see if this solves the issue.
>
> On Fedora 3.8 I don't see these, ./sage runs without any issues like this.
> However, I get lots of
> [sagemath_doc_html-none] [a_tour_of] Extension error:
> [sagemath_doc_html-none] [a_tour_of] Could not import extension
> IPython.sphinxext.ipython_directive (exception: No module named
> 'IPython.sphinxext')
>
> during docbuild (in most modules, not only in [a_tour_of] )
>
> Strangely they don't lead to docbuild erroring out.
>
> I ran ./configure --enable-system-site-packages
> so some Python packages come from the system.

It was ipython 8.9 on the system, too old, apparently.

./sage --pip install ipython

installed ipython 8.18.1, which fixed this issue. So in
ipython/spkg-configure.m4 one needs to add a check that
IPython.sphinxext.ipython_directive is available.



>
>
>
> > Thanks.
> > David.
> >
> > Le 9 déc. 2023 à 18:25, Dima Pasechnik  a écrit :
> >
> > On Sat, Dec 9, 2023 at 4:52 PM David Coudert  
> > wrote:
> >
> >
> > Hello,
> >
> > I have a surprising and annoying issue on Fedora 35 with 10.3.beta0 after
> > make distclean sagelib-clean
> > make build
> > ./sage -i bliss tdlib benzene buckygen cryptominisat dot2tex glucose 
> > gap_packages mcqd plantri  csdp python_igraph
> >
> > When I start sage in a console, I see some warnings:
> >
> > gelati:/home/dcoudert/sage> ./sage
> > ┌┐
> > │ SageMath version 10.3.beta0, Release Date: 2023-12-05  │
> > │ Using Python 3.10.8. Type "help()" for help.   │
> > └┘
> > ┏┓
> > ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> > ┗┛
> > /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
> >  DeprecationWarning: There is no current event loop
> >  loop = asyncio.get_event_loop()
> >
> >
> > I presume your  Python comes from the OS.
> > It seems to be an upstream issue with prompt_toolkit:
> > https://github.com/prompt-toolkit/python-prompt-toolkit/pull/1714
> > It says that they have a workaround for Python 3.10.9+, but you're on
> > 3.10.8. Either they missed this, or I don't know. Can you install a
> > newer Python ?
> >
> > Fedora 35 is past EOL for over a year, can you move to 37 (36 is past
> > EOL too) or even newer?
> >
> >
> > sage: G = graphs.PetersenGraph()
> > /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
> >  DeprecationWarning: There is no current event loop
> >  loop = asyncio.get_event_loop()
> > sage: G
> > Petersen graph: Graph on 10 vertices
> > /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
> >  DeprecationWarning: There is no current event loop
> >  loop = asyncio.get_event_loop()
> > sage:
> >
> >
> > However, these warnings are not interfering with doctests. Running for 
> > instance `./sage -t src/sage/graphs/` works fine.
> >
> > Anyway help to avoid these warnings is more than welcome.
> >
> > Best,
> > David.
> >
> >
> >
> > Le 6 déc. 2023 à 20:37, John H Palmieri  a écrit :
> >
> > Builds fine for me on OS X, both Intel and Apple Silicon. No new doctest 
> > failures.
> >
> > On Tuesday, December 5, 2023 at 4:26:09 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
> >
> > 272582be9e0 (github/develop, tag: 10.3.beta0) Updated SageMath version to 
> > 10.3.beta0
> > 9b1e18ffc02  gh-36664: ruff auto-fix for C4 in modular
> > 3253ed95cdb gh-36658: `sage.sat`: Update `# needs`
> > b707b299324 gh-36657: `sage.tests`: Update `# needs`
> > 34b6321efb2 gh-36655: `sage.misc.explain_pickle`: Docstring cosmetics
> > c9e28a84924 gh-36654: More fixes for e221
> > 0394ea

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

[Dima Pasechnik]

On Sat, Dec 9, 2023 at 5:41 PM David Coudert  wrote:
>
> I will ask for an upgrade of the desktop to a newer Fedora (may be 39) and 
> see if this solves the issue.

On Fedora 3.8 I don't see these, ./sage runs without any issues like this.
However, I get lots of
[sagemath_doc_html-none] [a_tour_of] Extension error:
[sagemath_doc_html-none] [a_tour_of] Could not import extension
IPython.sphinxext.ipython_directive (exception: No module named
'IPython.sphinxext')

during docbuild (in most modules, not only in [a_tour_of] )

Strangely they don't lead to docbuild erroring out.

I ran ./configure --enable-system-site-packages
so some Python packages come from the system.



> Thanks.
> David.
>
> Le 9 déc. 2023 à 18:25, Dima Pasechnik  a écrit :
>
> On Sat, Dec 9, 2023 at 4:52 PM David Coudert  wrote:
>
>
> Hello,
>
> I have a surprising and annoying issue on Fedora 35 with 10.3.beta0 after
> make distclean sagelib-clean
> make build
> ./sage -i bliss tdlib benzene buckygen cryptominisat dot2tex glucose 
> gap_packages mcqd plantri  csdp python_igraph
>
> When I start sage in a console, I see some warnings:
>
> gelati:/home/dcoudert/sage> ./sage
> ┌┐
> │ SageMath version 10.3.beta0, Release Date: 2023-12-05  │
> │ Using Python 3.10.8. Type "help()" for help.   │
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>  loop = asyncio.get_event_loop()
>
>
> I presume your  Python comes from the OS.
> It seems to be an upstream issue with prompt_toolkit:
> https://github.com/prompt-toolkit/python-prompt-toolkit/pull/1714
> It says that they have a workaround for Python 3.10.9+, but you're on
> 3.10.8. Either they missed this, or I don't know. Can you install a
> newer Python ?
>
> Fedora 35 is past EOL for over a year, can you move to 37 (36 is past
> EOL too) or even newer?
>
>
> sage: G = graphs.PetersenGraph()
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>  loop = asyncio.get_event_loop()
> sage: G
> Petersen graph: Graph on 10 vertices
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>  loop = asyncio.get_event_loop()
> sage:
>
>
> However, these warnings are not interfering with doctests. Running for 
> instance `./sage -t src/sage/graphs/` works fine.
>
> Anyway help to avoid these warnings is more than welcome.
>
> Best,
> David.
>
>
>
> Le 6 déc. 2023 à 20:37, John H Palmieri  a écrit :
>
> Builds fine for me on OS X, both Intel and Apple Silicon. No new doctest 
> failures.
>
> On Tuesday, December 5, 2023 at 4:26:09 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
>
> 272582be9e0 (github/develop, tag: 10.3.beta0) Updated SageMath version to 
> 10.3.beta0
> 9b1e18ffc02  gh-36664: ruff auto-fix for C4 in modular
> 3253ed95cdb gh-36658: `sage.sat`: Update `# needs`
> b707b299324 gh-36657: `sage.tests`: Update `# needs`
> 34b6321efb2 gh-36655: `sage.misc.explain_pickle`: Docstring cosmetics
> c9e28a84924 gh-36654: More fixes for e221
> 0394ea33387 gh-36653: clean E702 etc in integer.pyx
> bf801b1edfb gh-36644: `sage.combinat.words`: Update `# needs`
> 5a22cce2510 gh-36643: `sage.combinat.species`: Update `# needs`
> 91c9fa67907 gh-36642: `sage.algebras`: Update `# needs`, modularization 
> fixes, doctest cosmetics
> ef9b2792302 gh-36638: return Weierstrass scaling factor in base field for 
> EllipticCurveIsogeny
> 2b9f3e0e4ff gh-36637: sums of elliptic-curve morphisms
> 3a9254d73ae gh-36630: Allow to specify output directory for generated 
> interpreters
> 69d03d36651 gh-36623: cylint cleanup in combinatorial polyhedra
> 7b3e208631f gh-36597: Replace relative imports by absolute ones in modules
> 779a502cd5e gh-36592: Add pull_from_function_field to curves
> 54dbcbf46a6 gh-36589: Replace relative imports by absolute ones i

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

[Dima Pasechnik]

On Sat, Dec 9, 2023 at 4:52 PM David Coudert  wrote:
>
> Hello,
>
> I have a surprising and annoying issue on Fedora 35 with 10.3.beta0 after
> make distclean sagelib-clean
> make build
> ./sage -i bliss tdlib benzene buckygen cryptominisat dot2tex glucose 
> gap_packages mcqd plantri  csdp python_igraph
>
> When I start sage in a console, I see some warnings:
>
> gelati:/home/dcoudert/sage> ./sage
> ┌┐
> │ SageMath version 10.3.beta0, Release Date: 2023-12-05  │
> │ Using Python 3.10.8. Type "help()" for help.   │
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>   loop = asyncio.get_event_loop()

I presume your  Python comes from the OS.
It seems to be an upstream issue with prompt_toolkit:
https://github.com/prompt-toolkit/python-prompt-toolkit/pull/1714
It says that they have a workaround for Python 3.10.9+, but you're on
3.10.8. Either they missed this, or I don't know. Can you install a
newer Python ?

Fedora 35 is past EOL for over a year, can you move to 37 (36 is past
EOL too) or even newer?


> sage: G = graphs.PetersenGraph()
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>   loop = asyncio.get_event_loop()
> sage: G
> Petersen graph: Graph on 10 vertices
> /home/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib64/python3.10/site-packages/prompt_toolkit/application/application.py:988:
>  DeprecationWarning: There is no current event loop
>   loop = asyncio.get_event_loop()
> sage:
>
>
> However, these warnings are not interfering with doctests. Running for 
> instance `./sage -t src/sage/graphs/` works fine.
>
> Anyway help to avoid these warnings is more than welcome.
>
> Best,
> David.
>
>
>
> Le 6 déc. 2023 à 20:37, John H Palmieri  a écrit :
>
> Builds fine for me on OS X, both Intel and Apple Silicon. No new doctest 
> failures.
>
> On Tuesday, December 5, 2023 at 4:26:09 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
>>
>> 272582be9e0 (github/develop, tag: 10.3.beta0) Updated SageMath version to 
>> 10.3.beta0
>> 9b1e18ffc02  gh-36664: ruff auto-fix for C4 in modular
>> 3253ed95cdb gh-36658: `sage.sat`: Update `# needs`
>> b707b299324 gh-36657: `sage.tests`: Update `# needs`
>> 34b6321efb2 gh-36655: `sage.misc.explain_pickle`: Docstring cosmetics
>> c9e28a84924 gh-36654: More fixes for e221
>> 0394ea33387 gh-36653: clean E702 etc in integer.pyx
>> bf801b1edfb gh-36644: `sage.combinat.words`: Update `# needs`
>> 5a22cce2510 gh-36643: `sage.combinat.species`: Update `# needs`
>> 91c9fa67907 gh-36642: `sage.algebras`: Update `# needs`, modularization 
>> fixes, doctest cosmetics
>> ef9b2792302 gh-36638: return Weierstrass scaling factor in base field for 
>> EllipticCurveIsogeny
>> 2b9f3e0e4ff gh-36637: sums of elliptic-curve morphisms
>> 3a9254d73ae gh-36630: Allow to specify output directory for generated 
>> interpreters
>> 69d03d36651 gh-36623: cylint cleanup in combinatorial polyhedra
>> 7b3e208631f gh-36597: Replace relative imports by absolute ones in modules
>> 779a502cd5e gh-36592: Add pull_from_function_field to curves
>> 54dbcbf46a6 gh-36589: Replace relative imports by absolute ones in a few 
>> packages
>> 671f7d56ba0 gh-36588: Replace relative imports by absolute ones in rings
>> caa10685ff2 gh-36584: implemented power of graph function under basic methods
>> 8801f6e24cd gh-36574: rename the backtrack algorithm of method 
>> `longest_path` with deprecation
>> 9014410efb7 gh-36572: Replace relative imports by absolute ones in categories
>> e86721e0b97 gh-36562: `pkgs/sage-{docbuild,setup,sws2rst}`: Migrate from 
>> `setup.cfg` to `pyproject.toml`
>> d67dba4740c gh-36505: `sage --tox -e coverage.py`
>> a5107c61cf4 gh-36504: Functions for nice tree decomposition and its labelling
>> 8bcebb19169 gh-36457: check coprimality of moduli in CRT_basis()
>> a6f2c461733 gh-36368: Laurent polynomials, Fitting ideals and characteristic 
>> varieties
>> d2b457895c4 gh-36223: src/sage/doctest/control.py: double the default test 
>> timeout
>> fb7ef07389d gh-36190: establish interface for instantiated classical modular 
>> polynomials
>> 839327af1f2 gh-36184: add class groups of binary quadratic forms
>> c1a38172852 gh-36135: `sage -fixdistributions`
>> 

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

[Dima Pasechnik]

On Thu, 16 Nov 2023, 01:40 Matthias Köppe,  wrote:

> Which package, Dima?
>
sorry, wrong thread

>
> On Wednesday, November 15, 2023 at 4:45:29 PM UTC-8 Dima Pasechnik wrote:
>
>> This package produces incorrect maths results, it has to be demoted to
>> experimental, IMHO.
>>
>>
>> On 15 November 2023 22:37:30 GMT, "Matthias Köppe" 
>> wrote:
>>
>>> On Tuesday, November 14, 2023 at 3:13:46 PM UTC-8 Volker Braun wrote:
>>>
>>> fa5c9395d3e (tag: 10.2.rc3, github/develop) Updated SageMath version to
>>> 10.2.rc3
>>>
>>>
>>> Thanks, Volker, for the latest rc. I think we're in pretty good shape
>>> now, but I think we need one more round for the following:
>>> - https://github.com/sagemath/sage/pull/36722 (openblas upgrade,
>>> appears to fix build failures on archlinux-latest and fedora-38; needs
>>> review)
>>>
>>> I would also like to get the following PR in:
>>> - https://github.com/sagemath/sage/pull/36031
>>> (LatticePolytope.normal_form fixes; needs review)
>>>
>>>
>>> --
> 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/1136a803-7a38-433f-b9ea-b7d57a939b42n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-release/1136a803-7a38-433f-b9ea-b7d57a939b42n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAAWYfq1bYVHi1AHvBepLO2k%3D1G8F9ahJnDBo8%2BhpLXJgVGbnVQ%40mail.gmail.com.

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

[Dima Pasechnik]

This package produces incorrect maths results, it has to be demoted to 
experimental, IMHO.


On 15 November 2023 22:37:30 GMT, "Matthias Köppe"  
wrote:
>On Tuesday, November 14, 2023 at 3:13:46 PM UTC-8 Volker Braun wrote:
>
>fa5c9395d3e (tag: 10.2.rc3, github/develop) Updated SageMath version to 
>10.2.rc3
>
>
>Thanks, Volker, for the latest rc. I think we're in pretty good shape now, 
>but I think we need one more round for the following:
>- https://github.com/sagemath/sage/pull/36722 (openblas upgrade, appears to 
>fix build failures on archlinux-latest and fedora-38; needs review)
>
>I would also like to get the following PR in:
>- https://github.com/sagemath/sage/pull/36031 (LatticePolytope.normal_form 
>fixes; needs review)
>
>
>-- 
>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/dafffaa8-de83-4d60-9d6a-5b6d124d8c7an%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/D989B784-B5B0-469C-BEE6-A48E96C04034%40gmail.com.

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

[Dima Pasechnik]

On Wed, Nov 15, 2023 at 5:12 PM John Cremona  wrote:
>
> I am seeing failures building from rc3 (commit fa5c9395d3).  To make sure
I made a fresh git clone of this and did nothing more than
>
> ./bootstrap
> ./configure
>  make -j16
>
> On thre machines, make build worked OK, but not make: it is
sagemath_doc_html-none which fails.  The short logfile is attached.  It's a
problem with libntl linking: it wants libntl.so.44 .   In configure, Sage
did decide that it was OK to use a system NTL.  I have two (which may be
the problem):  in /usr and in /usrlocal.  the relevant library files are
/usr/lib/x86_64-linux-gnu/libntl.so -> libntl.so.43.0.1 and
/usr/local/lib/libntl.so -> libntl.so.44.0.1.   From the error message in
the attached log it could not find libntl.so.44 but it exists in
/usr/local/lib and has the correct permissions.

This setup is asking for trouble. We don't have a fine-tune way to deal
with such cases.
Consider this a bug.
Basically,  ./configure sees libntl available and good enough, but goes
with whatever default ordering of libraries' locations it has.

Then the linker, possibly using another ordering, tries to resolve -lntl...




>
> On two of the three machines I ran "make" again and that resulted in
crashing python -- you can see the traceback file if you want, it ends with
>
> No symbol table info available.
> >>>
> [Inferior 1 (process 3558942) detached]
> 27  ../sysdeps/unix/sysv/linux/wait4.c: No such file or directory.
> Traceback (most recent call last):
>   File "", line 25, in 
> ModuleNotFoundError: No module named 'Cython'
> Error while executing Python code.
> Saved trace to /home/jec/.sage/crash_logs/crash_y7tokr_q.log
> 
> Unhandled SIGABRT: An abort() occurred.
> This probably occurred because a *compiled* module has a bug
> in it and is not properly wrapped with sig_on(), sig_off().
> Python will now terminate.
> 
> Aborted (core dumped)
> make[6]: *** [Makefile:28: doc-inventory--reference-combinat] Error 134
> make[5]: *** [Makefile:45: doc-inventory-reference] Error 2
>
> On Wed, 15 Nov 2023 at 16:05, Matthias Köppe 
wrote:
>>
>> You may have to force-pull the release tags:
>>
>> git fetch --tags -f upstream
>>
>>
>> On Wednesday, November 15, 2023 at 1:51:07 AM UTC-8 John Cremona wrote:
>>
>> Is it expected that doing "git pull upstream develop" on top of the rc1
commit should be a merge?
>>
>> On Tue, 14 Nov 2023 at 23:13, 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
>>
>>
>> fa5c9395d3e (tag: 10.2.rc3, github/develop) Updated SageMath version to
10.2.rc3
>> 705a0ee9bf3 gh-36711: CI macOS: Build following stages even when some
job failed; adjust platforms
>> 7f6a2a7e6a8 gh-36708: CI Linux: Fixes for tests of optional packages
>> dccb4127165 gh-36707: `build/pkgs/nauty`: Handle `SAGE_FAT_BINARY`
>> 82a3102d058 gh-36699: CI Linux: Follow-up fix for conda-forge-python3.11
>> 4d2dd497f5f gh-36696: Fix SSL timeout in doctest / internet feature
>> 613775f17bd gh-36692: Make doc-pdf separate from doc-html
>> 606c816a9d9 gh-36670: .github/workflows/docker.yml: Interrupt the build
before the 6 hour cancellation
>> 9953321a2d2 gh-36660: .github/workflows/ci-linux.yml: Fine-tune
max-parallel
>> 4430e4cc37c (tag: 10.2.rc2) Updated SageMath version to 10.2.rc2
>>
>> --
>> You received this message because you are subscribed to the Google
Groups "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send
an email to sage-release...@googlegroups.com.
>> To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-release/8593234a-b974-40f0-be55-8ec14c975231n%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/db4ffd07-b437-4d4c-bf79-3f4f7928a084n%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/CAD0p0K6587td__1MvJFHv3a9GH9hJLfR3jvg63NSYMhDyBKBLA%40mail.gmail.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 

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

[Dima Pasechnik]

On Mon, Nov 13, 2023 at 1:30 PM David Coudert  wrote:

> Yesterday I have synchronized my fork on GitHub with 10.2.rc2 and it went 
> well, but today I see that « This branch is 1 commit ahead, 1 commit behind 
> sagemath:develop » O_o. See  https://github.com/dcoudert/sage/
> It seems that I have to resolve that manually, but I’m not sure how.

suppose you're on your branch, and origin/develop is the current
develop branch (rc2), already "git fetch"'ed.
Then run

   git rebase origin/develop

and hopefully it will go automatically

(you can always do "git rebase --abort" if something goes wrong)

Often you'd see
CONFLICT... (in such and such file); so you edit this file and "git
add" it (and same for all the conflicts you see)
and type

   git rebase --continue

Use "git status" to see where you are in the rebase process.

HTH
Dima




>
> I also see that one of my PR has conflicts that must be resolved, certainly 
> due to forced push (https://github.com/sagemath/sage/pull/36705). I will 
> check that when I will be able to properly synchronize my own fork of the 
> develop branch.
>
> Best,
> David.
>
>
> Le 13 nov. 2023 à 09:52, Eric Gourgoulhon  a écrit :
>
> Thank you for having merged https://github.com/sagemath/sage/pull/36529 !
>
> Eric.
>
>
> Le dimanche 12 novembre 2023 à 22:42:41 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
>>
>>
>> 4430e4cc37c (tag: 10.2.rc2, github/develop) Updated SageMath version to 
>> 10.2.rc2
>> 883e05f8ee0 gh-36698: src/sage/combinat/root_system/coxeter_group.py: Fix 
>> typo in lazy_import
>> a0872bed5c9 gh-36671: build/pkgs/openblas: Stop openblas from using explicit 
>> `make -j N`; but use `make -j 1` on `ubuntu-trusty`
>> 405e166238e gh-36669: Sage knows Hadamard matrices <1201, not 1001
>> bb7cf9b7c64 gh-36529: src/sage/misc/latex.py: fix view()
>> e349b002499 (tag: 10.2.rc1) Updated SageMath version to 10.2.rc1
>
>
> --
> 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/c2a87e5a-5645-439a-99b5-88a0c5661862n%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/26D5FF0E-52FF-4D16-B34D-9EF3B0E41454%40gmail.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/CAAWYfq2GDtnePYrL%3DxL_cJACuujYicoCVH9eM3NUymDUKXqodA%40mail.gmail.com.

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

[Dima Pasechnik]

Hi Volker,

could you please merge https://github.com/sagemath/sage/pull/36669 ?
It's just documentation (and promoting work of my student)

Dima

On Fri, Nov 10, 2023 at 7:18 PM 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
>
> I just corrected a mistake, so if your head commit is not e349b002499 then 
> please reset.
>
> e349b002499  (tag: 10.2.rc1, github/develop) Updated SageMath version to 
> 10.2.rc1
> 81bf4e52c66 gh-36668: CI Linux: Fix "optional", "experimental" jobs
> dfde868e2f2 gh-36663: Upgrade `zeromq` to 4.3.5, `pyzmq` to 25.1.1, patch out 
> broken tests in setup
> 7cad4fc0026 gh-36661: .github/workflows/doc-build.yml: Fix live doc building
> 781dbff5cb4 gh-36659: prompt_toolkit: Set version constraint for conda
> a88fe91eae2 gh-36652: src/sage/misc/sageinspect.py: Fix pycodestyle complaint
> 9d2750c52bd gh-36648: CI macOS: Update
> 07ea7e18328 gh-36636: Deploy live doc on push to develop
> 88984731816 gh-36599: sage-env: identify the version of command-line tools 
> (OS X) and set LDFLAGS accordingly
> 31a1ae59c46 gh-36534: CI Linux: Fix `centos-7` after #36435, remove 
> `gentoo-python3.12` for now, use `conda-forge` with `-python3.11`
> b7d34011471 gh-36533: `pkgs/sage-conf_pypi`: Repair after #36400, #36435
> ebef87aa8db (tag: 10.2.rc0) Updated SageMath version to 10.2.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/5e861409-f499-4cd6-8463-9393aca33913n%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/CAAWYfq0B6ufcFhirAQasc%2BuZakb2FnPFqgepWfRrxWkOSNY0dg%40mail.gmail.com.

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

[Dima Pasechnik]

On Wed, Nov 1, 2023 at 1:13 PM Dima Pasechnik  wrote:
>
> On Wed, Nov 1, 2023 at 12:47 PM Dima Pasechnik  wrote:
> >
> > I've opened https://github.com/sagemath/sage/issues/36624 to deal with it
> As I wrote on the issue above, here we get very small primes for the
> RSA, 37 and 2, and
> in particular 2 is probably breaking something in the implementation.

Indeed.
Fixed in https://github.com/sagemath/sage/pull/36625 - please review

>
> >
> > On Wed, Nov 1, 2023 at 12:32 PM Dima Pasechnik  wrote:
> > >
> > > I've added
> > >
> > > --- a/src/sage/tests/book_stein_ent.py
> > > +++ b/src/sage/tests/book_stein_ent.py
> > > @@ -198,6 +198,7 @@ sage: def rsa(bits):
> > >  : phi_n = (p-1) * (q-1)
> > >  : while True:
> > >  : e = ZZ.random_element(1,phi_n)
> > > +: print("e=", e)
> > >  : if gcd(e,phi_n) == 1: break
> > >  : d = lift(Mod(e,phi_n)^(-1))
> > >  : return e, d, n
> > >
> > > and see
> > >
> > > sage -t --warn-long 33.1
> > > --random-seed=119293255820329071348175335411518596036
> > > src/sage/tests/book_stein_ent.py
> > > **
> > > File "src/sage/tests/book_stein_ent.py", line 205, in 
> > > sage.tests.book_stein_ent
> > > Failed example:
> > > e,d,n = rsa(20)
> > > Expected nothing
> > > Got:
> > > e= 4
> > > e= 18
> > > e= 22
> > > e= 3
> > > e= 18
> > > e= 18
> > > e= 11
> > > **
> > > File "src/sage/tests/book_stein_ent.py", line 207, in 
> > > sage.tests.book_stein_ent
> > > Failed example:
> > > decrypt(c, d, n)
> > > Expected:
> > > 123
> > > Got:
> > > 49
> > >
> > > ---
> > >
> > > with a different seed I see
> > >
> > >e= 659913
> > > e= 1602755
> > > e= 2633
> > >
> > >
> > > (i.e. the e used will be 2633, as opposed to 11 with the random seed
> > > in question)
> > >
> > > So it's either an issue with ZZ.random_element(1,phi_n), or with the
> > > need for e to be bigger (or both)
> > >
> > > Someone versed in RSA should step in here.
> > >
> > > Dima
> > >
> > > On Wed, Nov 1, 2023 at 8:45 AM david@gmail.com
> > >  wrote:
> > > >
> > > > I'm seeing a new random failure on both MacOS and Fedora 35. The test 
> > > > passes with other random seeds.
> > > >
> > > > sage -t --warn-long 33.1 
> > > > --random-seed=119293255820329071348175335411518596036 
> > > > src/sage/tests/book_stein_ent.py
> > > >
> > > > **
> > > >
> > > > File "src/sage/tests/book_stein_ent.py", line 206, in 
> > > > sage.tests.book_stein_ent
> > > >
> > > > Failed example:
> > > >
> > > > decrypt(c, d, n)
> > > >
> > > > Expected:
> > > >
> > > > 123
> > > >
> > > > Got:
> > > >
> > > > 49
> > > >
> > > > **
> > > >
> > > > 1 item had failures:
> > > >
> > > >1 of 257 in sage.tests.book_stein_ent
> > > >
> > > > [256 tests, 1 failure, 5.62 s]
> > > >
> > > >
> > > >
> > > > sage -t --long --warn-long 33.1 
> > > > --random-seed=316346340216019203823556085838607651488 
> > > > src/sage/tests/book_stein_ent.py
> > > >
> > > > [261 tests, 5.91 s]
> > > >
> > > > --
> > > >
> > > > All tests passed!
> > > >
> > > > --
> > > >
> > > > Total time for all tests: 6.0 seconds
> > > >
> > > > cpu time: 5.9 seconds
> > > >
> > > &

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

[Dima Pasechnik]

On Wed, Nov 1, 2023 at 12:47 PM Dima Pasechnik  wrote:
>
> I've opened https://github.com/sagemath/sage/issues/36624 to deal with it
As I wrote on the issue above, here we get very small primes for the
RSA, 37 and 2, and
in particular 2 is probably breaking something in the implementation.

>
> On Wed, Nov 1, 2023 at 12:32 PM Dima Pasechnik  wrote:
> >
> > I've added
> >
> > --- a/src/sage/tests/book_stein_ent.py
> > +++ b/src/sage/tests/book_stein_ent.py
> > @@ -198,6 +198,7 @@ sage: def rsa(bits):
> >  : phi_n = (p-1) * (q-1)
> >  : while True:
> >  : e = ZZ.random_element(1,phi_n)
> > +: print("e=", e)
> >  : if gcd(e,phi_n) == 1: break
> >  : d = lift(Mod(e,phi_n)^(-1))
> >  : return e, d, n
> >
> > and see
> >
> > sage -t --warn-long 33.1
> > --random-seed=119293255820329071348175335411518596036
> > src/sage/tests/book_stein_ent.py
> > **
> > File "src/sage/tests/book_stein_ent.py", line 205, in 
> > sage.tests.book_stein_ent
> > Failed example:
> > e,d,n = rsa(20)
> > Expected nothing
> > Got:
> > e= 4
> > e= 18
> > e= 22
> > e= 3
> > e= 18
> > e= 18
> > e= 11
> > **
> > File "src/sage/tests/book_stein_ent.py", line 207, in 
> > sage.tests.book_stein_ent
> > Failed example:
> > decrypt(c, d, n)
> > Expected:
> > 123
> > Got:
> > 49
> >
> > ---
> >
> > with a different seed I see
> >
> >e= 659913
> > e= 1602755
> > e= 2633
> >
> >
> > (i.e. the e used will be 2633, as opposed to 11 with the random seed
> > in question)
> >
> > So it's either an issue with ZZ.random_element(1,phi_n), or with the
> > need for e to be bigger (or both)
> >
> > Someone versed in RSA should step in here.
> >
> > Dima
> >
> > On Wed, Nov 1, 2023 at 8:45 AM david@gmail.com
> >  wrote:
> > >
> > > I'm seeing a new random failure on both MacOS and Fedora 35. The test 
> > > passes with other random seeds.
> > >
> > > sage -t --warn-long 33.1 
> > > --random-seed=119293255820329071348175335411518596036 
> > > src/sage/tests/book_stein_ent.py
> > >
> > > **
> > >
> > > File "src/sage/tests/book_stein_ent.py", line 206, in 
> > > sage.tests.book_stein_ent
> > >
> > > Failed example:
> > >
> > > decrypt(c, d, n)
> > >
> > > Expected:
> > >
> > > 123
> > >
> > > Got:
> > >
> > > 49
> > >
> > > **
> > >
> > > 1 item had failures:
> > >
> > >1 of 257 in sage.tests.book_stein_ent
> > >
> > > [256 tests, 1 failure, 5.62 s]
> > >
> > >
> > >
> > > sage -t --long --warn-long 33.1 
> > > --random-seed=316346340216019203823556085838607651488 
> > > src/sage/tests/book_stein_ent.py
> > >
> > > [261 tests, 5.91 s]
> > >
> > > --
> > >
> > > All tests passed!
> > >
> > > --
> > >
> > > Total time for all tests: 6.0 seconds
> > >
> > > cpu time: 5.9 seconds
> > >
> > > cumulative wall time: 5.9 seconds
> > >
> > >
> > > sage -t --long --warn-long 33.1 
> > > --random-seed=291401821193365627335310477024028027230 
> > > src/sage/tests/book_stein_ent.py
> > >
> > > [261 tests, 6.82 s]
> > >
> > > --
> > >
> > > All tests passed!
> > >
> > > --
> > >
> > > Total time for all tests: 6.9 seconds
> > >
> > > cpu time: 7.4 seconds
> > >
> > > cumulative wall time: 6.8 seconds
> >

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

[Dima Pasechnik]

I've opened https://github.com/sagemath/sage/issues/36624 to deal with it

On Wed, Nov 1, 2023 at 12:32 PM Dima Pasechnik  wrote:
>
> I've added
>
> --- a/src/sage/tests/book_stein_ent.py
> +++ b/src/sage/tests/book_stein_ent.py
> @@ -198,6 +198,7 @@ sage: def rsa(bits):
>  : phi_n = (p-1) * (q-1)
>  : while True:
>  : e = ZZ.random_element(1,phi_n)
> +: print("e=", e)
>  : if gcd(e,phi_n) == 1: break
>  : d = lift(Mod(e,phi_n)^(-1))
>  : return e, d, n
>
> and see
>
> sage -t --warn-long 33.1
> --random-seed=119293255820329071348175335411518596036
> src/sage/tests/book_stein_ent.py
> **
> File "src/sage/tests/book_stein_ent.py", line 205, in 
> sage.tests.book_stein_ent
> Failed example:
> e,d,n = rsa(20)
> Expected nothing
> Got:
> e= 4
> e= 18
> e= 22
> e= 3
> e= 18
> e= 18
> e= 11
> **
> File "src/sage/tests/book_stein_ent.py", line 207, in 
> sage.tests.book_stein_ent
> Failed example:
> decrypt(c, d, n)
> Expected:
> 123
> Got:
> 49
>
> ---
>
> with a different seed I see
>
>e= 659913
> e= 1602755
> e= 2633
>
>
> (i.e. the e used will be 2633, as opposed to 11 with the random seed
> in question)
>
> So it's either an issue with ZZ.random_element(1,phi_n), or with the
> need for e to be bigger (or both)
>
> Someone versed in RSA should step in here.
>
> Dima
>
> On Wed, Nov 1, 2023 at 8:45 AM david@gmail.com
>  wrote:
> >
> > I'm seeing a new random failure on both MacOS and Fedora 35. The test 
> > passes with other random seeds.
> >
> > sage -t --warn-long 33.1 
> > --random-seed=119293255820329071348175335411518596036 
> > src/sage/tests/book_stein_ent.py
> >
> > **
> >
> > File "src/sage/tests/book_stein_ent.py", line 206, in 
> > sage.tests.book_stein_ent
> >
> > Failed example:
> >
> > decrypt(c, d, n)
> >
> > Expected:
> >
> > 123
> >
> > Got:
> >
> > 49
> >
> > **
> >
> > 1 item had failures:
> >
> >1 of 257 in sage.tests.book_stein_ent
> >
> > [256 tests, 1 failure, 5.62 s]
> >
> >
> >
> > sage -t --long --warn-long 33.1 
> > --random-seed=316346340216019203823556085838607651488 
> > src/sage/tests/book_stein_ent.py
> >
> > [261 tests, 5.91 s]
> >
> > --
> >
> > All tests passed!
> >
> > --
> >
> > Total time for all tests: 6.0 seconds
> >
> > cpu time: 5.9 seconds
> >
> > cumulative wall time: 5.9 seconds
> >
> >
> > sage -t --long --warn-long 33.1 
> > --random-seed=291401821193365627335310477024028027230 
> > src/sage/tests/book_stein_ent.py
> >
> > [261 tests, 6.82 s]
> >
> > --
> >
> > All tests passed!
> >
> > --
> >
> > Total time for all tests: 6.9 seconds
> >
> > cpu time: 7.4 seconds
> >
> > cumulative wall time: 6.8 seconds
> >
> >
> > On Wednesday, November 1, 2023 at 1:04:00 AM UTC+1 John H Palmieri wrote:
> >>
> >> I'm seeing one new failure on two different OS X machines (one Intel, one 
> >> M2):
> >>
> >> File 
> >> "src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py",
> >>  line 398, in 
> >> sage.tests.books.computational-mathematics-with-sagemath.mpoly_doctest
> >> Failed example:
> >> [CDF['x'](p(y=ys[0][0])).roots() for p in J.gens()] # abs tol 2e-15
> >> Expected:
> >> [[(-0.5999, 1), (0.6001, 1)], 
> >> [(0.6001, 1), (2.601, 1)]]
> >> Got:
> >> [[(-0.5998, 1), (0.5999, 1)],
> >>  [(0.6001 - 6.162975822039155e-33*I, 1),
> >>

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

[Dima Pasechnik]

I've added

--- a/src/sage/tests/book_stein_ent.py
+++ b/src/sage/tests/book_stein_ent.py
@@ -198,6 +198,7 @@ sage: def rsa(bits):
 : phi_n = (p-1) * (q-1)
 : while True:
 : e = ZZ.random_element(1,phi_n)
+: print("e=", e)
 : if gcd(e,phi_n) == 1: break
 : d = lift(Mod(e,phi_n)^(-1))
 : return e, d, n

and see

sage -t --warn-long 33.1
--random-seed=119293255820329071348175335411518596036
src/sage/tests/book_stein_ent.py
**
File "src/sage/tests/book_stein_ent.py", line 205, in sage.tests.book_stein_ent
Failed example:
e,d,n = rsa(20)
Expected nothing
Got:
e= 4
e= 18
e= 22
e= 3
e= 18
e= 18
e= 11
**
File "src/sage/tests/book_stein_ent.py", line 207, in sage.tests.book_stein_ent
Failed example:
decrypt(c, d, n)
Expected:
123
Got:
49

---

with a different seed I see

   e= 659913
e= 1602755
e= 2633


(i.e. the e used will be 2633, as opposed to 11 with the random seed
in question)

So it's either an issue with ZZ.random_element(1,phi_n), or with the
need for e to be bigger (or both)

Someone versed in RSA should step in here.

Dima

On Wed, Nov 1, 2023 at 8:45 AM david@gmail.com
 wrote:
>
> I'm seeing a new random failure on both MacOS and Fedora 35. The test passes 
> with other random seeds.
>
> sage -t --warn-long 33.1 
> --random-seed=119293255820329071348175335411518596036 
> src/sage/tests/book_stein_ent.py
>
> **
>
> File "src/sage/tests/book_stein_ent.py", line 206, in 
> sage.tests.book_stein_ent
>
> Failed example:
>
> decrypt(c, d, n)
>
> Expected:
>
> 123
>
> Got:
>
> 49
>
> **
>
> 1 item had failures:
>
>1 of 257 in sage.tests.book_stein_ent
>
> [256 tests, 1 failure, 5.62 s]
>
>
>
> sage -t --long --warn-long 33.1 
> --random-seed=316346340216019203823556085838607651488 
> src/sage/tests/book_stein_ent.py
>
> [261 tests, 5.91 s]
>
> --
>
> All tests passed!
>
> --
>
> Total time for all tests: 6.0 seconds
>
> cpu time: 5.9 seconds
>
> cumulative wall time: 5.9 seconds
>
>
> sage -t --long --warn-long 33.1 
> --random-seed=291401821193365627335310477024028027230 
> src/sage/tests/book_stein_ent.py
>
> [261 tests, 6.82 s]
>
> --
>
> All tests passed!
>
> --
>
> Total time for all tests: 6.9 seconds
>
> cpu time: 7.4 seconds
>
> cumulative wall time: 6.8 seconds
>
>
> On Wednesday, November 1, 2023 at 1:04:00 AM UTC+1 John H Palmieri wrote:
>>
>> I'm seeing one new failure on two different OS X machines (one Intel, one 
>> M2):
>>
>> File 
>> "src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py",
>>  line 398, in 
>> sage.tests.books.computational-mathematics-with-sagemath.mpoly_doctest
>> Failed example:
>> [CDF['x'](p(y=ys[0][0])).roots() for p in J.gens()] # abs tol 2e-15
>> Expected:
>> [[(-0.5999, 1), (0.6001, 1)], 
>> [(0.6001, 1), (2.601, 1)]]
>> Got:
>> [[(-0.5998, 1), (0.5999, 1)],
>>  [(0.6001 - 6.162975822039155e-33*I, 1),
>>   (2.6 + 3.0814879110195774e-32*I, 1)]]
>> **
>> 1 item had failures:
>>1 of 161 in 
>> sage.tests.books.computational-mathematics-with-sagemath.mpoly_doctest
>> [160 tests, 1 failure, 9.54 s]
>> --
>> sage -t --random-seed=151162198507806711540314627633568329221 
>> src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py
>>   # 1 doctest failed
>>
>>
>> On Monday, October 30, 2023 at 5:22:19 PM UTC-7 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
>>>
>>> I'm proposing 10.2.rc0 next, so if there is anything that you want to be 
>>> merged before then now would be a good time to do so ;)
>>>
>>>
>>> eb8417b6107 (github/develop, tag: 10.2.beta9) Updated SageMath version to 
>>> 10.2.beta9
>>> c0221f90a86 gh-36554: Speedup of the method to reduce ternary quadratic 
>>> forms in the class TernaryQF
>>> f5bdda94fd4 gh-36553: Add a hash function for the class TernaryQF.
>>> 37f7f5d5028 gh-36552: `src/sage/misc/cython.py`: Fix the 

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

[Dima Pasechnik]

On Tue, Oct 31, 2023 at 5:29 PM John H Palmieri  wrote:
>
> I don't see this yet on any mirrors.

one can always use
https://github.com/sagemath/sage/archive/refs/tags/10.2.beta9.tar.gz
(this is unconfigured source, though, i.e. it would need ./bootstrap to be run)

>
> On Monday, October 30, 2023 at 5:22:19 PM UTC-7 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
>>
>> I'm proposing 10.2.rc0 next, so if there is anything that you want to be 
>> merged before then now would be a good time to do so ;)
>>
>>
>> eb8417b6107 (github/develop, tag: 10.2.beta9) Updated SageMath version to 
>> 10.2.beta9
>> c0221f90a86 gh-36554: Speedup of the method to reduce ternary quadratic 
>> forms in the class TernaryQF
>> f5bdda94fd4 gh-36553: Add a hash function for the class TernaryQF.
>> 37f7f5d5028 gh-36552: `src/sage/misc/cython.py`: Fix the workaround for 
>> setuptools_scm
>> ccb093422cd gh-36550: remove deprecated name parameter in category ; capital 
>> for Coxeter
>> 5c6004be074 gh-36547: expurge parent_old from cryptosystem
>> 7c6cda9559f gh-36541: `build/pkgs/nauty`: Upgrade to 2.8.6, require nauty >= 
>> 2.8
>> c8299c7b1b6 gh-36540: `build/pkgs/pip`: Increase lower version bound; 
>> upgrade `pip`, `wheel`, `packaging`, `platformdirs`
>> 970d7f27c88 gh-36537: refresh the maple(tm) interface
>> ee0adcdad3d gh-36535: build/pkgs/openssl: Update to 3.0.12
>> 81665ba4a36 gh-36532: `pkgs/sagemath-standard`: Fix sdist
>> fef74127ec2 gh-36528: some cleanup in quadratic forms
>> d2523e70b00 gh-36522: Fix linter failure E401 multiple imports on one line
>> 7c974480400 gh-36521: GH Actions: Fix wheel build
>> ac7ed0e2478 gh-36520: `pkgs/sagemath-{bliss,sirocco,tdlib}`: Fix sdists
>> dff2b2db763 gh-36516: `sage.schemes.toric`: Remove pyright 'is possibly 
>> unbound' warnings
>> f79dc7a181f gh-36514: `build/pkgs/sagenb_export`: Fix install-requires.txt
>> 5eb0dba9618 gh-36513: `networkx`, `scipy`, `ipywidgets`: Update version 
>> ranges in `conda.txt`
>> 15b24deb5d7 gh-36511: Exclude symlinks from vscode search config via glob 
>> pattern
>> 0a0f14180e1 gh-36510: Add pyright ci annotations
>> 97b06bd9b4c gh-36509: meson 1.2.3, numpy 1.26.1, require meson >= 1.2.0
>> 1185345f0f4 gh-36507: Fix implicit noexcept warnings
>> 5b0af6777f8 gh-36506: Support launching notebook 7
>> b0569410e72 gh-36499: Remove conda patchelf distro
>> a49c36b8d50 gh-36497: lint.yml: Always run all 3 linters
>> ca7de640ef3 gh-36496: build*.yml: Fix application of CI fixes broken in 
>> #36442
>> 26dca91d79e gh-36495: Conditional documentation
>> 2c7b52eb7e6 gh-36493: improve method `cycle_basis` for graphs with multiple 
>> edges
>> 6d304484897 gh-36491: Fix size of varchenko_matrix
>> 7a37e8ff681 gh-36488: Fix func_persist: do not use the (now removed) 
>> inspect.formatargspec, but instead use inspect.signature.
>> 4d20a26e6fb gh-36484: Fix typos in Italian docs
>> 83dcc176064 gh-36483: Remove spurious diffs in doc build changes
>> d052d9f99e3 gh-36482: Loosen version requirement on fpylll and align its 
>> conda version
>> 4e658387593 gh-36478: some details in pyx files in combinat
>> b297c4d8ec7 gh-36475: .github/workflows/doc-build.yml: Repair display of 
>> changes
>> 9d3e427285a gh-36466: Run incremental linux ci only when packages changed
>> a1e100a22e6 gh-36462: using ruff for UP004, UP008, UP028
>> 980f28c681d gh-36444: upgrade cypari2 to 2.1.4
>> b62d8401917 gh-36416: `build/pkgs/cython`: Update to 3.0.4
>> 652d42948ef gh-36292: Fix sync labels issues for step 2 going live completion
>> 6afeae8285b gh-36271: `sage.{dynamics,schemes}`: Modularization fixes, 
>> docstring cosmetics, update `# needs`
>> b42b3818706 gh-36246: Use URLs to online Sage documents for JupyterLab
>> c59ebbb4e18 gh-36144: Revive sage live doc using jupyter-sphinx
>> 94682909ba4 gh-35302: update pari to 2.15.4, drop patch
>> 07a2afd65fb (tag: 10.2.beta8) Updated SageMath version to 10.2.beta8
>
> --
> 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/0bef2957-1ae5-42cc-8b37-6d35e8a8f5fdn%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/CAAWYfq1KqB47x-sjgbRbNwqMqNURwta%3D6AaYFpF-p8dtRewfdQ%40mail.gmail.com.

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

[Dima Pasechnik]

you need

 make cython-clean cython-uninstall


to trigger the rebuild of Cython by

 make cython

On Mon, 16 Oct 2023, 21:57 Dima Pasechnik,  wrote:

> for me, the beginning of logs/pkgs/cython-3.0.2.log
> on the branch of PR 36332
> is as follows. You see, the patch is applied.
>
>
> Attempting to download package Cython-3.0.2.tar.gz from mirrors
>
> https://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cython/Cython-3.0.2.tar.gz
> [..]
> cython-3.0.2
> 
> Setting up build directory for cython-3.0.2
> Finished extraction
> Applying patches from ../patches...
> Applying ../patches/5690.patch
> patching file Cython/Debugger/DebugWriter.py
> 
>
> Why it's not like this for you, I have no idea.
>
> On Mon, Oct 16, 2023 at 9:54 PM Emmanuel Charpentier
>  wrote:
> >
> > Le lundi 16 octobre 2023 à 22:41:38 UTC+2, Dima Pasechnik a écrit :
> >
> > can you check that build/pkgs/cython/patches/5690.patch is there?
> >
> > Indeed it is here…
> >
> > charpent@zen-book-flip:/usr/local/sage-10$ ls
> build/pkgs/cython/patches/ 5690.patch
> >
> > And make build still fails :
> >
> > [sagelib-10.2.beta7] [143/144] Cythonizing sage/symbolic/expression.pyx
> [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback:
> [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call
> last): [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker
> [sagelib-10.2.beta7] result = (True, func(*args, **kwds))
> [sagelib-10.2.beta7] ^^^ [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar
> [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7]
>  [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return
> cythonize_one(*m) [sagelib-10.2.beta7] ^
> [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None,
> pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError:
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
> [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The
> above exception was the direct cause of the following exception:
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call
> last): [sagelib-10.2.beta7] File "", line 2, in 
> [sagelib-10.2.beta7] File "", line 34, in 
> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in
>  [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7]
> ^^ [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1125, in cythonize [sagelib-10.2.beta7] result.get(9) # seconds
> [sagelib-10.2.beta7] ^ [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get
> [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7]
> Cython.Compiler.Errors.CompileError:
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
> [sagelib-10.2.beta7]
> 
> [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7]
> 
> [sagelib-10.2.beta7] Please email sage-devel (
> http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7]
> explaining the problem and including the relevant part of the log file
> [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log
> [sagelib-10.2.beta7] Describe your computer, operating system, etc.
> [sagelib-10.2.beta7]
> 
> [sagelib-10.2.beta7] error: subprocess-exited-with-error
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not
> run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7]
> ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note:
> This error originates from a subprocess, and is likely not a problem with
> pip. [sagelib-1

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

[Dima Pasechnik]

for me, the beginning of logs/pkgs/cython-3.0.2.log
on the branch of PR 36332
is as follows. You see, the patch is applied.


Attempting to download package Cython-3.0.2.tar.gz from mirrors
https://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cython/Cython-3.0.2.tar.gz
[..]
cython-3.0.2

Setting up build directory for cython-3.0.2
Finished extraction
Applying patches from ../patches...
Applying ../patches/5690.patch
patching file Cython/Debugger/DebugWriter.py


Why it's not like this for you, I have no idea.

On Mon, Oct 16, 2023 at 9:54 PM Emmanuel Charpentier
 wrote:
>
> Le lundi 16 octobre 2023 à 22:41:38 UTC+2, Dima Pasechnik a écrit :
>
> can you check that build/pkgs/cython/patches/5690.patch is there?
>
> Indeed it is here…
>
> charpent@zen-book-flip:/usr/local/sage-10$ ls build/pkgs/cython/patches/ 
> 5690.patch
>
> And make build still fails :
>
> [sagelib-10.2.beta7] [143/144] Cythonizing sage/symbolic/expression.pyx 
> [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: 
> [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call 
> last): [sagelib-10.2.beta7] File 
> "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker 
> [sagelib-10.2.beta7] result = (True, func(*args, **kwds)) 
> [sagelib-10.2.beta7] ^^^ [sagelib-10.2.beta7] File 
> "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar 
> [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7] 
>  [sagelib-10.2.beta7] File 
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>  line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return 
> cythonize_one(*m) [sagelib-10.2.beta7] ^ [sagelib-10.2.beta7] 
> File 
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>  line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None, 
> pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: 
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
>  [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The above 
> exception was the direct cause of the following exception: 
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call last): 
> [sagelib-10.2.beta7] File "", line 2, in  
> [sagelib-10.2.beta7] File "", line 34, in  
> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in 
>  [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7] 
> ^^ [sagelib-10.2.beta7] File 
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>  line 1125, in cythonize [sagelib-10.2.beta7] result.get(9) # seconds 
> [sagelib-10.2.beta7] ^ [sagelib-10.2.beta7] File 
> "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get 
> [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7] 
> Cython.Compiler.Errors.CompileError: 
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
>  [sagelib-10.2.beta7] 
>  
> [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7] 
>  
> [sagelib-10.2.beta7] Please email sage-devel 
> (http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7] explaining 
> the problem and including the relevant part of the log file 
> [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log 
> [sagelib-10.2.beta7] Describe your computer, operating system, etc. 
> [sagelib-10.2.beta7] 
>  
> [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] 
> [sagelib-10.2.beta7] × python setup.py develop did not run successfully. 
> [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for 
> output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates 
> from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] 
> full command: 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 -c ' 
> [sagelib-10.2.beta7] exec(compile('"'"''"'"''"'"' [sagelib-10.2.beta7] # This 
> is  -- a caller that pip uses to run setup.py 
> [sageli

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

[Dima Pasechnik]

can you check that build/pkgs/cython/patches/5690.patch is there?

On Mon, Oct 16, 2023 at 9:38 PM Emmanuel Charpentier
 wrote:
>
> Le lundi 16 octobre 2023 à 22:31:38 UTC+2, Emmanuel Charpentier a écrit :
>
> Le lundi 16 octobre 2023 à 18:35:28 UTC+2, Dima Pasechnik a écrit :
>
> On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik  wrote:
> >
> > Please also send config.log, as I already asked.
>
> Done. See above
>
>
> >
> > On Mon, Oct 16, 2023 at 5:27 PM  wrote:
> > >
> > > IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log
>
> It looks as if you haven't installed the patch for Cython, as I still see
>
> ValueError: Invalid tag name '.0'
>
> in your log.
>
> You can check this somewhere in the beginning of logs/pkgs/cython*...log
> You'd see there "applying patch "
>
> Indeed :
>
> charpent@zen-book-flip:/usr/local/sage-10$ grep patch 
> logs/pkgs/cython-3.0.2.log No patch files found in ../patches
>
> However, I’m pretty certain to have run it (but it has already scrolled off 
> my session transcript) .
>
> I’ll try to start again :
>
> - make sagelib-clean sagelib uninstall - git pull upstream pull/36332/head
>
> BTW :
>
> charpent@zen-book-flip:/usr/local/sage-10$ git pull upstream pull/36332/head 
> Depuis github.com:sagemath/sage * branch refs/pull/36332/head -> FETCH_HEAD 
> Déjà à jour.
>
> (“already up to date”).
>
> - make cython - make build
>
>
>
>
> > >
> > > Here it is.
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "sage-release" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an 
> > > email to sage-release...@googlegroups.com.
> > > To view this discussion on the web visit 
> > > https://groups.google.com/d/msgid/sage-release/3210ca421c3720605652da6ca86165e187c64ccd.camel%40gmail.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/9bba3b91-09c9-40f0-8945-9d5c7a3c5b24n%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/CAAWYfq0oJNz%3D%2B1jH0%3DA9NfNyqNciQzhdLOgEEJURpc7%2BLy-Kzg%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik  wrote:
>
> Please also send config.log, as I already asked.
>
> On Mon, Oct 16, 2023 at 5:27 PM  wrote:
> >
> >  IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

It looks as if you haven't installed the patch for Cython, as I still see

ValueError: Invalid tag name '.0'

in your log.

You can check this somewhere in the beginning of logs/pkgs/cython*...log
You'd see there "applying patch "


> >
> > Here it is.
> >
> > --
> > 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/3210ca421c3720605652da6ca86165e187c64ccd.camel%40gmail.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/CAAWYfq3tLYmFNPJfAHgwVp2QiGPKd9SYECHBdxvmEdWaVMCAUw%40mail.gmail.com.

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

[Dima Pasechnik]

Please also send config.log, as I already asked.

On Mon, Oct 16, 2023 at 5:27 PM  wrote:
>
>  IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log
>
> Here it is.
>
> --
> 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/3210ca421c3720605652da6ca86165e187c64ccd.camel%40gmail.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/CAAWYfq3k5BJN8-%2BX484tothTXa7imcKt7KPbUS%3DQzaYf-7Le9Q%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Oct 16, 2023 at 4:38 PM Emmanuel Charpentier
 wrote:
>
> Would the updated install.log be useful ?
IMHO  what we need there is in logs/pkgs/sagelib-10.2.beta7.log

>
> Le lundi 16 octobre 2023 à 17:09:31 UTC+2, Dima Pasechnik a écrit :
>>
>> please post config.log, and logs/pkgs/sagelib-10.2.beta7.log
>>
>> In your previous install.log I see
>>
>> [sagelib-10.2.beta7] Error compiling Cython file:
>> [sagelib-10.2.beta7]
>> 
>> [sagelib-10.2.beta7] ...
>> [sagelib-10.2.beta7] # -*- coding: utf-8 -*-
>> [sagelib-10.2.beta7] ^
>> [sagelib-10.2.beta7]
>> 
>> [sagelib-10.2.beta7]
>> [sagelib-10.2.beta7] sage/sets/disjoint_set.pyx:1:0: Compiler
>> crash in DebugTransform
>> [sagelib-10.2.beta7]
>> [sagelib-10.2.beta7]
>> [sagelib-10.2.beta7] Compiler crash traceback from this point on:
>> [sagelib-10.2.beta7] File "Cython/Compiler/Visitor.py", line
>> 182, in Cython.Compiler.Visitor.TreeVisitor._visit
>> [sagelib-10.2.beta7] File
>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Compiler/ParseTreeTransforms.py",
>> line 4053, in visit_ModuleNode
>> [sagelib-10.2.beta7] self.visit_FuncDefNode(nested_funcdef)
>> [sagelib-10.2.beta7] File
>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Compiler/ParseTreeTransforms.py",
>> line 4113, in visit_FuncDefNode
>> [sagelib-10.2.beta7] self.tb.start(arg.name)
>> [sagelib-10.2.beta7] File
>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Debugger/DebugWriter.py",
>> line 42, in start
>> [sagelib-10.2.beta7] self.tb.start(name, attrs or {})
>> [sagelib-10.2.beta7] File "src/lxml/saxparser.pxi", line 841, in
>> lxml.etree.TreeBuilder.start
>> [sagelib-10.2.beta7] File "src/lxml/saxparser.pxi", line 769, in
>> lxml.etree.TreeBuilder._handleSaxStart
>> [sagelib-10.2.beta7] File "src/lxml/apihelpers.pxi", line 179,
>> in lxml.etree._makeSubElement
>> [sagelib-10.2.beta7] File "src/lxml/apihelpers.pxi", line 1754,
>> in lxml.etree._tagValidOrRaise
>> [sagelib-10.2.beta7] ValueError: Invalid tag name '.0'
>>
>> which should disappear from your install.log after you applied the patch.
>> But the other error, this is something different.
>>
>>
>> On Mon, Oct 16, 2023 at 3:12 PM Emmanuel Charpentier
>>  wrote:
>> >
>> > Nope again : make sagelib-clean sagelib uninstall works, but make -j8 
>> > build (or even make build) fails again:
>> >
>> > [ Again a bunch of lines elided… ]
>> >
>> > [sagelib-10.2.beta7] [553/557] Cythonizing sage/symbolic/expression.pyx 
>> > [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: 
>> > [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call 
>> > last): [sagelib-10.2.beta7] File 
>> > "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker 
>> > [sagelib-10.2.beta7] result = (True, func(*args, **kwds)) 
>> > [sagelib-10.2.beta7] ^^^ [sagelib-10.2.beta7] File 
>> > "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar 
>> > [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7] 
>> >  [sagelib-10.2.beta7] File 
>> > "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>> >  line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return 
>> > cythonize_one(*m) [sagelib-10.2.beta7] ^ 
>> > [sagelib-10.2.beta7] File 
>> > "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>> >  line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None, 
>> > pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: 
>> > sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
>> >  [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The 
>> > above exception was the direct cause of the following exception: 
>> > [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call 
>> > last): [sagelib-10.2.beta7] File "", line 2, in  
>> > [sagelib-10.2.beta7] File "", line 34, in  
>> 

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

[Dima Pasechnik]

*** Error 
> building Sage. The following package(s) may have failed to build (not 
> necessarily during this run of 'make all-build'): * package: 
> sagelib-10.2.beta7 last build time: 16 oct. 16:10 log file: 
> /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log It is safe to delete any 
> log files and build directories, but they contain information that is helpful 
> for debugging build problems. WARNING: If you now run 'make' again, the build 
> directory of the same version of the package will, by default, be deleted. 
> Set the environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this. 
> make[1]: *** [Makefile:40 : all-build] Erreur 1 make[1] : on quitte le 
> répertoire « /usr/local/sage-10 » make: *** [Makefile:16 : build] Erreur 2 
> real 2m52,299s user 11m6,822s sys 0m35,210s
> Le lundi 16 octobre 2023 à 15:06:42 UTC+2, Dima Pasechnik a écrit :
>>
>>
>>
>> On Mon, 16 Oct 2023, 14:04 Emmanuel Charpentier,  
>> wrote:
>>>
>>> Nope...
>>>
>>> `make cython` succeeds. Bit `make build fails :
>>
>>
>> oops, sorry, you need to clean sagelib first.
>>
>> make sagelib-clean sagelib-uninstall
>>
>>
>>>
>>> ```
>>> [sagelib-10.2.beta7] [85/85] Cythonizing sage/symbolic/expression.pyx
>>> [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback:
>>> [sagelib-10.2.beta7] """
>>> [sagelib-10.2.beta7] Traceback (most recent call last):
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker
>>> [sagelib-10.2.beta7] result = (True, func(*args, **kwds))
>>> [sagelib-10.2.beta7] ^^^
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar
>>> [sagelib-10.2.beta7] return list(map(*args))
>>> [sagelib-10.2.beta7]
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>>>  line 1325, in cythonize_one_helper
>>> [sagelib-10.2.beta7] return cythonize_one(*m)
>>> [sagelib-10.2.beta7]^
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>>>  line 1301, in cythonize_one
>>> [sagelib-10.2.beta7] raise CompileError(None, pyx_file)
>>> [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: 
>>> sage/combinat/combinat_cython.pyx
>>> [sagelib-10.2.beta7] """
>>> [sagelib-10.2.beta7]
>>> [sagelib-10.2.beta7] The above exception was the direct cause of the 
>>> following exception:
>>> [sagelib-10.2.beta7]
>>> [sagelib-10.2.beta7] Traceback (most recent call last):
>>> [sagelib-10.2.beta7]   File "", line 2, in 
>>> [sagelib-10.2.beta7]   File "", line 34, in 
>>> 
>>> [sagelib-10.2.beta7]   File "/usr/local/sage-10/src/setup.py", line 
>>> 108, in 
>>> [sagelib-10.2.beta7] extensions = cythonize(
>>> [sagelib-10.2.beta7]  ^^
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
>>>  line 1125, in cythonize
>>> [sagelib-10.2.beta7] result.get(9)  # seconds
>>> [sagelib-10.2.beta7] ^
>>> [sagelib-10.2.beta7]   File 
>>> "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get
>>> [sagelib-10.2.beta7] raise self._value
>>> [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: 
>>> sage/combinat/combinat_cython.pyx
>>> [sagelib-10.2.beta7] 
>>> 
>>> [sagelib-10.2.beta7] Error building the Sage library
>>> [sagelib-10.2.beta7] 
>>> 
>>> [sagelib-10.2.beta7] Please email sage-devel 
>>> (http://groups.google.com/group/sage-devel)
>>> [sagelib-10.2.beta7] explaining the problem and including the relevant 
>>> part of the log file
>>> [sagelib-10.2.beta7]   

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

[Dima Pasechnik]

e following warning:
> [sagelib-10.2.beta7] # manifest_maker: standard file '"'"'-c'"'"'
> not found".
> [sagelib-10.2.beta7] # - It generates a shim setup.py, for handling
> setup.cfg-only projects.
> [sagelib-10.2.beta7] import os, sys, tokenize
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] try:
> [sagelib-10.2.beta7] import setuptools
> [sagelib-10.2.beta7] except ImportError as error:
> [sagelib-10.2.beta7] print(
> [sagelib-10.2.beta7] "ERROR: Can not execute `setup.py` since
> setuptools is not available in "
> [sagelib-10.2.beta7] "the build environment.",
> [sagelib-10.2.beta7] file=sys.stderr,
> [sagelib-10.2.beta7] )
> [sagelib-10.2.beta7] sys.exit(1)
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] __file__ = %r
> [sagelib-10.2.beta7] sys.argv[0] = __file__
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] if os.path.exists(__file__):
> [sagelib-10.2.beta7] filename = __file__
> [sagelib-10.2.beta7] with tokenize.open(__file__) as f:
> [sagelib-10.2.beta7] setup_py_code = f.read()
> [sagelib-10.2.beta7] else:
> [sagelib-10.2.beta7] filename = " caller>"
> [sagelib-10.2.beta7] setup_py_code = "from setuptools import
> setup; setup()"
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] exec(compile(setup_py_code, filename, "exec"))
> [sagelib-10.2.beta7] '"'"''"'"''"'"' %
> ('"'"'/usr/local/sage-10/src/setup.py'"'"',), "",
> "exec"))' --no-user-cfg develop --no-deps
> [sagelib-10.2.beta7] cwd: /usr/local/sage-10/src/
> [sagelib-10.2.beta7]   Rolling back uninstall of sagemath-standard
> [sagelib-10.2.beta7]   Moving to
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/sagemath-standard.egg-link
> [sagelib-10.2.beta7]from
> /tmp/pip-uninstall-8mtj1z6r/sagemath-standard.egg-link
> [sagelib-10.2.beta7] error: subprocess-exited-with-error
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] × python setup.py develop did not run successfully.
> [sagelib-10.2.beta7] │ exit code: 1
> [sagelib-10.2.beta7] ╰─> See above for output.
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] note: This error originates from a subprocess, and is
> likely not a problem with pip.
> [sagelib-10.2.beta7]
> 
> [sagelib-10.2.beta7] Error installing
> [sagelib-10.2.beta7]
> 
> [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] real 0m51,149s
> [sagelib-10.2.beta7] user 2m36,755s
> [sagelib-10.2.beta7] sys 0m8,185s
> make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1
> make[3]: *** [Makefile:3373 :
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7]
> Erreur 2
> make[2]: *** [Makefile:2849 : all-build] Erreur 2
> make[2] : on quitte le répertoire « /usr/local/sage-10/build/make »
>
> real 0m51,674s
> user 2m39,788s
> sys 0m11,577s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-build'):
>
> * package: sagelib-10.2.beta7
>   last build time: 16 oct. 15:01
>   log file:/usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version of the package will, by default, be deleted. Set the
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>
> make[1]: *** [Makefile:40 : all-build] Erreur 1
> make[1] : on quitte le répertoire « /usr/local/sage-10 »
> make: *** [Makefile:16 : build] Erreur 2
>
> real 0m52,809s
> user 2m41,021s
> sys 0m12,733s
> ```
>
> Hints ?
>
>
> Le lundi 16 octobre 2023 à 10:37:35 UTC+2, Dima Pasechnik a écrit :
>
>> On Mon, Oct 16, 2023 at 09:16:46AM +0200, emanuel.c...@gmail.com wrote:
>> > More examination of the `install.log` file shows a raft of Cython
>> errors. `install.log` (compressed) enclosed.
>> I think this shows that certain patch for Cython 3.0.2 (Cython PR #5690)
>> must have been included.
>> E.g. it's in the branch of https://github.com/sagemath/sage/pull/36332,
>> the file build/pkgs/cython/patches/5690.patch there
>>
>> So you can do
>>

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

[Dima Pasechnik]

On Tue, Oct 10, 2023 at 12:02 AM Matthias Köppe
 wrote:
>
> On Monday, October 9, 2023 at 3:51:35 PM UTC-7 Dima Pasechnik wrote:
>
> On Mon, Oct 9, 2023 at 11:45 PM Matthias Köppe  wrote:
> >
> > We are building most of our Python packages with build isolation. This 
> > means that for the build of the packages, it is irrelevant what is 
> > installed in SAGE_VENV; only the wheels of its build dependencies need to 
> > be present. After the build of a package, when we install the built wheel 
> > in the SAGE_VENV, pip checks for dependencies and may complain when runtime 
> > dependencies are unmet. We fall back to ignoring dependencies when 
> > installing. It is safe to ignore all errors/warning during this process.
>
> I don't get it. These are build dependencies, not only runtime ones;
> you can't build numpy without cython; you can't build cython without
> pythran; you cannot build pythran without numpy.
>
>
> No, pythran does not have any build dependencies other than setuptools.
> It's pure Python, nothing needs compiling.

Really? 
https://github.com/serge-sans-paille/pythran/tree/master/pythran/pythonic
is full of C++
>
> --
> 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/e9b41af0-7abf-43bf-9378-177681772942n%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/CAAWYfq1i21QzWBPrZ98dprcRNbhKCMoOFvu4uBdTnGTfougU6Q%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Oct 9, 2023 at 11:45 PM Matthias Köppe  wrote:
>
> We are building most of our Python packages with build isolation. This means 
> that for the build of the packages, it is irrelevant what is installed in 
> SAGE_VENV; only the wheels of its build dependencies need to be present. 
> After the build of a package, when we install the built wheel in the 
> SAGE_VENV, pip checks for dependencies and may complain when runtime 
> dependencies are unmet. We fall back to ignoring dependencies when 
> installing. It is safe to ignore all errors/warning during this process.

I don't get it. These are build dependencies, not only runtime ones;
you can't build numpy without cython; you can't build cython without
pythran; you cannot build pythran without numpy.



>
> On Monday, October 9, 2023 at 3:34:56 PM UTC-7 John H Palmieri wrote:
>>
>> On Monday, October 9, 2023 at 2:53:57 PM UTC-7 Dima Pasechnik wrote:
>>
>> On Mon, Oct 9, 2023 at 10:44 PM John H Palmieri  wrote:
>> >
>> >
>> >
>> > On Monday, October 9, 2023 at 9:44:02 AM UTC-7 Dima Pasechnik wrote:
>> >
>> > On Mon, Oct 9, 2023 at 5:39 PM John H Palmieri  wrote:
>> > >
>> > > (I tried to send this last night and I see some indication that the 
>> > > message was deleted, so I'm reposting. Apologies if this has already 
>> > > appeared.)
>> > >
>> > > I see some error message (aside from those already reported) but the 
>> > > build completes anyway. These are probably not new.
>> > >
>> > > In pythran's log:
>> > >
>> > > ERROR: Could not find a version that satisfies the requirement numpy 
>> > > (from pythran) (from versions: none)
>> > > ERROR: No matching distribution found for numpy
>> >
>> > numpy is a dependency of pythran, apparently - but it's not listed.
>> >
>> >
>> > It looks like pythran is an order-only dependency of cython which is an 
>> > order-only dependency of numpy, so I guess we're trying to avoid circular 
>> > dependencies by not listing numpy as a dependency of pythran?
>>
>> How is it going to help? A circle is not null-homotopic (topology!),
>> thus one would need to bootstrap one of the packages...
>>
>>
>> How is what going to help? I didn't make any suggestions, although I'm 
>> wondering how the whole thing works.
>>
>>
>>
>>
>>
>> >
>> >
>> > >
>> > > In notebook's log:
>> > >
>> > > ERROR: Could not find a version that satisfies the requirement 
>> > > jupyter_packaging~=0.9 (from versions: none)
>> > > ERROR: No matching distribution found for jupyter_packaging~=0.9
>> >
>> > not sure - I guess it's a good idea to make sure we're switching to
>> > modern notebook (7) asap.
>> >
>> > >
>> > > Should we be concerned about these?
>> > >
>> > >
>> > > On Monday, October 9, 2023 at 9:25:44 AM UTC-7 emanuel.c...@gmail.com 
>> > > wrote:
>> > >>
>> > >>
>> > >>
>> > >> Le lundi 9 octobre 2023 à 18:17:11 UTC+2, Dima Pasechnik a écrit :
>> > >>
>> > >> [ Snip... ]
>> > >>
>> > >> > The key seems to be “ERROR: Could not find a version that satisfies 
>> > >> > the requirement hatchling (from versions: none)“, which I do not 
>> > >> > understand..
>> > >>
>> > >> just a missing dependency (hatchling) for attrs.
>> > >>
>> > >>
>> > >> as a hotfix, run
>> > >>
>> > >> make hatchling
>> > >>
>> > >>
>> > >> Seems to work... but fails again :
>> > >>
>> > >> ```
>> > >> Processing 
>> > >> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels/hatch_vcs-0.3.0-py3-none-any.whl
>> > >> ERROR: Could not find a version that satisfies the requirement 
>> > >> hatch-fancy-pypi-readme (from versions: none)
>> > >> ERROR: No matching distribution found for hatch-fancy-pypi-readme
>> > >> error: subprocess-exited-with-error
>> > >> ```
>> > >>
>> > >> Stuck again...
>> > >>
>> > >> [ Re-Snip... ]
>> > >>
>> > >>
>> > > --
>> > > You received this message because you are subscribed t

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

[Dima Pasechnik]

On Mon, Oct 9, 2023 at 10:44 PM John H Palmieri  wrote:
>
>
>
> On Monday, October 9, 2023 at 9:44:02 AM UTC-7 Dima Pasechnik wrote:
>
> On Mon, Oct 9, 2023 at 5:39 PM John H Palmieri  wrote:
> >
> > (I tried to send this last night and I see some indication that the message 
> > was deleted, so I'm reposting. Apologies if this has already appeared.)
> >
> > I see some error message (aside from those already reported) but the build 
> > completes anyway. These are probably not new.
> >
> > In pythran's log:
> >
> > ERROR: Could not find a version that satisfies the requirement numpy (from 
> > pythran) (from versions: none)
> > ERROR: No matching distribution found for numpy
>
> numpy is a dependency of pythran, apparently - but it's not listed.
>
>
> It looks like pythran is an order-only dependency of cython which is an 
> order-only dependency of numpy, so I guess we're trying to avoid circular 
> dependencies by not listing numpy as a dependency of pythran?

How is it going to help? A circle is not null-homotopic (topology!),
thus one would need to bootstrap one of the packages...


>
>
> >
> > In notebook's log:
> >
> > ERROR: Could not find a version that satisfies the requirement 
> > jupyter_packaging~=0.9 (from versions: none)
> > ERROR: No matching distribution found for jupyter_packaging~=0.9
>
> not sure - I guess it's a good idea to make sure we're switching to
> modern notebook (7) asap.
>
> >
> > Should we be concerned about these?
> >
> >
> > On Monday, October 9, 2023 at 9:25:44 AM UTC-7 emanuel.c...@gmail.com wrote:
> >>
> >>
> >>
> >> Le lundi 9 octobre 2023 à 18:17:11 UTC+2, Dima Pasechnik a écrit :
> >>
> >> [ Snip... ]
> >>
> >> > The key seems to be “ERROR: Could not find a version that satisfies the 
> >> > requirement hatchling (from versions: none)“, which I do not understand..
> >>
> >> just a missing dependency (hatchling) for attrs.
> >>
> >>
> >> as a hotfix, run
> >>
> >> make hatchling
> >>
> >>
> >> Seems to work... but fails again :
> >>
> >> ```
> >> Processing 
> >> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels/hatch_vcs-0.3.0-py3-none-any.whl
> >> ERROR: Could not find a version that satisfies the requirement 
> >> hatch-fancy-pypi-readme (from versions: none)
> >> ERROR: No matching distribution found for hatch-fancy-pypi-readme
> >> error: subprocess-exited-with-error
> >> ```
> >>
> >> Stuck again...
> >>
> >> [ Re-Snip... ]
> >>
> >>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to sage-release...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/44895efa-3007-441d-ae1c-681d7c314d87n%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/46c0210b-17df-43eb-96c1-87855dd38af2n%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/CAAWYfq3v2_9k1rCVXSDcLFcewZOAOg1UD4OUOvr%2BPXP6GSS%2BWQ%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Oct 9, 2023 at 6:26 PM Emmanuel Charpentier
 wrote:
>
>
>
> Le lundi 9 octobre 2023 à 18:58:13 UTC+2, Dima Pasechnik a écrit :
>
> Ik ken bijna geen Frans, hoor...
> Dat is een grafische dingetje in je mail, niet makkelijk voor automatische 
> vertaling, sorry.
>
>
> Wups ! Sorry for the noise...
>
> Litteral translation :
> ```
> make[1] : entering the « /usr/local/sage-10/build/make » directory
> make[1]: *** No rule to make the « hatch-fancy-pypi-readme » target. Stop.
>  make[1]: Leaving the « /usr/local/sage-10/build/make » directory
> ```
>
sorry, typo

make hatch_fancy_pypi_readme


> HTH,
>
> [ Snip... ]
>
> --
> 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/ea582cff-45ce-4665-9e2e-299da35d4386n%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/CAAWYfq0dsdz02-8wh3gDKKwsRjV%2Br7HPGve41ksdf37Z1%3Dig%3DQ%40mail.gmail.com.

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

[Dima Pasechnik]

Ik ken bijna geen Frans, hoor...
Dat is een grafische dingetje in je mail, niet makkelijk voor automatische
vertaling, sorry.

On Mon, 9 Oct 2023, 17:54 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

> Le lundi 9 octobre 2023 à 18:37:49 UTC+2, Dima Pasechnik a écrit :
>
> well, I'm sure it's the same story, same fix:
>
> make  hatch-fancy-pypi-readme
>
> Nope :
> make[1] : on entre dans le répertoire « /usr/local/sage-10/build/make »
> make[1]: *** Aucune règle pour fabriquer la cible « hatch-fancy-pypi-readme
> ». Arrêt. make[1] : on quitte le répertoire « /usr/local/sage-10/build/make
> »
>
> [ Snip… ]
>
>
> ​
>
> --
> 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/46ca499b-bd2e-4db8-809d-24eebdd8c307n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-release/46ca499b-bd2e-4db8-809d-24eebdd8c307n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAAWYfq3AuwNQGkTsM8XKHzGih9YDMDO6OdjzPL1cegSSBQ5ByQ%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Oct 9, 2023 at 5:39 PM John H Palmieri  wrote:
>
> (I tried to send this last night and I see some indication that the message 
> was deleted, so I'm reposting. Apologies if this has already appeared.)
>
> I see some error message (aside from those already reported) but the build 
> completes anyway. These are probably not new.
>
> In pythran's log:
>
> ERROR: Could not find a version that satisfies the requirement numpy (from 
> pythran) (from versions: none)
> ERROR: No matching distribution found for numpy

numpy is a dependency of pythran, apparently - but it's not listed.

>
> In notebook's log:
>
>   ERROR: Could not find a version that satisfies the requirement 
> jupyter_packaging~=0.9 (from versions: none)
>   ERROR: No matching distribution found for jupyter_packaging~=0.9

not sure - I guess it's a good idea to make sure we're switching to
modern notebook (7) asap.

>
> Should we be concerned about these?
>
>
> On Monday, October 9, 2023 at 9:25:44 AM UTC-7 emanuel.c...@gmail.com wrote:
>>
>>
>>
>> Le lundi 9 octobre 2023 à 18:17:11 UTC+2, Dima Pasechnik a écrit :
>>
>> [ Snip... ]
>>
>> > The key seems to be “ERROR: Could not find a version that satisfies the 
>> > requirement hatchling (from versions: none)“, which I do not understand..
>>
>> just a missing dependency (hatchling) for attrs.
>>
>>
>> as a hotfix, run
>>
>> make hatchling
>>
>>
>> Seems to work...  but fails again :
>>
>> ```
>>   Processing 
>> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels/hatch_vcs-0.3.0-py3-none-any.whl
>>   ERROR: Could not find a version that satisfies the requirement 
>> hatch-fancy-pypi-readme (from versions: none)
>>   ERROR: No matching distribution found for hatch-fancy-pypi-readme
>>   error: subprocess-exited-with-error
>> ```
>>
>> Stuck again...
>>
>> [ Re-Snip... ]
>>
>>
> --
> 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/44895efa-3007-441d-ae1c-681d7c314d87n%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/CAAWYfq2KDfGizLuKO9bQACNjrpntougGyJ6_R0LNaeGHRSskLQ%40mail.gmail.com.

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

[Dima Pasechnik]

well, I'm sure it's the same story, same fix:

make  hatch-fancy-pypi-readme


On Mon, 9 Oct 2023, 17:25 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

>
>
> Le lundi 9 octobre 2023 à 18:17:11 UTC+2, Dima Pasechnik a écrit :
>
> [ Snip... ]
>
> > The key seems to be “ERROR: Could not find a version that satisfies the
> requirement hatchling (from versions: none)“, which I do not understand..
>
> just a missing dependency (hatchling) for attrs.
>
>
> as a hotfix, run
>
> make hatchling
>
>
> Seems to work...  but fails again :
>
> ```
>   Processing
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels/hatch_vcs-0.3.0-py3-none-any.whl
>   ERROR: Could not find a version that satisfies the requirement
> hatch-fancy-pypi-readme (from versions: none)
>   ERROR: No matching distribution found for hatch-fancy-pypi-readme
>   error: subprocess-exited-with-error
> ```
>
> Stuck again...
>
> [ Re-Snip... ]
>
>
> --
> 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/8178c74e-4301-4cb1-afd8-798433d4ae42n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-release/8178c74e-4301-4cb1-afd8-798433d4ae42n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAAWYfq2zrpVxZWB__3LCQqWts-6h500qOObBTR72_Hfba3dOMQ%40mail.gmail.com.

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

[Dima Pasechnik]

to be fixed by https://github.com/sagemath/sage/pull/36434

On Mon, Oct 9, 2023 at 5:16 PM Dima Pasechnik  wrote:
>
> On Mon, Oct 9, 2023 at 5:14 PM Emmanuel Charpentier
>  wrote:
> >
> > On Debian testing running on core i7 + 16 GB RAM :
> >
> > Upgrading (after ./bootstrap ; ./configure ; make -j8 fails to build 
> > sagemath-lib
> >
> > Cleaning, reconfiguring and making fails in the compilatoion of 
> > attrs-23.1.0.tar.gz :
> >
> > Using cached file /usr/local/sage-10/upstream/attrs-23.1.0.tar.gz 
> > attrs-23.1.0  Setting 
> > up build directory for attrs-23.1.0 Finished extraction No patch files 
> > found in ../patches  
> > Host system: Linux zen-book-flip 6.5.0-1-amd64 #1 SMP PREEMPT_DYNAMIC 
> > Debian 6.5.3-1 (2023-09-13) x86_64 GNU/Linux 
> >  C compiler: gcc C 
> > compiler version: Using built-in specs. COLLECT_GCC=gcc 
> > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper 
> > OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 
> > Target: x86_64-linux-gnu Configured with: ../src/configure -v 
> > --with-pkgversion='Debian 13.2.0-4' 
> > --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
> > --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
> > --with-gcc-major-version-only --program-suffix=-13 
> > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
> > --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
> > --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
> > --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> > --with-default-libstdcxx-abi=new --enable-gnu-unique-object 
> > --disable-vtable-verify --enable-plugin --enable-default-pie 
> > --with-system-zlib --enable-libphobos-checking=release 
> > --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
> > --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
> > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
> > --enable-offload-targets=nvptx-none=/build/reproducible-path/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/reproducible-path/gcc-13-13.2.0/debian/tmp-gcn/usr
> >  --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
> > --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu 
> > --with-build-config=bootstrap-lto-lean --enable-link-serialization=3 Thread 
> > model: posix Supported LTO compression algorithms: zlib zstd gcc version 
> > 13.2.0 (Debian 13.2.0-4) 
> >  Package 'attrs' is 
> > currently not installed No legacy uninstaller found for 'attrs'; nothing to 
> > do Installing attrs-23.1.0 Looking in links: 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels 
> > Processing 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/tmp/sage/build/attrs-23.1.0/src
> >  Installing build dependencies: started Running command pip subprocess to 
> > install build dependencies Looking in links: 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels 
> > ERROR: Could not find a version that satisfies the requirement hatchling 
> > (from versions: none) ERROR: No matching distribution found for hatchling 
> > error: subprocess-exited-with-error × pip subprocess to install build 
> > dependencies did not run successfully. │ exit code: 1 ╰─> See above for 
> > output. note: This error originates from a subprocess, and is likely not a 
> > problem with pip. full command: 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/pip/__pip-runner__.py
> >  install --ignore-installed --no-user --prefix 
> > /tmp/pip-build-env-kmfben_t/overlay --no-warn-script-location --no-binary 
> > :none: --only-binary :none: --no-index --find-links 
> > /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels 
> > -- hatchling hatch-vcs hatch-fancy-pypi-readme cwd: [inherit] Installing 
> > build dependencies: finished with status 'error' error: 
> > subprocess-exited-with-error × pip subprocess to install build dependencies 
> > did not run successfully. │ exit code: 1 ╰─> See above for output. note: 
> > This error originates from a subprocess, and is likely not a problem with 
> > pip. Warning: building with "

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

[Dima Pasechnik]

On Mon, Oct 9, 2023 at 5:14 PM Emmanuel Charpentier
 wrote:
>
> On Debian testing running on core i7 + 16 GB RAM :
>
> Upgrading (after ./bootstrap ; ./configure ; make -j8 fails to build 
> sagemath-lib
>
> Cleaning, reconfiguring and making fails in the compilatoion of 
> attrs-23.1.0.tar.gz :
>
> Using cached file /usr/local/sage-10/upstream/attrs-23.1.0.tar.gz 
> attrs-23.1.0  Setting up 
> build directory for attrs-23.1.0 Finished extraction No patch files found in 
> ../patches  Host system: 
> Linux zen-book-flip 6.5.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.3-1 
> (2023-09-13) x86_64 GNU/Linux 
>  C compiler: gcc C 
> compiler version: Using built-in specs. COLLECT_GCC=gcc 
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper 
> OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 
> Target: x86_64-linux-gnu Configured with: ../src/configure -v 
> --with-pkgversion='Debian 13.2.0-4' 
> --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
> --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
> --with-gcc-major-version-only --program-suffix=-13 
> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
> --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
> --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object 
> --disable-vtable-verify --enable-plugin --enable-default-pie 
> --with-system-zlib --enable-libphobos-checking=release 
> --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
> --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
> --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
> --enable-offload-targets=nvptx-none=/build/reproducible-path/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/reproducible-path/gcc-13-13.2.0/debian/tmp-gcn/usr
>  --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
> --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu 
> --with-build-config=bootstrap-lto-lean --enable-link-serialization=3 Thread 
> model: posix Supported LTO compression algorithms: zlib zstd gcc version 
> 13.2.0 (Debian 13.2.0-4)  
> Package 'attrs' is currently not installed No legacy uninstaller found for 
> 'attrs'; nothing to do Installing attrs-23.1.0 Looking in links: 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels 
> Processing 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/tmp/sage/build/attrs-23.1.0/src
>  Installing build dependencies: started Running command pip subprocess to 
> install build dependencies Looking in links: 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels 
> ERROR: Could not find a version that satisfies the requirement hatchling 
> (from versions: none) ERROR: No matching distribution found for hatchling 
> error: subprocess-exited-with-error × pip subprocess to install build 
> dependencies did not run successfully. │ exit code: 1 ╰─> See above for 
> output. note: This error originates from a subprocess, and is likely not a 
> problem with pip. full command: 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/pip/__pip-runner__.py
>  install --ignore-installed --no-user --prefix 
> /tmp/pip-build-env-kmfben_t/overlay --no-warn-script-location --no-binary 
> :none: --only-binary :none: --no-index --find-links 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels -- 
> hatchling hatch-vcs hatch-fancy-pypi-readme cwd: [inherit] Installing build 
> dependencies: finished with status 'error' error: 
> subprocess-exited-with-error × pip subprocess to install build dependencies 
> did not run successfully. │ exit code: 1 ╰─> See above for output. note: This 
> error originates from a subprocess, and is likely not a problem with pip. 
> Warning: building with "python3 -m pip wheel --wheel-dir=dist --verbose 
> --no-deps --no-index --isolated --ignore-requires-python 
> --find-links=/usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/wheels"
>  failed. Retrying with "python3 -m pip wheel --wheel-dir=dist --verbose 
> --no-deps --no-index --isolated --ignore-requires-python --no-build-isolation 
> --no-binary :all:". Processing 
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/tmp/sage/build/attrs-23.1.0/src
>  Preparing metadata (pyproject.toml): started Running command Preparing 
> metadata (pyproject.toml) Preparing metadata (pyproject.toml): finished with 
> status 'done' ERROR: Exception: Traceback 

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

[Dima Pasechnik]

On Sun, Sep 24, 2023 at 5:53 PM John H Palmieri  wrote:
>
> I've already tried uninstalling and reinstalling every homebrew package, and 
> it didn't help.
I meant removing the whole /opt/homebrew/ and reinstalling homebrew
from scratch.


> I've also been doing "make distclean" and "./configure" in between attempts.
>
> I'm confused about your comment about meson_python: I don't think that Sage 
> ordinarily uses a system package of this (except on gentoo?), so it always 
> builds its own. It is using the homebrew installation of meson. I do not have 
> the homebrew meson-python package.

It is (or going to) be available with ./configure --enable-system-site-packages
(after https://github.com/sagemath/sage/pull/36256 and
https://github.com/sagemath/sage/pull/36276)

>
> On Sunday, September 24, 2023 at 3:28:22 AM UTC-7 Dima Pasechnik wrote:
>>
>> both meson and meson_python may potentially come from the system (homebrew 
>> in your case).
>> Make sure they are up to date, and you don't have these packages installed 
>> in Sage.
>> And run ./configure
>>
>> Perhaps the whole homebrew must be reinstated after an OS update, too.
>>
>> On Sun, 24 Sept 2023, 03:07 John H Palmieri,  wrote:
>>>
>>> Building Sage's own gfortran worked to build scipy (and this is an argument 
>>> to keep the gfortran package around, by the way).
>>>
>>> Alternatively, building all of scipy's dependencies and then using `./sage 
>>> --python3 -m pip install scipy` also seems to have worked. I then "touch"ed 
>>> the appropriate file to convince Sage that scipy had built, and the rest of 
>>> the build succeeded, except for some extra warnings during doctests: "ld: 
>>> warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"
>>>
>>> On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:
>>>>
>>>> If by "they" you mean scipy, then: I have no problems building scipy on 
>>>> another OS X machine: an Intel machine running OS X 13.5.2 (rather than 
>>>> 13.6). "xcode-select --version" reports the same for both machines, but I 
>>>> don't know how informative this is. "gfortran --version" says
>>>>
>>>> GNU Fortran (Homebrew GCC 13.2.0) 13.2.0
>>>> Copyright (C) 2023 Free Software Foundation, Inc.
>>>> This is free software; see the source for copying conditions.  There is NO
>>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>>>
>>>> and this is the one that scipy finds. On the M2 machine, Sage's scipy 
>>>> built back in August with earlier versions of the OS (probably 13.5.2) and 
>>>> command-line tools and gfortran (13.1.0).
>>>>
>>>>
>>>> On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>>>>>
>>>>> do they even support gcc/gfortran 13?
>>>>>
>>>>> On Sat, 23 Sept 2023, 23:04 John H Palmieri,  wrote:
>>>>>>
>>>>>> Same result if I do `pip3 install scipy --no-binary scipy` (another of 
>>>>>> their suggested ways of building from source). I guess something is 
>>>>>> broken with my fortran compiler, but I don't know how to troubleshoot it.
>>>>>>
>>>>>> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri 
>>>>>> wrote:
>>>>>>>
>>>>>>> It didn't work for me. At least directly attempting a scipy build left 
>>>>>>> an intact log file. Any clues about what's broken on this machine?
>>>>>>>
>>>>>>> Build started at 2023-09-23T14:31:26.723020
>>>>>>> Main binary: /Users/palmieri/Downloads/scipy-1.11.2/venv/bin/python3
>>>>>>> Build Options: 
>>>>>>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>>>>>>> Python system: Darwin
>>>>>>> The Meson build system
>>>>>>> Version: 1.2.1
>>>>>>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>>>>>>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>>>>>>> Build type: native build
>>>>>>> Project name: SciPy
>>>>>>> Project version: 1.11.2
>>>>>>> ---
>>>>>>> Detecting compiler via: `cc --version` -> 0
>>>>>>> stdout:
>>>>

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

[Dima Pasechnik]

both meson and meson_python may potentially come from the system (homebrew
in your case).
Make sure they are up to date, and you don't have these packages installed
in Sage.
And run ./configure

Perhaps the whole homebrew must be reinstated after an OS update, too.

On Sun, 24 Sept 2023, 03:07 John H Palmieri,  wrote:

> Building Sage's own gfortran worked to build scipy (and this is an
> argument to keep the gfortran package around, by the way).
>
> Alternatively, building all of scipy's dependencies and then using `./sage
> --python3 -m pip install scipy` also seems to have worked. I then "touch"ed
> the appropriate file to convince Sage that scipy had built, and the rest of
> the build succeeded, except for some extra warnings during doctests: "ld:
> warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"
>
> On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:
>
>> If by "they" you mean scipy, then: I have no problems building scipy on
>> another OS X machine: an Intel machine running OS X 13.5.2 (rather than
>> 13.6). "xcode-select --version" reports the same for both machines, but I
>> don't know how informative this is. "gfortran --version" says
>>
>> GNU Fortran (Homebrew GCC 13.2.0) 13.2.0
>> Copyright (C) 2023 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> and this is the one that scipy finds. On the M2 machine, Sage's scipy
>> built back in August with earlier versions of the OS (probably 13.5.2) and
>> command-line tools and gfortran (13.1.0).
>>
>>
>> On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
>>
>>> do they even support gcc/gfortran 13?
>>>
>>> On Sat, 23 Sept 2023, 23:04 John H Palmieri, 
>>> wrote:
>>>
>>>> Same result if I do `pip3 install scipy --no-binary scipy` (another of
>>>> their suggested ways of building from source). I guess something is broken
>>>> with my fortran compiler, but I don't know how to troubleshoot it.
>>>>
>>>> On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri
>>>> wrote:
>>>>
>>>>> It didn't work for me. At least directly attempting a scipy build left
>>>>> an intact log file. Any clues about what's broken on this machine?
>>>>>
>>>>> Build started at 2023-09-23T14:31:26.723020
>>>>> Main binary: /Users/palmieri/Downloads/scipy-1.11.2/venv/bin/python3
>>>>> Build Options:
>>>>> -Dprefix=/Users/palmieri/Downloads/scipy-1.11.2/build-install
>>>>> Python system: Darwin
>>>>> The Meson build system
>>>>> Version: 1.2.1
>>>>> Source dir: /Users/palmieri/Downloads/scipy-1.11.2
>>>>> Build dir: /Users/palmieri/Downloads/scipy-1.11.2/build
>>>>> Build type: native build
>>>>> Project name: SciPy
>>>>> Project version: 1.11.2
>>>>> ---
>>>>> Detecting compiler via: `cc --version` -> 0
>>>>> stdout:
>>>>> Apple clang version 15.0.0 (clang-1500.0.40.1)
>>>>> Target: arm64-apple-darwin22.6.0
>>>>> Thread model: posix
>>>>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>>>> ---
>>>>> Running command: cc -E -dM -
>>>>> -
>>>>> ---
>>>>> Detecting linker via: `cc -Wl,--version` -> 1
>>>>> stderr:
>>>>> ld: unknown options: --version
>>>>> clang: error: linker command failed with exit code 1 (use -v to see
>>>>> invocation)
>>>>> ---
>>>>> ---
>>>>> Detecting Apple linker via: `cc -Wl,-v` -> 1
>>>>> stderr:
>>>>> @(#)PROGRAM:ld  PROJECT:dyld-1015.7
>>>>> BUILD 18:48:48 Aug 22 2023
>>>>> configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32
>>>>> i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
>>>>> will use ld-classic for: armv6 armv7 armv7s arm64_32 i386 armv6m
>>>>> armv7k armv7m armv7em
>>>>> LTO support using: LLVM version 15.0.0 (static support for 29, runtime
>>>>> is 29)
>>>>> TAPI support using: Apple TAPI version 15.0.0 (tapi-1500.0.12.3)
>>>>> Library search paths:
>>>>

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

[Dima Pasechnik]

 return 0; }
>>
>> ---
>> Command line: `cc
>> /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/tmp__jom5wq/testfile.c
>> -o
>> /Users/palmieri/Downloads/scipy-1.11.2/build/meson-private/tmp__jom5wq/output.exe
>> -O0 -Werror=implicit-function-declaration -lm
>> -Wl,-undefined,dynamic_lookup` -> 0
>> Library m found: YES
>> ---
>> Detecting compiler via: `gfortran --version` -> 0
>> stdout:
>> GNU Fortran (Homebrew GCC 13.2.0) 13.2.0
>> Copyright (C) 2023 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>> ---
>> Running command: gfortran -E -dM -
>> -
>> ---
>> Detecting linker via: `gfortran -Wl,--version` -> 1
>> stderr:
>> collect2 version 13.2.0
>> /usr/bin/ld -syslibroot
>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
>> -platform_version macos 13.0.0 0.0 -o a.out
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>> -L/opt/homebrew/lib
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>> --version -lemutls_w -lgcc -lSystem -lgcc -no_compact_unwind -rpath
>> @loader_path -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>
>> ld: unknown options: --version
>> collect2: error: ld returned 1 exit status
>> ---
>>
>> meson.build:82:0: ERROR: Unable to detect linker for compiler `gfortran
>> -Wl,--version`
>>
>> stdout:
>> stderr: collect2 version 13.2.0
>> /usr/bin/ld -syslibroot
>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
>> -platform_version macos 13.0.0 0.0 -o a.out
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>> -L/opt/homebrew/lib
>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>> --version -lemutls_w -lgcc -lSystem -lgcc -no_compact_unwind -rpath
>> @loader_path -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>
>> ld: unknown options: --version
>> collect2: error: ld returned 1 exit status
>>
>>
>>
>> On Saturday, September 23, 2023 at 11:06:06 AM UTC-7 Dima Pasechnik wrote:
>>
>>> As far as I can gather from scipy bug tracker,
>>> they can build on M2 just fine
>>> https://github.com/scipy/scipy/issues/18308
>>>
>>>
>>> On Sat, 23 Sept 2023, 18:07 John H Palmieri, 
>>> wrote:
>>>
>>>> This is with an Apple Silicon laptop, M2 chip, in case that matters.
>>>>
>>>> On Saturday, September 23, 2023 at 10:06:36 AM UTC-7 John H Palmieri
>>>> wrote:
>>>>
>>>>> I tried the venv approach in the scipy docs, and I ran into the same
>>>>> error.
>>>>>
>>>>> On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima Pasechnik
>>>

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

[Dima Pasechnik]

As far as I can gather from scipy bug tracker,
they can build on M2 just fine
https://github.com/scipy/scipy/issues/18308


On Sat, 23 Sept 2023, 18:07 John H Palmieri,  wrote:

> This is with an Apple Silicon laptop, M2 chip, in case that matters.
>
> On Saturday, September 23, 2023 at 10:06:36 AM UTC-7 John H Palmieri wrote:
>
>> I tried the venv approach in the scipy docs, and I ran into the same
>> error.
>>
>> On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima Pasechnik wrote:
>>
>>> Can you build scipy from source using their instructions?
>>>
>>> On Sat, 23 Sept 2023, 06:25 John H Palmieri, 
>>> wrote:
>>>
>>>> It's from homebrew's gcc. I did `brew reinstall gcc` followed by `make
>>>> distclean && ./configure && make meson_python && make` and it still fails
>>>> at scipy, same error. I removed the cached download file for homebrew's gcc
>>>> and tried again, same result. I have not yet tried Sage's gcc.
>>>>
>>>> On Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik
>>>> wrote:
>>>>
>>>>> Where is gfortran coming from here?
>>>>> Do you build it with Sage, or use an external one?
>>>>>
>>>>> If the external one, e.g. from Homebrew, you most probably need to
>>>>> update/reinstall.
>>>>> Ditto in Sage
>>>>>
>>>>>
>>>>> On Fri, 22 Sept 2023, 00:52 John H Palmieri, 
>>>>> wrote:
>>>>>
>>>>>> A new problem, after upgrading to OS X 13.6 and the newest version of
>>>>>> the command-line tools: scipy fails to build again, this time with the
>>>>>> error:
>>>>>>
>>>>>>   ../../meson.build:82:0: ERROR: Unable to detect linker for compiler
>>>>>> `gfortran -Wl,--version
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>>>>>>   stdout:
>>>>>>   stderr: collect2 version 13.2.0
>>>>>>   /usr/bin/ld -syslibroot
>>>>>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch 
>>>>>> arm64
>>>>>> -platform_version macos 13.0.0 0.0 -o a.out
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>>>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>>>>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>>>>>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>>>>>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>>>>>> -L/opt/homebrew/lib
>>>>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>>>>>> --version -rpath
>>>>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>>>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
>>>>>> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
>>>>>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>>>>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>>>>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>>>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>>>>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>>>>>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>>>>>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>>>>>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>>>>>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>>>>>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>>>>>> /opt/ho

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

[Dima Pasechnik]

Can you build scipy from source using their instructions?

On Sat, 23 Sept 2023, 06:25 John H Palmieri,  wrote:

> It's from homebrew's gcc. I did `brew reinstall gcc` followed by `make
> distclean && ./configure && make meson_python && make` and it still fails
> at scipy, same error. I removed the cached download file for homebrew's gcc
> and tried again, same result. I have not yet tried Sage's gcc.
>
> On Thursday, September 21, 2023 at 11:18:15 PM UTC-7 Dima Pasechnik wrote:
>
>> Where is gfortran coming from here?
>> Do you build it with Sage, or use an external one?
>>
>> If the external one, e.g. from Homebrew, you most probably need to
>> update/reinstall.
>> Ditto in Sage
>>
>>
>> On Fri, 22 Sept 2023, 00:52 John H Palmieri,  wrote:
>>
>>> A new problem, after upgrading to OS X 13.6 and the newest version of
>>> the command-line tools: scipy fails to build again, this time with the
>>> error:
>>>
>>>   ../../meson.build:82:0: ERROR: Unable to detect linker for compiler
>>> `gfortran -Wl,--version
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>>>   stdout:
>>>   stderr: collect2 version 13.2.0
>>>   /usr/bin/ld -syslibroot
>>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
>>> -platform_version macos 13.0.0 0.0 -o a.out
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
>>> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
>>> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
>>> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
>>> -L/opt/homebrew/lib
>>> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
>>> --version -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
>>> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
>>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
>>> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
>>> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
>>> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
>>> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
>>> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
>>> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
>>> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
>>> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>>>   ld: unknown options: --version
>>>   collect2: error: ld returned 1 exit status
>>>
>>> Suggestions?
>>>
>>> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 John H Palmieri wrote:
>>>
>>>> Similar problem for me on OS X. I don't understand something: the
>>>> dependencies for scipy include meson_python, but that package is not
>>>> installed before scipy attempts to build, and fails. Running "make
>>>> meson_python" and then "make scipy" succeeds, as does "make".
>>>>
>>>>
>>>>
>>>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>>>
>>>>> Succeeded after sage -pip install meson-python.
>>>>>
>>>>> On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
>>>>>
>>>>>> Incremental build failed
>>>>>>
>>>>>> [scipy-1.11.2]
>>>>>> [..]
>>>>>> [scipy-1.11.2] scipy-1.11.2
>>>>>> [scipy-1.11.2] 

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

[Dima Pasechnik]

Where is gfortran coming from here?
Do you build it with Sage, or use an external one?

If the external one, e.g. from Homebrew, you most probably need to
update/reinstall.
Ditto in Sage


On Fri, 22 Sept 2023, 00:52 John H Palmieri,  wrote:

> A new problem, after upgrading to OS X 13.6 and the newest version of the
> command-line tools: scipy fails to build again, this time with the error:
>
>   ../../meson.build:82:0: ERROR: Unable to detect linker for compiler
> `gfortran -Wl,--version
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -Wl,-rpath,/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib`
>   stdout:
>   stderr: collect2 version 13.2.0
>   /usr/bin/ld -syslibroot
> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/ -dynamic -arch arm64
> -platform_version macos 13.0.0 0.0 -o a.out
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib
> -L/opt/homebrew/opt/primesieve/lib -L/opt/homebrew/opt/bdw-gc/lib
> -L/opt/homebrew/opt/libpng/lib -L/opt/homebrew/opt/ntl/lib
> -L/opt/homebrew/opt/bzip2/lib -L/opt/homebrew/opt/readline/lib
> -L/opt/homebrew/lib
> -L/opt/homebrew/Cellar/gcc/13.2.0/bin/../lib/gcc/current/gcc/aarch64-apple-darwin22/13/../../..
> --version -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -lemutls_w
> -lgcc -lSystem -lgcc -no_compact_unwind -rpath @loader_path -rpath
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc/aarch64-apple-darwin22/13
> -rpath /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/gcc -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /Users/palmieri/Desktop/Sage/TESTING/sage-10.2.beta3/local/lib -rpath
> /opt/homebrew/Cellar/primesieve/11.1/lib -rpath
> /opt/homebrew/Cellar/bdw-gc/8.2.4/lib -rpath
> /opt/homebrew/Cellar/libpng/1.6.40/lib -rpath
> /opt/homebrew/Cellar/ntl/11.5.1/lib -rpath
> /opt/homebrew/Cellar/bzip2/1.0.8/lib -rpath
> /opt/homebrew/Cellar/readline/8.2.1/lib -rpath /opt/homebrew/lib -rpath
> /opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current
>   ld: unknown options: --version
>   collect2: error: ld returned 1 exit status
>
> Suggestions?
>
> On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 John H Palmieri wrote:
>
>> Similar problem for me on OS X. I don't understand something: the
>> dependencies for scipy include meson_python, but that package is not
>> installed before scipy attempts to build, and fails. Running "make
>> meson_python" and then "make scipy" succeeds, as does "make".
>>
>>
>>
>> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>
>>> Succeeded after sage -pip install meson-python.
>>>
>>> On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
>>>
 Incremental build failed

 [scipy-1.11.2]
 [..]
 [scipy-1.11.2] scipy-1.11.2
 [scipy-1.11.2] 
 [sagelib-10.2.beta3]   Removing file or directory
 /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
 [sagelib-10.2.beta3]   Removing pth entries from
 /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
 [sagelib-10.2.beta3]   Removing entry:
 /Users/kwankyu/GitHub/sage-dev/src
 [sagelib-10.2.beta3]   Successfully uninstalled
 sagemath-standard-10.2b3
 [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
 [sagelib-10.2.beta3] Running command python setup.py develop
 [scipy-1.11.2] Setting up build directory for scipy-1.11.2
 [scipy-1.11.2] Finished extraction
 [scipy-1.11.2] Applying patches from ../patches...
 [scipy-1.11.2] Applying ../patches/numpy-include.patch
 [scipy-1.11.2] patching file scipy/spatial/setup.py
 [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
 [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
 [scipy-1.11.2] patching file scipy/datasets/meson.build
 [scipy-1.11.2] 
 [scipy-1.11.2] Host system:
 [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0:
 Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
 [scipy-1.11.2] 

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

[Dima Pasechnik]

run

make pytest

(or ./sage -i pytest)

to install it and have it ready for Sage.
(i.e. install it into Sage's venv)

On Mon, Sep 18, 2023 at 9:04 AM John Cremona  wrote:
>
> What should I do to avoid this message when running "make testlong":
>
> pytest is not installed in the venv, skip checking tests that rely on it
>
> i.e. how should I install pytest.  System-wide or what?
>
> John
>
> On Mon, 18 Sept 2023 at 01:08, Matthias Köppe  
> wrote:
>>
>> I've pushed a fix to https://github.com/sagemath/sage/pull/36276
>>
>> On Sunday, September 17, 2023 at 5:02:05 PM UTC-7 Matthias Köppe wrote:
>>>
>>> Yes, it's a bug in the build system. Running  CONFIG_SHELL="bash -x" 
>>> ./configure
>>>
>>> + printf '%s\n' 'configure:49868: result: no; skipping check'
>>> + printf '%s\n' 'no; skipping check'
>>> + sage_spkg_install_meson-python=yes
>>> ./configure: line 49870: sage_spkg_install_meson-python=yes: command not 
>>> found
>>> + test yes = yes
>>> + :
>>> + sage_use_system_meson-python=no
>>> ./configure: line 49874: sage_use_system_meson-python=no: command not found
>>> + test xno = xno
>>> + :
>>> + sage_use_system_meson_python=yes
>>> + printf '%s\n' 'configure:49884: will use system package and not install 
>>> SPKG meson_python'
>>> + printf '%s\n' 'configure: will use system package and not install SPKG 
>>> meson_python'
>>> +
>>>
>>> On Sunday, September 17, 2023 at 1:34:35 PM UTC-7 Dima Pasechnik wrote:
>>>>
>>>>
>>>>
>>>> On Sun, Sep 17, 2023 at 7:25 PM John H Palmieri  
>>>> wrote:
>>>> >
>>>> > Similar problem for me on OS X. I don't understand something: the 
>>>> > dependencies for scipy include meson_python, but that package is not 
>>>> > installed before scipy attempts to build, and fails. Running "make 
>>>> > meson_python" and then "make scipy" succeeds, as does "make".
>>>>
>>>> $ cat build/pkgs/scipy/dependencies
>>>>  $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN) 
>>>> meson_python $(PYTHON)
>>>>
>>>> looks OK. So this looks like a bug in our build system
>>>>
>>>>
>>>> >
>>>> >
>>>> >
>>>> > On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>>> >>
>>>> >> Succeeded after sage -pip install meson-python.
>>>> >>
>>>> >> On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
>>>> >>>
>>>> >>> Incremental build failed
>>>> >>>
>>>> >>> [scipy-1.11.2] 
>>>> >>> [..]
>>>> >>> [scipy-1.11.2] scipy-1.11.2
>>>> >>> [scipy-1.11.2] 
>>>> >>> [sagelib-10.2.beta3]   Removing file or directory 
>>>> >>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>>>> >>> [sagelib-10.2.beta3]   Removing pth entries from 
>>>> >>> /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>>>> >>> [sagelib-10.2.beta3]   Removing entry: 
>>>> >>> /Users/kwankyu/GitHub/sage-dev/src
>>>> >>> [sagelib-10.2.beta3]   Successfully uninstalled 
>>>> >>> sagemath-standard-10.2b3
>>>> >>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>>>> >>> [sagelib-10.2.beta3] Running command python setup.py develop
>>>> >>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>>>> >>> [scipy-1.11.2] Finished extraction
>>>> >>> [scipy-1.11.2] Applying patches from ../patches...
>>>> >>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>>>> >>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>>>> >>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>>>> >>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
>>>> >>> [scipy-1.11.2] patching file scipy/datasets/meson

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

[Dima Pasechnik]

On Sun, Sep 17, 2023 at 7:25 PM John H Palmieri 
wrote:
>
> Similar problem for me on OS X. I don't understand something: the
dependencies for scipy include meson_python, but that package is not
installed before scipy attempts to build, and fails. Running "make
meson_python" and then "make scipy" succeeds, as does "make".

$ cat build/pkgs/scipy/dependencies
 $(BLAS) gfortran numpy pybind11 cython pythran | $(PYTHON_TOOLCHAIN)
meson_python $(PYTHON)

looks OK. So this looks like a bug in our build system

>
>
>
> On Saturday, September 16, 2023 at 2:59:58 PM UTC-7 Kwankyu Lee wrote:
>>
>> Succeeded after sage -pip install meson-python.
>>
>> On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
>>>
>>> Incremental build failed
>>>
>>> [scipy-1.11.2]
[..]
>>> [scipy-1.11.2] scipy-1.11.2
>>> [scipy-1.11.2] 
>>> [sagelib-10.2.beta3]   Removing file or directory
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link
>>> [sagelib-10.2.beta3]   Removing pth entries from
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth:
>>> [sagelib-10.2.beta3]   Removing entry:
/Users/kwankyu/GitHub/sage-dev/src
>>> [sagelib-10.2.beta3]   Successfully uninstalled
sagemath-standard-10.2b3
>>> [sagelib-10.2.beta3]   Running setup.py develop for sagemath-standard
>>> [sagelib-10.2.beta3] Running command python setup.py develop
>>> [scipy-1.11.2] Setting up build directory for scipy-1.11.2
>>> [scipy-1.11.2] Finished extraction
>>> [scipy-1.11.2] Applying patches from ../patches...
>>> [scipy-1.11.2] Applying ../patches/numpy-include.patch
>>> [scipy-1.11.2] patching file scipy/spatial/setup.py
>>> [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines).
>>> [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch
>>> [scipy-1.11.2] patching file scipy/datasets/meson.build
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] Host system:
>>> [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0:
Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] C compiler: gcc
>>> [scipy-1.11.2] C compiler version:
>>> [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1)
>>> [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0
>>> [scipy-1.11.2] Thread model: posix
>>> [scipy-1.11.2] InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>> [scipy-1.11.2] 
>>> [scipy-1.11.2] Package 'scipy' is currently not installed
>>> [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do
>>> [scipy-1.11.2] Installing scipy-1.11.2
>>> [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading from
the cache of locally built wheels. In the future --no-binary will not
influence the wheel cache. pip 23.1 will enforce this behaviour change. A
possible replacement is to use the --no-cache-dir option. You can use the
flag --use-feature=no-binary-enable-wheel-cache to test the upcoming
behaviour. Discussion can be found at
https://github.com/pypa/pip/issues/11453
>>> [scipy-1.11.2] Processing
/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src
>>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): started
>>> [scipy-1.11.2]   Running command Preparing metadata (pyproject.toml)
>>> [scipy-1.11.2]   Preparing metadata (pyproject.toml): finished with
status 'done'
>>> [scipy-1.11.2] ERROR: Exception:
>>> [scipy-1.11.2] Traceback (most recent call last):
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/base_command.py",
line 160, in exc_logging_wrapper
>>> [scipy-1.11.2] status = run_func(*args)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/req_command.py",
line 247, in wrapper
>>> [scipy-1.11.2] return func(self, options, args)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/commands/wheel.py",
line 170, in run
>>> [scipy-1.11.2] requirement_set = resolver.resolve(reqs,
check_supported_wheels=True)
>>> [scipy-1.11.2]   File
"/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py",
line 73, in resolve
>>> [scipy-1.11.2] collected =
self.factory.collect_root_requirements(root_reqs)
>>> [scipy-1.11.2]   File

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

[Dima Pasechnik]

On Mon, 14 Aug 2023, 17:10 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

>
>
> Le lundi 14 août 2023 à 14:03:31 UTC+2, Dima Pasechnik a écrit :
>
> [ Snip... ]
>
> Discounting for the moment the obvious workaround ./configure
> --with-system-arb=no, what can be done ?
>
>
> Do you mean to say that an update to the system arb does not cause a
> rebuild of sagelib?
> (otherwise, what's inconsistent?)
>
>
> I can't certify that system's `arb` has been updated ; it's jut a
> possibility.
>

Why have you expected a rebuild of sagelib?
If no Cython has been touched, and no deps updated, there's no reason for
it.



> That's obviously not being checked, and there is no easy way to do this,
> either.
>
> Yes, system updates are tricky.
>
>   make sagelib-clean sagelib-uninstall
>
> will help.
>
>
>
> It *did* helo. Thank you !
>
> `ptestlong` underway...
>
>
> --
> 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/a80e100d-8286-4bd0-83e6-4cd12edc077bn%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-release/a80e100d-8286-4bd0-83e6-4cd12edc077bn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAAWYfq3PwzSfve%2Bt9UetANn8dV01dd8MT_aJURt7n4XvDALmHQ%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, 14 Aug 2023, 09:57 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

> ./configure is inconsistent when handling arb detection. I do have
> system’s libraries :
> charpent@zen-book-flip:/usr/local/sage-10$ dpkg -l "*arb*"
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder |
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=att>
> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/
> Nom Version Architecture Description
> +++-==-=--=>
> ii libflint-arb-dev:amd64 1:2.23.0-1+b1 amd64 C library for arbitrary-p> un
> libflint-arb-doc   (aucune description n'est> ii
> libflint-arb2:amd64 1:2.23.0-1+b1 amd64 C library for arbitrary-p
>
> However, ./configure gives inconsistent resulys. From config.log :
> ##  ## ## Checking
> whether SageMath should install SPKG arb... ## ##
>  ## configure:15898:
> checking installing flint? configure:15905: checking for arb.h
> configure:15905: g++ -std=gnu++11 -c conftest.cpp >&5 configure:15905: $? =
> 0 configure:15905: result: yes configure:15909: checking for
> acb_mat_eig_simple in -larb configure:15931: g++ -std=gnu++11 -o conftest
> conftest.cpp -larb -lflint -lmpfr -lglpk -lgmp -lm -lntl >&5 /usr/bin/ld:
> cannot find -larb: No such file or directory collect2: error: ld returned 1
> exit status configure:15931: $? = 1 configure: failed program was: | /*
> confdefs.h */ | #define PACKAGE_NAME "Sage" | #define PACKAGE_TARNAME
> "sage" | #define PACKAGE_VERSION "10.1.rc0" | #define PACKAGE_STRING "Sage
> 10.1.rc0" | #define PACKAGE_BUGREPORT "sage-de...@googlegroups.com" |
> #define PACKAGE_URL "" | #define PACKAGE "sage" | #define VERSION
> "10.1.rc0" | #define HAVE_STDIO_H 1 | #define HAVE_STDLIB_H 1 | #define
> HAVE_STRING_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 |
> #define HAVE_STRINGS_H 1 | #define HAVE_SYS_STAT_H 1 | #define
> HAVE_SYS_TYPES_H 1 | #define HAVE_UNISTD_H 1 | #define STDC_HEADERS 1 |
> #define HAVE_LIBM 1 | #define HAVE_CXX11 1 | #define HAVE_GMP_H 1 | #define
> ABSOLUTE_GMP_H "///usr/include/x86_64-linux-gnu/gmp.h" | #define
> HAVE_NTL_ZZ_H 1 | #define ABSOLUTE_NTL_ZZ_H "///usr/include/NTL/ZZ.h" | /*
> end confdefs.h. */ | | namespace conftest { | extern "C" int
> acb_mat_eig_simple (); | } | int | main (void) | { | return
> conftest::acb_mat_eig_simple (); | ; | return 0; | } configure:15941:
> result: no configure:15950: checking for acb_mat_eig_simple in -lflint-arb
> configure:15972: g++ -std=gnu++11 -o conftest conftest.cpp -lflint-arb
> -lflint -lmpfr -lglpk -lgmp -lm -lntl >&5 configure:15972: $? = 0
> configure:15982: result: yes configure:16004: will use system package and
> not install SPKG arb
>
> As a result, sagelib isn’t built.
>
> Discounting for the moment the obvious workaround ./configure
> --with-system-arb=no, what can be done ?
>

Do you mean to say that an update to the system arb does not cause a
rebuild of sagelib?
(otherwise, what's inconsistent?)


That's obviously not being checked, and there is no easy way to do this,
either.

Yes, system updates are tricky.

  make sagelib-clean sagelib-uninstall

will help.




​
> Le dimanche 13 août 2023 à 19:31:15 UTC+2, 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
>>
>> aa220c4a1e3 (tag: 10.1.rc0, github/develop) Updated SageMath version to
>> 10.1.rc0
>> 50208b76199 gh-36077: `sage.graphs`: fix doctest warnings due to
>> modularization
>> 2b22924ded5 gh-36076: Remove deprecated parameter circular from method
>> `is_planar`
>> a00ac4f5a5c gh-36075: Remove rename warning in spanning_tree.pyx
>> 35ac035e0eb gh-36074: Remove deprecation warnings renaming parameter
>> verbosity to verbose in graphs
>> 32d375d23ce gh-36073: Stop sorting Graph vertices and edges by default
>> 1e6cd50d88d gh-36072: small cleanup of triangulation/base.pyx
>> ddcfc9afe34 gh-36068: Speed-up matrix construction by ensuring MatrixArgs
>> type MA_ENTRIES_ZERO
>> caf98de404c gh-36066: Fix link to tutorial in PDF docs. This fixes #35736.
>> 517cdce8d9b gh-36062: Fix typo in docstring
>> d6c6f621891 gh-36056: `sage.rings.finite_rings`: Modularization fixes, `#
>> needs`
>> 03dec7d1d7a gh-36052: `sage.rings.{padics,valuation}`: Modularization
>> fixes, `# needs`
>> afb74af1e6f gh-36051: `sage.{topology,homology}`: Update # needs,
>> modularization fixes
>> ba7d11896cf gh-36045: `sage.rings.polynomial`: Modularization fixes, `#
>> needs`
>> a38d1298dd2 gh-36044: `sage.rings.number_field`: Modularization fixes,
>> doctest cosmetics, `# needs`
>> 11751dccdb9 gh-36040: Fix failing doctest in sage/graphs/bliss.pyx
>> a023470b2a5 gh-36039: cylint: some details in arith, algebras and crypto
>> folders
>> 

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

[Dima Pasechnik]

On Tue, Aug 1, 2023 at 10:08 PM Emmanuel Charpentier
 wrote:
>
>
>
> Le mardi 1 août 2023 à 22:54:19 UTC+2, Dima Pasechnik a écrit :
>
> [ Snip... ]
>
> > a few permanent errors :
> >
> > ** File 
> > "src/sage/graphs/generators/classical_geometries.py", line 1268, in 
> > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> > example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> > (grape) Exception raised: Traceback (most recent call last): File 
> > "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> > self.compile_and_execute(example, compiler, test.globs) File 
> > "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> > compile_and_execute exec(compiled, globs) File " > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[1]>", 
> > line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> > gap_packages (grape) ^ NameError: name 'G' is not defined 
> > ** File 
> > "src/sage/graphs/generators/classical_geometries.py", line 1274, in 
> > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> > example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> > (grape) Exception raised: Traceback (most recent call last): File 
> > "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> > self.compile_and_execute(example, compiler, test.globs) File 
> > "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> > compile_and_execute exec(compiled, globs) File " > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[3]>", 
> > line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> > gap_packages (grape) ^ NameError: name 'G' is not defined 
> > ** File 
> > "src/sage/graphs/generators/classical_geometries.py", line 1280, in 
> > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> > example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> > (grape) # long time Exception raised: Traceback (most recent call last): 
> > File "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> > self.compile_and_execute(example, compiler, test.globs) File 
> > "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> > compile_and_execute exec(compiled, globs) File " > sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[5]>", 
> > line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> > gap_packages (grape) # long time ^ NameError: name 'G' is not defined 
> > **
> >
> > These three seems genuine.
>
> looks like an # optional tagging issue.
> Do you have gap_packages installed?
>
>
> Yep ! (4.12.2).

OK, it's actually mangled doctests - 'G' was accidentally renamed to
'g' in 94bca97cfe9


@@ -1259,20 +1264,20 @@ def CossidentePenttilaGraph(q):

 For `q=3` one gets Sims-Gewirtz graph. ::

-sage: G=graphs.CossidentePenttilaGraph(3) # optional -
gap_packages (grape)
-sage: G.is_strongly_regular(parameters=True)  # optional -
gap_packages (grape)
+sage: g = graphs.CossidentePenttilaGraph(3) # optional -
gap_packages (grape)
+sage: G.is_strongly_regular(parameters=True)# optional -
gap_packages (grape)
 (56, 10, 0, 2)

 For `q>3` one gets new graphs. ::

-sage: G=graphs.CossidentePenttilaGraph(5) # optional -
gap_packages (grape)
-sage: G.is_strongly_regular(parameters=True)  # optional -
gap_packages (grape)
+sage: g = graphs.CossidentePenttilaGraph(5) # optional -
gap_packages (grape)
+sage: G.is_strongly_regular(parameters=True)# optional -
gap_packages (grape)
 (378, 52, 1, 8)

 TESTS::

-sage: G=graphs.CossidentePenttilaGraph(7) # optional -
gap_packages (grape) # long time
-sage: G.is_strongly_regular(parameters=True)  # optional -
gap_packages (grape) # long time
+sage: g = graphs.CossidentePenttilaGraph(7) # optional -
gap_packages (grape) # long time
+sage: G.is_strongly_regular(parameters=True)# optional -
gap_packages (grape) # long time
 (1376, 150, 2, 18)
 sage: graphs.CossidentePenttilaGraph(2)
 Traceback (most recent call last):


fix in https://github.com/sagemath/sage/pull/36017
&g

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

[Dima Pasechnik]

On Tue, Aug 1, 2023 at 9:46 PM Emmanuel Charpentier
 wrote:
>
> Le mardi 1 août 2023 à 22:00:00 UTC+2, matthia…@gmail.com a écrit :
>
> cvxopt may be installed systemwide, but Sage does not use Python packages 
> from the system.
>
> "make cvxopt-uninstall cvxopt" should fix the problem
>
> Indeeed. Except that you neeed make cvxopt-uninstall ; make cvxopt… Thank you 
> Matthias !
>
> The cvxopt errors disappeared. Hwever, I still have
>
> a (metric) tonne of Warnings related to the modularization of doctests,
>
> a few permanent errors :
>
> ** File 
> "src/sage/graphs/generators/classical_geometries.py", line 1268, in 
> sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> (grape) Exception raised: Traceback (most recent call last): File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> self.compile_and_execute(example, compiler, test.globs) File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> compile_and_execute exec(compiled, globs) File " sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[1]>", 
> line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> gap_packages (grape) ^ NameError: name 'G' is not defined 
> ** File 
> "src/sage/graphs/generators/classical_geometries.py", line 1274, in 
> sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> (grape) Exception raised: Traceback (most recent call last): File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> self.compile_and_execute(example, compiler, test.globs) File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> compile_and_execute exec(compiled, globs) File " sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[3]>", 
> line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> gap_packages (grape) ^ NameError: name 'G' is not defined 
> ** File 
> "src/sage/graphs/generators/classical_geometries.py", line 1280, in 
> sage.graphs.generators.classical_geometries.CossidentePenttilaGraph Failed 
> example: G.is_strongly_regular(parameters=True) # optional - gap_packages 
> (grape) # long time Exception raised: Traceback (most recent call last): File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 709, in _run 
> self.compile_and_execute(example, compiler, test.globs) File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 1144, in 
> compile_and_execute exec(compiled, globs) File " sage.graphs.generators.classical_geometries.CossidentePenttilaGraph[5]>", 
> line 1, in  G.is_strongly_regular(parameters=True) # optional - 
> gap_packages (grape) # long time ^ NameError: name 'G' is not defined 
> **
>
> These three seems genuine.

looks like an # optional tagging issue.
Do you have gap_packages installed?



>
> File "src/sage/coding/linear_code.py", line 913, in 
> sage.coding.linear_code.AbstractLinearCode.covering_radius Failed example: 
> C.covering_radius() # optional - gap_packages (Guava package) Expected: ... 1 
> Got: 1 ** 
> File "src/sage/coding/linear_code.py", line 1377, in 
> sage.coding.linear_code.AbstractLinearCode.minimum_distance Failed example: 
> C.minimum_distance(algorithm="guava") # optional - gap_packages (Guava 
> package) Expected: ... 3 Got: 3 
> **
>
> Probably cosmetic.
>
> File "src/sage/combinat/posets/posets.py", line 1371, in 
> sage.combinat.posets.posets.FinitePoset._latex_ Failed example: 
> print(P._latex_()) # optional - dot2tex graphviz Expected: 
> \begin{tikzpicture}[>=latex,line join=bevel,] %% \node (node_...) at 
> (5...bp,...bp) [draw,draw=none] {$...$}; \node (node_...) at (5...bp,...bp) 
> [draw,draw=none] {$...$}; \draw [black,->] (node_...) ..controls 
> (...bp,...bp) and (...bp,...bp) .. (node_...); % \end{tikzpicture} Got: 
> \begin{tikzpicture}[>=latex,line join=bevel,] %% \node (node_0) at 
> (6.0bp,6.5bp) [draw,draw=none] {$1$}; \node (node_1) at (6.0bp,55.5bp) 
> [draw,draw=none] {$2$}; \draw [black,->] (node_0) ..controls (6.0bp,19.603bp) 
> and (6.0bp,30.062bp) .. (node_1); % \end{tikzpicture} 
> **
>
> Possibly numerical noise.
>
> File "src/sage/coding/code_constructions.py", line 734, in 
> sage.coding.code_constructions.ToricCode Failed example: 
> C.minimum_distance(algorithm="guava") # optional - gap_packages (Guava 
> package) Expected: ... 24 Got: 24
>
> Probably 

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

[Dima Pasechnik]

On Tue, Aug 1, 2023 at 11:54 AM Emmanuel Charpentier
 wrote:
>
> On Debian testing, upgarding 10.1.beta7 to 10.1.beta8 and running prestlong 
> gave a raft of new failures :
>
> -- sage 
> -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 src/sage/doctest/test.py 
> # 1 doctest failed # Passes standalone sage -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 
> src/sage/graphs/generators/classical_geometries.py # 3 doctests failed # 
> Permanent sage -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 
> src/sage/combinat/posets/posets.py # 1 doctest failed # Permanent sage -t 
> --long --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/matrix/matrix2.pyx # 2 doctests failed # Permanent sage -t --long 
> --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/coding/linear_code.py # 2 doctests failed # Permanent sage -t --long 
> --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/numerical/optimize.py # 8 doctests failed # Permanent sage -t --long 
> --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/coding/code_constructions.py # 1 doctest failed # Permanent sage -t 
> --long --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/numerical/sdp.pyx # 34 doctests failed # Permanent sage -t --long 
> --warn-long 219.5 --random-seed=26277986705114085533763530404370933785 
> src/sage/numerical/backends/cvxopt_sdp_backend.pyx # 21 doctests failed # 
> Permanent sage -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 
> src/sage/matrix/matrix_double_sparse.pyx # 9 doctests failed # Permanent sage 
> -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 
> src/sage/numerical/backends/cvxopt_backend.pyx # 17 doctests failed # 
> Permanent sage -t --long --warn-long 219.5 
> --random-seed=26277986705114085533763530404370933785 
> src/doc/en/thematic_tutorials/numerical_sage/cvxopt.rst # 8 doctests failed # 
> Permanent 
> --
>
> Most of them may be related to outdated references to libcholmod.so.3 (my 
> locate database may have been out of date). I’ll reconfigure and retry.

if you used systemwide sparsesuite (libcholmod is there) and updated
it, you'd need to rebuild everything that uses it.
Specifically, only cvxopt, it seems.

>
> Le dimanche 30 juillet 2023 à 16:25:06 UTC+2, 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
>>
>>
>> 26f5a09baf7 (tag: 10.1.beta8, github/develop) Updated SageMath version to 
>> 10.1.beta8
>> 79dc3510abb gh-35997: Improve getting matrix entries after permutation in 
>> _palp_PM_max()
>> 845963ced07 gh-35977: Move hilbert_numerator test to its proper place
>> fb1648e79fc gh-35974: `src/sage/schemes/projective/proj_bdd_height.py`: Fix 
>> markup
>> 2f604dd785d gh-35965: Minor changes in is_chordal
>> dd82378cbbe gh-35962: Fix documentation formatting problem: 
>> kRegularSequence.partial_sums
>> 448341b2c7c gh-35957: `sage.rings.function_field`: Update `# needs`
>> ce5b249d4d0 gh-35956: Fix several issues in find_hamiltonian
>> 4279c4e326e gh-35943: `sage.combinat.designs`: Modularization fixes, update 
>> `# needs`
>> 4eb3fcb81a7 gh-35904: Make SubgraphSearch robust to vertex labels
>> f85e7b8b192 gh-35900: complex_dynamics, fix: mandelbrot_plot throws 
>> exception for z^2*(z-c) + c
>> 66baa6a2638 gh-35896: deal with bad chosen representations of k-regular 
>> sequences
>> a48b7b81c28 gh-35891: Deprecate sorting by default in connected component 
>> methods for graphs
>> 8b3883de7fd gh-35881: `sage.groups.perm_gps.partn_ref*`: Modularization fixes
>> f2abd5af51f gh-35749: Add style guide / reference for `# optional - 
>> sage` doctest tags, extend `sage -t` and `sage -fixdoctests` for 
>> modularization tasks
>> 3a51d8ca597 gh-35661: New modularized distributions 
>> sagemath-{sirocco,bliss,meataxe,mcqd,coxeter3,tdlib}
>> 1436ea2cbe7 gh-35057: Implement basic j-invariants of Drinfeld modules
>> 543f8d62b08 (tag: 10.1.beta7) Updated SageMath version to 10.1.beta7
>
> --
> 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/17f0c70b-294e-4518-89fa-407e8653e8dfn%40googlegroups.com.

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

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

[Dima Pasechnik]

On Sun, Jul 2, 2023 at 10:21 AM David Coudert  wrote:
>
> Thanks for this release.
>
> After incremental update on fedora 35, I had the following doctest errors.
>
> sage -t --long --random-seed=152397713735156567863222915477684656337 
> src/sage/graphs/generic_graph.py  # 15 doctests failed
> sage -t --long --random-seed=152397713735156567863222915477684656337 
> src/sage/graphs/generators/families.py  # 2 doctests failed
> sage -t --long --random-seed=152397713735156567863222915477684656337 
> src/sage/graphs/bliss.pyx  # 42 doctests failed
>
> Apparently bliss has not been (correctly) updated during incremental update. 
> After running ./sage -i bliss, I don't have these errors anymore.


Fedora 35 (updates) has the right version of bliss, install it
instead, and never rebuild bliss with Sage-
but this needs https://github.com/sagemath/sage/pull/35830 reviewed and merged.



>
> However, I have a few warnings:
>
> sage -t --long --random-seed=290123504548484623481640699812773564886 
> src/sage/graphs/generic_graph.py
> **
> File "src/sage/graphs/generic_graph.py", line 2006, in 
> sage.graphs.generic_graph.GenericGraph.adjacency_matrix
> Warning: Variable 'M' referenced here was set only in doctest marked '# 
> optional - sage.modules'
> M[2, 2] = 1
> **
> File "src/sage/graphs/generic_graph.py", line 5084, in 
> sage.graphs.generic_graph.GenericGraph.cycle_basis
> Warning: Variable 'basis' referenced here was set only in doctest marked '# 
> optional - networkx'
> edge_space.span(basis_as_vectors).rank() == len(basis)# 
> optional - sage.modules sage.rings.finite_rings
> **
> File "src/sage/graphs/generic_graph.py", line 17305, in 
> sage.graphs.generic_graph.GenericGraph.?
> Warning: Variable 'd2' referenced here was set only in doctest marked '# 
> optional - networkx'
> d1 == d2 == d3 == d4
> [3890 tests, 35.49 s]
>
>
> Surprizingly, on macOS I don't see the same warnings:
>
> sage -t --long --random-seed=245923686717559167414566898310223623085 
> src/sage/graphs/generic_graph.py
> **
> File "src/sage/graphs/generic_graph.py", line 2006, in 
> sage.graphs.generic_graph.GenericGraph.adjacency_matrix
> Warning: Variable 'M' referenced here was set only in doctest marked '# 
> optional - sage.modules'
> M[2, 2] = 1
> **
> File "src/sage/graphs/generic_graph.py", line 5083, in 
> sage.graphs.generic_graph.GenericGraph.cycle_basis
> Warning: Variable 'basis' referenced here was set only in doctest marked '# 
> optional - networkx'
> basis_as_vectors = [cycle_to_vector(_) for _ in basis]# 
> optional - sage.modules sage.rings.finite_rings
> [3890 tests, 27.53 s]
>
>
> Best,
> David.
>
>
>
> Le 2 juil. 2023 à 00:53, 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
>
> 853d07099ce (tag: 10.1.beta5, github/develop) Updated SageMath version to 
> 10.1.beta5
> 9161c6c27bf gh-35855: Extend `MAX_MODULUS` of `matrix_modn_dense_double.pyx`
> 42945352f77 gh-35854: correct deprecation messages
> f846602923a gh-35850: Remove mention of defunct magic command "%bg" from the 
> tutorial
> f41eb7db674 gh-35843: Add a WSL prerequisites section
> 90ece168c3c gh-35842: Fix tests with scipy 1.11
> 0796e698004 gh-35831: Support setuptools 68.0.0
> 63eb1d700af gh-35827: some pep8 fixes in symbolic (E305 and others)
> ecfe06b8f1f gh-35826: Fixes to support numpy 1.25.0
> ebc71309fe5 gh-35822: most cython-lint suggestions fixed in algebras/
> f9cb12c362e gh-35820: `sage.features`: Declare features as "standard" 
> explicitly
> 9efdddb0b2b gh-35819: advance the linter (add more checks)
> 9d390f60d4c gh-35818: fully get rid of xrange() in pyx files
> 834144943dc gh-35816: `sage.misc.timing`: Split out from `sage.misc.misc`
> 65ceff81bbb gh-35809: Ensure GCD in `normalize_coordinates` for projective 
> morphisms
> 404d9e5e7f4 gh-35808: .github/workflows/doc-build.yml: Fix generation of 
> CHANGES.html
> c80cc11d4c9 gh-35805: gap: use libgap API for int conversion
> 6b6475d64eb gh-35798: Replace imports from `sage.geometry...all`, update 
> relint pattern
> a7a70f0e5e2 gh-35795: Fix copyright headers in function fields
> 53139f79ded gh-35794: tox.ini, .github/workflows/docker.yml: Add almalinux
> 41d81136451 gh-35792: cleaning some things remaining from python 2
> fb0ae6658cc gh-35789: more arguments for simplify
> f3d389ddf2a gh-35785: build/pkgs/onetbb: Add distros/opensuse.txt
> ffac6e0e197 gh-35782: Allow partial result in minimal_model, and translate 
> OS-algebra to cdga
> 

Re: [sage-release] A detail that matters - please help

[Dima Pasechnik]

On Wed, 28 Jun 2023, 17:13 John H Palmieri,  wrote:

> I think this should be discussed at sage-devel.
>

are there any setbacks in using svg nowadays?


> On Wednesday, June 28, 2023 at 8:49:51 AM UTC-7 vdelecroix wrote:
>
>> I agree with Marc that svg is almost always preferable than png for
>> graphics : it scales and compresses. Thanks for raising the issue.
>>
>> Do you have a concrete proposal for making the change png -> svg
>> happen? I guess there is a lot of files that would be involved in the
>> transition.
>>
>> Vincent
>>
>> On Wed, 28 Jun 2023 at 16:23, Marc Culler  wrote:
>> >
>> > Details really do matter. The devil is in them. Here is one which makes
>> a major difference to my efforts to distribute Sage. I hope that I can
>> convince people to pay attention to it.
>> >
>> > DETAIL: An svg image can be compressed very efficiently and will look
>> good at all resolutions. A png image can not be compressed, being already
>> compressed, and pixelates at high resolutions.
>> >
>> > BACK STORY: I am working on adding documentation to the Sage_macOS
>> distribution. Size is important. For 10.1beta3 the English documentation
>> occupied 631MB, and compressed down to 104MB. For 10.1beta4 the
>> uncompressed size increased by over 100MB due to the addition of 100MB of
>> png images. Now it only compresses to 207MB, doubling the compressed size.
>> >
>> > There is no need for this wastefulness. Here is an example:
>> >
>> > sage: D = graphs.DodecahedralGraph()
>> > sage: p = D.plot()
>> > sage: p.save_image('/tmp/dodec.svg')
>> > sage: p.save_image('/tmp/dodec.png')
>> >
>> > The result:
>> > % ls -l /tmp/dodec*
>> > -rw-r--r--@ 1 culler wheel 42735 Jun 28 08:48 /tmp/dodec.png
>> > -rw-r--r-- 1 culler wheel 18524 Jun 28 08:48 /tmp/dodec.svg
>> > % gzip /tmp/dodec*
>> > % ls -l /tmp/dodec*
>> > -rw-r--r--@ 1 culler wheel 39473 Jun 28 08:48 /tmp/dodec.png.gz
>> > -rw-r--r-- 1 culler wheel 3815 Jun 28 08:48 /tmp/dodec.svg.gz
>> >
>> > BOTTOM LINE: we get more than a 90% reduction in size simply by
>> choosing to use the .svg extension when saving the plot instead of the .png
>> extension.
>> >
>> > I am not allowed to upload an svg file to google groups, so you will
>> have to verify for yourself that the svg looks better than the png, but it
>> does.
>> >
>> > - Marc
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "sage-release" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to sage-release...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-release/8ce7a804-3be1-4551-959e-cc770fe589ecn%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/70d5389f-97ae-490e-b57f-3838a737114an%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/CAAWYfq1zhUVsk0UR1uJv6snYaNOX4DGt96N6Qt23v5oMdVVOZA%40mail.gmail.com.

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

[Dima Pasechnik]

On Thu, Jun 22, 2023 at 7:15 AM Emmanuel Charpentier
 wrote:
>
> On Debian testing running on core i7 + 16 GB RAM, `bootstrap` + `configure` + 
> `make -j8` *fails*. The relevant error seems to be as follows :
>
> ```
> [sagelib-10.1.beta4] INFO: g++ -std=gnu++11 -shared -Wl,-O1 
> -Wl,-Bsymbolic-functions -g -fwrapv -O2 
> -Wl,-rpath-link,/usr/local/sage-10/local/lib -L/usr/local/sage-10/local/lib 
> -Wl,-rpath,/usr/local/sage-10/local/lib -g -O2 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/expression.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/add.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/archive.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/assume.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/basic.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/cmatcher.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/constant.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/context.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/ex.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/expair.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/expairseq.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/exprseq.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/fderivative.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/function.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/function_info.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/infinity.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/infoflagbase.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_comb.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_gamma.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_hyperb.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_hyperg.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_nstdsums.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_orthopoly.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_trans.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_trig.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/inifcns_zeta.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/lst.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/matrix.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/mpoly-giac.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/mpoly-ginac.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/mpoly-singular.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/mpoly.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/mul.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/normal.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/numeric.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/operators.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/order.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/power.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/print.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/pseries.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/py_funcs.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/registrar.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/relational.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/remember.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/sum.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/symbol.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/templates.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/upoly-ginac.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/useries.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/utils.o 
> build/temp.linux-x86_64-cpython-311/sage/symbolic/ginac/wildcard.o 
> -L/usr/lib/x86_64-linux-gnu/openblas-pthread/ -L/usr/lib/x86_64-linux-gnu 
> -lflint -lgmp -lSingular -lpolys -lfactory -lflint -lmpfr -lntl -lgmp 
> -lomalloc -lsingular_resources -lgsl -lm -lopenblas -o 
> build/lib.linux-x86_64-cpython-311/sage/symbolic/expression.cpython-311-x86_64-linux-gnu.so
>  -lpari
> [sagelib-10.1.beta4] error: Command "gcc -shared -Wl,-O1 
> -Wl,-Bsymbolic-functions -g -fwrapv -O2 
> -Wl,-rpath-link,/usr/local/sage-10/local/lib -L/usr/local/sage-10/local/lib 
> -Wl,-rpath,/usr/local/sage-10/local/lib -g -O2 
> build/temp.linux-x86_64-cpython-311/sage/libs/arb/arith.o 
> -L/usr/lib/x86_64-linux-gnu -lgmp -lflint -larb -o 
> build/lib.linux-x86_64-cpython-311/sage/libs/arb/arith.cpython-311-x86_64-linux-gnu.so"
>  failed with exit status 1
> [sagelib-10.1.beta4] error: subprocess-exited-with-error
> [sagelib-10.1.beta4]
> 

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

[Dima Pasechnik]

You can't reopen PRs, I think, you can certainly reopen issues.

No need to fill in the longish PR boilerplate, just remove it and write
what it does, mentioning #35626



On Fri, 16 Jun 2023, 09:08 chris wuthrich, 
wrote:

> I replaced old tests with "random" by new ones with "random" (and forgot
> these two). Some other tests do check consistency.
>
> All that the function really does is converting a pari output back into a
> point on the elliptic curve. Therefore the test checks if pari runs without
> error and if the returned is a point on the curve. Checking if it is a
> generator modulo torsion would be checking if pari gets this right. Is that
> what we should do?
>
> But this discussing should happen on a pull request. I repeat my question:
> Do I open a new one or is the faulty initial one reopened? (Trac tickets
> used to be reopened, that is why I ask).
>
> Chris
>
> On Friday, 16 June 2023 at 01:39:46 UTC+1 tsc...@ucdavis.edu wrote:
>
>> I don't think it should be random; that has the chance of hiding actual
>> bugs. I think we should check that it belongs to a particular set
>> (specifically, the one from John's comment).
>>
>> Best,
>> Travis
>>
>>
>> On Thursday, June 15, 2023 at 5:15:52 AM UTC+9 chris wuthrich wrote:
>>
>>> I agree with John. Lines 2380 and 2388 need a "random output" for that
>>> reason, like the other calls of that function have already.
>>> Is this a new pull request or is the old #35626
>>> https://github.com/sagemath/sage/pull/35626 opened again for
>>> corrections?
>>>
>>> Chris
>>>
>>> On Wednesday, 14 June 2023 at 17:49:21 UTC+1 John Cremona wrote:
>>>
 On Tue, 13 Jun 2023 at 17:06, John Cremona  wrote:

> The elliptic curve failure might be a consequence of the recently
> merged PR #35626 about using libpari to compute ranks and generators.
>
> I'll take a look to at least see if the output you get is
> mathematically correct -- generators are not unique.
>

 I was right. This curve has rank 1 and torsion (Z/2Z)^2 so if P is one
 generator (of infinte order) then there are 3 other, P+T for T a point of
 order 2.  The one your are getting is one of these.

 So we conclude that we cannot reply on pari always returning the same
 generator despite random seeds etc being fixed in doctests.  I don't know
 why that is, but if it is the case then this (and other similar) doctests
 will have to be written accordingly.


>
> John
>
>
> On Tue, 13 Jun 2023, 17:00 Emmanuel Charpentier, <
> emanuel.c...@gmail.com> wrote:
>
>> On Debian testing running on core i7 + 16 GB RAM, upgrading
>> 10.1.beta2 to 10.1.beta3 and rinning ptestlong gives 3 permanent 
>> failures :
>> --
>> sage -t --long --warn-long 207.1
>> --random-seed=291812591553963182024849035945523427319
>> src/sage/schemes/elliptic_curves/ell_rational_field.py # 1 doctest failed
>> sage -t --long --warn-long 207.1
>> --random-seed=291812591553963182024849035945523427319
>> src/sage/coding/linear_code.py # 2 doctests failed sage -t --long
>> --warn-long 207.1 --random-seed=291812591553963182024849035945523427319
>> src/sage/coding/code_constructions.py # 1 doctest failed
>> --
>>
>> The last two have been already reported a few times, and seem
>> cosmetic. The first one is new and seemingly *not* cosmetic :
>> charpent@zen-book-flip:/usr/local/sage-10$ sage -t --long
>> --warn-long 207.1 --random-seed=291812591553963182024849035945523427319
>> src/sage/schemes/elliptic_curves/ell_rational_field.py # 1 doctest failed
>> Running doctests with ID 2023-06-13-17-49-08-8dac2a23. Git branch: 
>> develop
>> Git ref: 10.1.beta0-453-g443b7549ad Running with
>> SAGE_LOCAL='/usr/local/sage-10/local' and
>> SAGE_VENV='/usr/local/sage-10/local/var/lib/sage/venv-python3.11' Using
>> --optional=debian,dot2tex,fricas,gap_jupyter,gap_packages,libsemigroups,msolve,pip,pysingular,sage,sage_spkg,singular_jupyter
>> Features to be detected:
>> 

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

[Dima Pasechnik]

On Tue, May 23, 2023 at 11:02 PM John H Palmieri  wrote:
>
> There was a problem with Singular, but that should have been fixed in #34851, 
> merged into 10.0.beta0 in February. 
> (https://github.com/sagemath/sage/issues/34851)

it's only Debian experimental that is on Singular 4.3.2, the previous
Debians are on 4.3.1
https://packages.debian.org/experimental/singular


>
> On Tuesday, May 23, 2023 at 1:11:50 PM UTC-7 matthia...@gmail.com wrote:
>>
>> On Monday, May 22, 2023 at 11:39:09 PM UTC-7 tdumont wrote:
>>
>>
>> On debian testing (buster) no problem when updating from 10.0.
>>
>> A question:
>> - since some months (?) I always configure "without system singular"
>> ( ./configure --without-system-singular ), as singular in debian testing
>> changed to a recent version.
>>
>> * Is it always necessary ? (yes, I think...)
>>
>>
>> I'm not aware of a problem with system singular on debian.
>>
>> On debian-buster, our configure script rejects system singular because of 
>> dependencies. 
>> https://github.com/sagemath/sage/actions/runs/5031589540/jobs/9024750374#step:11:2494
>>
>> Likewise on debian-bullseye: 
>> https://github.com/sagemath/sage/actions/runs/5031589540/jobs/9024750402#step:11:2603
>>
>> On debian-bookworm, the system package is accepted: 
>> https://github.com/sagemath/sage/actions/runs/5031589540/jobs/9024750423#step:11:2754
>> and all tests pass: 
>> https://github.com/sagemath/sage/actions/runs/5031589540/jobs/9026953445#step:11:11651
>>
>> Likewise on debian-sid.
>>
>> (These runs are for the 10.0 release.)
>>
>>
>
> --
> 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/fc6519f9-12ef-4989-b56b-e59bece1be99n%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/CAAWYfq3seUOsKP0F9oJVcvt1%3DYc2kDEbOJ1f68aO881_UrjTow%40mail.gmail.com.

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

[Dima Pasechnik]

On Tue, May 23, 2023 at 7:39 AM Thierry Dumont
 wrote:
>
>
> On debian testing (buster) no problem when updating from 10.0.
>
> A question:
> - since some months (?) I always configure "without system singular"
> ( ./configure --without-system-singular ), as singular in debian testing
> changed to a recent version.
>
> * Is it always necessary ? (yes, I think...)
>
> * If yes: Debian testing (bookworm) is about to turn "stable" (June, 10
> ?). So this problem will turn into a more important one. Is there any
> project to interface sage with singular recent release ?

I've opened https://github.com/sagemath/sage/issues/35676
to address this.


>
>
> Yours,
> t.d.
>
>
> Le 23/05/2023 à 00:59, 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
> >
> >
> > 7404764fb27 (tag: 10.1.beta0, github/develop) Updated SageMath version
> > to 10.1.beta0
> > 8455792fc70 gh-35573: some details in posets
> > f33652c70c1 gh-35570: 4ti2: Update to 1.6.10, fixes `egrep` issue, adds
> > GCC 13 support
> > ac73a80e68a gh-35566: partial cython-lint in plot folder
> > 0772e476dca gh-35565: replace obsolescent egrep
> > 91be3396035 gh-35563: Make doc preview message from github bot one liner
> > 8a49d3b05be gh-35553: cython-lint cleaning in combinat/
> > 57bd5b8fa1e gh-35551: Enable access to some methods in
> > sage/graphs/graph_decompositions
> > a919389af98 gh-35550: removing some unused imports in cython files
> > 941ff75d7d1 gh-35549: fixing some pycodestyle warnings E251
> > 6e3cc34d55a gh-35548: Fvector for fans
> > cab4a6fe520 gh-35540: For groups: generic centralizer, subgroup methods;
> > improving center
> > 5a2cbb7775c gh-35536: src/sage_docbuild/conf.py: Do not fail if pplpy
> > doc is not installed
> > 2a6d3eb7212 gh-35519: Make rank return an Integer object
> > e50524ac6bd gh-35516: some cython-linting in modular/ folder
> > 2c249964884 gh-35505: Deprecate `is_SymbolicVariable`, `is_SymbolicEquation`
> > 07bd42434be gh-35502: `sage.rings.factorint`: Modularization fixes
> > c3ed171b4ad gh-35484: Implement down-up algebras and their Verma modules
> > 349bb73c0cc gh-35477: `libgd`: Disable most image libraries, upgrade to
> > 2.3.3
> > b02631d13b8 gh-35432: Some fixes for Specht modules and diagrams
> > 828ad227946 gh-35430: Adding bigraded Betti numbers functionality
> > b3781191714 gh-35422: sage.categories: Add `# optional` for
> > modularization; reformat doctests
> > 2828993ab94 gh-35417: Remove tag fetching in docker workflow
> > 3bf5f0a25f7 gh-35387: The Fusion Ring of the Drinfeld Double of a Finite
> > Group
> > b147e2964b6 gh-35371: `openblas`: Update to 0.3.23
> > e154beabd78 gh-35354: Add a few operations from linear symplectic geometry
> > fdf96683497 gh-35260: Implement the logarithm and the exponential of a
> > Drinfeld module
> > 9de8e264001 gh-35208: Support tox 4.x for testing modularized distributions
> > 62dd325db17 gh-35145: add parallel algorithm to Graph chromatic_number
> > 8b24c201354 gh-35108: src/doc/en/developer/portability_testing.rst:
> > Update after migration
> > d73d7d7560d gh-35009:  Add ability to generate graphs based on
> > correlations of sequences #25933
> > 6ba0eafc2ca (tag: 10.0, github/master) Updated SageMath version to 10.0
> >
> > --
> > 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/6cbc6fee-823d-4e2b-8ee7-f96381b7f48en%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/11b8e793-7edc-edd0-567b-9504295a690f%40math.univ-lyon1.fr.

-- 
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/CAAWYfq0wRwSFB-OFv0Zysj5SiJKt%2BPEEpDKAdXxxCv12gSoQ%3DQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

On Sun, 21 May 2023, 19:37 Matthias Köppe,  wrote:

> On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote:
>
> > - I will no longer create a text version
> > of the changelog in the traditional format (e.g.
> > https://www.sagemath.org/changelogs/sage-9.8.txt),
> > as it provides no added value.
>
> I strongly disagree with "as it provides no added value".
>
>
"git log" does a good job of searching the history.
I think each ticket/PR can be found there.



>
> The traditional changelogs do provide added value:
>
> - the changelogs, as text files, are very searchable
> (see above for detecting previous contributions!)
> - they give a nice overview of what went into
> each development release and final release
> - they name authors and reviewers for each ticket
>
> Many other free software projects maintain changelogs
> as text files (which might point to their added value too).
>
>
> I'm not opposed to creating such changelogs. I'm just announcing that I
> will not be working on it.
>
> In fact, https://github.com/sagemath/sage/issues/31533 proposes to "Migrate
> old Sage release tours and changelogs from Sage website and wiki to Sage
> documentation".
>
> That may be something that people who perceive an added value in text
> changelogs may be movtivated to work on.
>
>
> --
> 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/e629d2ca-a338-4108-812c-168786e2089en%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/CAAWYfq3BWraq2_qoU8HdQYzNhNrNUu7XX8mPc2_vDfvfh6bCMw%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

This is now https://github.com/sagemath/sage/issues/35659

On Sun, May 21, 2023 at 2:33 PM Dima Pasechnik  wrote:
>
> probably, related to
> https://github.com/citation-file-format/citation-file-format/issues/374
>
> On Sun, May 21, 2023 at 1:58 PM Dima Pasechnik  wrote:
> >
> > something is again off with the DOI records for Sagemath, the latest
> > is still shown as 9.7.
> > Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
> > is off, and still refers to 9.5.
> >
> > (sorry, I didn't check this for 9.8)
> >
> > Dima

-- 
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/CAAWYfq3uF8r73zCua6yzY-uoBqv5hKbTvigWCbWayVWA%2BNzPnQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

probably, related to
https://github.com/citation-file-format/citation-file-format/issues/374

On Sun, May 21, 2023 at 1:58 PM Dima Pasechnik  wrote:
>
> something is again off with the DOI records for Sagemath, the latest
> is still shown as 9.7.
> Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
> is off, and still refers to 9.5.
>
> (sorry, I didn't check this for 9.8)
>
> Dima

-- 
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/CAAWYfq3CWJyOV8OiXFvLpsDMm1F4CJUN%2BDY59PRA5fLRE2w7dA%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

something is again off with the DOI records for Sagemath, the latest
is still shown as 9.7.
Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
is off, and still refers to 9.5.

(sorry, I didn't check this for 9.8)

Dima

-- 
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/CAAWYfq3kFPOOh8-dSMpyk_44RN6M4xST9FvpdGBM5YAYOu47%3DA%40mail.gmail.com.

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

[Dima Pasechnik]

On Sun, 14 May 2023, 09:48 Volker Braun,  wrote:

> As always, only blockers are merged in release candidates. If a normal
> ticket is not done during the normal merge window then its not going in,
> otherwise we never finish making a release.
>

Volker, can you at least merge small documentation or dependency lists only
things before the release?
i.e. PRs 35637 and 35638

Without them, we'd potentially get more bug/problems reports here - for
bugs which aren't bugs, or bugs which are fixed.
This is potentially much more work even for us, at expense of your 2
minutes or so needed to merge trivial changes.







> On Saturday, May 13, 2023 at 11:54:55 PM UTC+2 matthia...@gmail.com wrote:
>
> Other relevant tickets for the 10.0 release:
> https://github.com/sagemath/sage/milestone/152
>
> --
> 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/17850ffb-9e4f-44fb-96bf-dd9e10c3fdd3n%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/CAAWYfq1PKqtCPQp7_Z0BQ8YSuDZ4%3DUQ9ZaD%2Bjzyp%2BVvJHZviDA%40mail.gmail.com.

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

[Dima Pasechnik]

On Sat, May 6, 2023 at 11:18 PM Marc Culler  wrote:
>
> While  preparing a binary release for macOS I discovered that in 10.0.rc1 the 
> gap-packages spkg fails to install the script BuildPackages.sh in 
> sage/local/lib/gap/bin.  This breaks installation of GAP packages with 
> libgap.InstallPackage.  All that needs to be done to fix it is to copy that 
> script into place.

I've opened https://github.com/gap-system/gap/issues/5448
- as GAP's `make install` should do this.
>
> - Marc
>
> On Friday, April 28, 2023 at 6:15:04 PM UTC-5 Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git 
>> branch. Alternatively, the self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html
>>
>> 5bd81deae14 (HEAD -> develop, tag: 10.0.rc1, github/develop) Updated 
>> SageMath version to 10.0.rc1
>> 9185befce0c gh-35558: `sage.quadratic_forms`: Fix use of `staticmethod` for 
>> Python < 3.10
>> 2bedb53b5ea gh-35415: `givaro`, `zeromq`: Add patches for GCC 13 support
>> f3acd42678a (tag: 10.0.rc0) Updated SageMath version to 10.0.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/7da67ce0-fdd2-4334-a836-b19713b347acn%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/CAAWYfq1UZ2sztkeDLs7X7LpoTJ8_nDm99Vw0YQ1VB9-iibdqTQ%40mail.gmail.com.

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

[Dima Pasechnik]

Thanks, it's now https://github.com/sagemath/sage/pull/35571

On Wed, Apr 26, 2023 at 10:32 AM Thierry
 wrote:
>
> Hi,
>
> Sage's current openssl version (3.0.5) hass several "High severity"
> vulnerabilities, see https://www.openssl.org/news/vulnerabilities.html
>
> It would be nice to have the fixes included in the next Sage release. I am not
> using github, here is a pull request (literally) to fix this :
>
>   git pull https://lipn.univ-paris13.fr/~monteil/hebergement/sage/sage.git 
> openssl.3.0.8
>
> (commit hash : 997a6bd35a17f5511bb12552bd676597b09f1eaf)
> I checked the hash of the tarballs against the GPG signatures by upstream 
> developers.
>
> Tarball at : https://www.openssl.org/source/openssl-3.0.8.tar.gz
>
> Ciao,
> Thierry
>
> P.S. Note that 3.1.0. has been very recently released, however 3.0.x is LTS 
> and will
> not have structural changes. Just in case, here is a verified branch :
>
>   git pull https://lipn.univ-paris13.fr/~monteil/hebergement/sage/sage.git 
> openssl.3.1.0
>
> (commit hash : 9229a2be66dc0e4f2e3f677aa515a33bfe72a873)
> Tarball at : https://www.openssl.org/source/openssl-3.1.0.tar.gz
>
>
>
>
> Le Sun, Apr 23, 2023 at 07:46:00AM -0700, 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
> >
> >
> > f3acd42678a (tag: 10.0.rc0, github/develop) Updated SageMath version to
> > 10.0.rc0
> > eca2a773d08 gh-35543: Cleaning set partition
> > 9d8c9c05117 gh-35542: some fixes for cython-lint in various places
> > e1e119463ae gh-35534: some cython-lint fixes in matroids/
> > 133a345bacb gh-35533: Fix bug in graph.maximum_average_degree
> > 3c2ba826156 gh-35530: some minor details in interfaces
> > 12cea800735 gh-35526: fix pycodestyle E271 and E502 in pyx files
> > a03f09cf594 gh-35525: cython-lint and some doc cleanup for expression.pyx
> > e9b67cc117a gh-35521: `sage.combinat.sf`: re-enable a doctest
> > cc0ea4d66f4 gh-35518: Improve PolynomialSequence.connected_components()
> > a38a25a261e gh-35515: Bug in integer valued polys
> > 803c7aacaee gh-35514: Don't force ecl lisp with `maxima -l ecl` on command
> > line.
> > 20d2edd1736 gh-35513: Silence initialization of giac
> > 64c205c7d51 gh-35512: Improve PolynomialSequence.connection_graph()
> > implementation
> > db2fa5d13b1 gh-35511: Fix Graph.add_clique() for one vertex
> > 0ff23f67772 gh-35510: Make BooleanPolynomial.variables() way faster
> > e3636bd579c gh-35509: some cython-linting in matrix/ folder
> > 2c7e16e5faf gh-35507: fix pycodestyle E303 in schemes
> > 98595ef8661 gh-35506: add check for pycodestyle E502 in python files
> > 80f3fd99d04 gh-35504: `build/pkgs/sphinx_{copybutton,basic_ng}`: Add conda
> > info
> > 41c256ae647 gh-35499: Fix test output for ipywidgets 8.0.5, part deux
> > 3740e145432 gh-35478: Remove unused code from GAP interface
> > b25229b6647 gh-35476: scipy: Patch out test requiring internet access
> > eafd5215a28 gh-35472: Implement the Feichtner-Yuzvinsky rings for lattices
> > 957e627f023 gh-35465: Fix conda workflow
> > 1fc3fee5bed gh-35463: Add iterator over minimum distance k dominating sets
> > ecd162be3dc gh-35462: Iterator over the minimal distance k dominating sets
> > c18a3fbfe72 gh-35446: add method is_simple to permutations
> > ef68bee7ccf gh-35443: Fix slow doctests or mark # long time
> > c005c006d4e gh-35431: Documentation improvements for rounding methods
> > 15a5078afaa gh-35389: `sage.rings.finite_rings.residue_field`:
> > Modularization fixes
> > 9ff469adb9c gh-35375: Fix minimal kernel basis corner cases
> > 55ebb79b65a gh-35306: `sage.groups.matrix_gps`: Modularization fixes for
> > imports
> > 8bcce63b6a1 gh-35305: `sage.quadratic_forms`: Modularization fixes for
> > imports
> > 97b45d80a7c (tag: 10.0.beta9) Updated SageMath version to 10.0.beta9
> >
> > --
> > 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/788f2bad-420b-463a-be98-4f11819d3288n%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/ZEjvpybhNZhFERjm%40metelu.net.

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

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

[Dima Pasechnik]

On Mon, Apr 3, 2023 at 10:39 AM Sébastien Labbé  wrote:
>
> On Ubuntu 18.04, running tests with few optional and external packages, I get:
>
> Using 
> --optional=4ti2,antic,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_spkg
>
> --
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/algebras/fusion_rings/fusion_ring.py  # Timed out
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/combinat/bijectionist.py  # Timed out
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/combinat/designs/incidence_structures.py  # 1 doctest failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/databases/oeis.py  # 3 doctests failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/graphs/generators/smallgraphs.py  # 8 doctests failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/graphs/generic_graph.py  # 2 doctests failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/graphs/graph.py  # 3 doctests failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/graphs/strongly_regular_db.pyx  # 4 doctests failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/misc/package.py  # 1 doctest failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/repl/interpreter.py  # 1 doctest failed
> sage -t --long --random-seed=409344892558916435601795955895717921 
> src/sage/tests/cmdline.py  # 1 doctest failed
> --
> Features detected for doctesting: 
> cvxopt,dvipng,ffmpeg,gfan,graphviz,imagemagick,internet,latex,latex_package_tkz_graph,lualatex,nauty,networkx,numpy,octave,palp,pandoc,pdf2svg,pdflatex,pdftocairo,pplpy,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.libs.gap,sage.libs.pari,sage.libs.singular,sage.misc.cython,sage.modules,sage.plot,sage.rings.finite_rings,sage.rings.function_field,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.rings.real_mpfr,sage.symbolic,sagemath_doc_html,sphinx,xelatex
>
>
>
>
> --
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/algebras/fusion_rings/fusion_ring.py  # Timed out
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/combinat/bijectionist.py  # Timed out
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/combinat/designs/incidence_structures.py  # 1 doctest failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/databases/oeis.py  # 3 doctests failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/graphs/generators/smallgraphs.py  # 8 doctests failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/graphs/generic_graph.py  # 4 doctests failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/graphs/graph.py  # 2 doctests failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/graphs/strongly_regular_db.pyx  # 4 doctests failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/misc/package.py  # 1 doctest failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/repl/interpreter.py  # 1 doctest failed
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/tests/cmdline.py  # 1 doctest failed
> --
> Features detected for doctesting: 
> graphviz,internet,latex,networkx,pandoc,sage.groups,sage.symbolic
>
>
> Among the errors I have never seen before are:
>
>
>
> sage -t --long --random-seed=319675451421640445800652566785887159111 
> src/sage/graphs/strongly_regular_db.pyx
> **
> File "src/sage/graphs/strongly_regular_db.pyx", line 2292, in 
> sage.graphs.strongly_regular_db.SRG_280_135_70_60
> Failed example:
> g=SRG_280_135_70_60()  # long time # optional - internet
> Exception raised:
> Traceback (most recent call last):
>   File "/home/slabbe/GitBox/sage/src/sage/doctest/forker.py", line 695, 
> in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File "/home/slabbe/GitBox/sage/src/sage/doctest/forker.py", line 1093, 
> in compile_and_execute
> exec(compiled, globs)
>   File "", 
> line 1, in 
> g=SRG_280_135_70_60()  # long 

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

[Dima Pasechnik]

make sagelib-clean sagelib-uninstall
make

?

On Mon, 27 Mar 2023, 16:03 Eric Gourgoulhon,  wrote:

> Le lundi 27 mars 2023 à 17:00:12 UTC+2, Eric Gourgoulhon a écrit :
>
> Hi,
>
> On Ubuntu 22.04 running on Intel Core i7-8665U @1.9 GHz + 32 GB RAM,
> incremental parallel (-j8) build from Sage 10.0.beta4 failed while building
> the documentation.
> Running
> make doc-clean doc-uninstall
> and then make again did not help.
> The issue seems to be in sage.geometry.integral_points;
>
>
> This is the same error as reported by Emanuel, our messages being posted
> at almost the same time.
>
>
> --
> 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/c3657cd3-da46-4f4b-a72e-f6ca8514f120n%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/CAAWYfq0hBXUA0Xiky-cWg%2BHLG2k1FspDkiwb8kpaULa%3D9Z7DCA%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, Mar 27, 2023 at 11:08 AM Kenji Iohara  wrote:
>
> The first one:
>
>
> ls -l/usr/local/opt/openblas/lib/pkgconfig/openblas.pcgives
>
>
> ls: invalid option -- /

There must be a space between '-l' and the path, i.e

ls-l /usr/local/opt/openblas/lib/pkgconfig/openblas.pc
>
> usage: ls [-@ABCFGHILOPRSTUWabcdefghiklmnopqrstuvwxy1%,] [--color=when] [-D 
> format] [file ...]
>
>
> And the second one:
>
>
> ls -l /usr/local/opt/openblas/lib/pkgconfig/openblas.pc 
> local/lib/pkgconfig/*.pcgives
>
>
> -r--r--r--  1 iohara  admin  556 Mar 26 20:26 
> /usr/local/opt/openblas/lib/pkgconfig/openblas.pc
>
> lrwxr-xr-x  1 iohara  staff   49 Mar 26 20:38 local/lib/pkgconfig/blas.pc -> 
> /usr/local/opt/openblas/lib/pkgconfig/openblas.pc
>
> lrwxr-xr-x  1 iohara  staff   49 Mar 26 20:38 local/lib/pkgconfig/cblas.pc -> 
> /usr/local/opt/openblas/lib/pkgconfig/openblas.pc
>
> -rw-r--r--  1 iohara  staff  353 Mar 26 20:52 local/lib/pkgconfig/eclib.pc
>
> -rw-r--r--  1 iohara  staff  630 Mar 26 21:17 
> local/lib/pkgconfig/fflas-ffpack.pc
>
> -rw-r--r--  1 iohara  staff  340 Mar 26 22:58 local/lib/pkgconfig/gf2x.pc
>
> -rw-r--r--  1 iohara  staff  503 Mar 26 21:09 local/lib/pkgconfig/givaro.pc
>
> -rw-r--r--  1 iohara  staff  338 Mar 26 20:38 local/lib/pkgconfig/gsl.pc
>
> lrwxr-xr-x  1 iohara  staff   49 Mar 26 20:38 local/lib/pkgconfig/lapack.pc 
> -> /usr/local/opt/openblas/lib/pkgconfig/openblas.pc
>
> -rw-r--r--  1 iohara  staff  313 Mar 26 21:11 local/lib/pkgconfig/lcalc.pc
>
> -rw-r--r--  1 iohara  staff  636 Mar 26 21:18 local/lib/pkgconfig/linbox.pc
>
> -rw-r--r--  1 iohara  staff  332 Mar 26 20:45 local/lib/pkgconfig/m4ri.pc
>
> -rw-r--r--  1 iohara  staff  326 Mar 26 21:19 local/lib/pkgconfig/m4rie.pc
>
>
>
> And the last one
>   .mesonpy-cu4n01zf/
> does not exist.
>
> 27/03/2023 2:34、Matthias Köppe のメール:
>
> ls -l /usr/local/opt/openblas/lib/pkgconfig/openblas.pc 
> local/lib/pkgconfig/*.pc
>
>
> --
> 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/F37757D1-3756-405A-9625-DF5AA5DAD113%40gmail.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/CAAWYfq1%3Dx1qaMCb%3DWLnWtP1UAfwdBmZSXH-9oRjyWusuYXthZw%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.8 released

[Dima Pasechnik]

One reason might be is that this version of the package is just too old.
It was released long before all those macOS updates, and it is quite heavy
C++ stuff.

You might get better luck with using positively reviewed update with GAP
4.12.2



On Sun, 19 Feb 2023, 17:13 Dima Pasechnik,  wrote:

> does
>
>  sage: libgap.LoadPackage("semigroup")
>
> crash, as well?
>
> and how about the same at GAP prompt:
>
> ./sage --gap
> ..
>
>gap> LoadPackage("semigroup");
>
>
>
>
>
> On Sun, 19 Feb 2023, 16:11 Marc Culler,  wrote:
>
>> By running the load command in sage -gap I can see that GAP is crashing
>> with an illegal instruction error while trying to load the semigroups
>> package.
>>
>> - Marc
>>
>> On Sunday, February 19, 2023 at 10:04:51 AM UTC-6 Marc Culler wrote:
>>
>>> I am trying to build the binary release of Sage 9.8 for macOS and I have
>>> run into a mysterious problem.  I wonder if anyone on this list has any
>>> insight into it.
>>>
>>> There are really two separate binary releases: one for Intel and one for
>>> Apple Silicon.  These are built using the same build script but on two
>>> separate machines whose native architecture matches the target.  That is,
>>> there is no cross-compilation involved.
>>>
>>> This is what I see on Intel:
>>> sage: %gap LoadPackage("semigroups");
>>> true
>>>
>>> This is what I see on Apple M1:
>>> sage: %gap LoadPackage("semigroups");
>>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>>> Restarting Gap and trying again
>>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>>> Restarting Gap and trying again
>>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>>> Restarting Gap and trying again
>>>
>>> ^C---
>>>
>>> (You have to kill Sage or it will keep restarting Gap forever.)
>>>
>>> Does anyone have any ideas?
>>>
>>> - Marc
>>>
>>>
>>>
>>> On Saturday, February 11, 2023 at 7:47:09 AM UTC-6 Volker Braun wrote:
>>>
>>>> The "master" git branch has been updated to Sage-9.8. 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
>>>>
>>>> And as you are undoubtedly aware, the git repository is now hosted at
>>>> https://github.com/sagemath/sage, so update your git remote.
>>>>
>>>> To commemorate the move (and because we are getting really close to
>>>> .10), I'm proposing to target Sage version 10 as the next release.
>>>>
>>>> The changes over 9.8.rc0 are mainly housekeeping for the new repository
>>>> location.
>>>>
>>>> I'll try to finish up merging remaining positively reviewed trac
>>>> issues, and then move on to github pull requests.
>>>>
>>>>
>>>> c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8)
>>>> Updated SageMath version to 9.8
>>>> 104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
>>>> 17d8a73296f Merge pull request #35018 from x4/public/35017
>>>> 6a4667bb5c5 Merge pull request #34983 from
>>>> tobiasdiez/add-issue-templates
>>>> 66b319baffb Merge pull request #35011 from dimpase/develop
>>>> 872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
>>>> d57804e6dec Merge pull request #34964 from x4/public/linter-20230206
>>>> 698001b0e6a remove prohibition, promise details
>>>> 0c5f7baf6c2 remove trac references, promise details soon
>>>> 200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1
>>>>
>>> --
>> 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/be0b9508-3a85-4219-ad3f-4fe8cd0bbb8en%40googlegroups.com
>> <https://groups.google.com/d/msgid/sage-release/be0b9508-3a85-4219-ad3f-4fe8cd0bbb8en%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CAAWYfq3s5DCt1b_1HKk4xYoZB82bh053d3q9dzO0N82J%2BtcAuQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.8 released

[Dima Pasechnik]

does

 sage: libgap.LoadPackage("semigroup")

crash, as well?

and how about the same at GAP prompt:

./sage --gap
..

   gap> LoadPackage("semigroup");





On Sun, 19 Feb 2023, 16:11 Marc Culler,  wrote:

> By running the load command in sage -gap I can see that GAP is crashing
> with an illegal instruction error while trying to load the semigroups
> package.
>
> - Marc
>
> On Sunday, February 19, 2023 at 10:04:51 AM UTC-6 Marc Culler wrote:
>
>> I am trying to build the binary release of Sage 9.8 for macOS and I have
>> run into a mysterious problem.  I wonder if anyone on this list has any
>> insight into it.
>>
>> There are really two separate binary releases: one for Intel and one for
>> Apple Silicon.  These are built using the same build script but on two
>> separate machines whose native architecture matches the target.  That is,
>> there is no cross-compilation involved.
>>
>> This is what I see on Intel:
>> sage: %gap LoadPackage("semigroups");
>> true
>>
>> This is what I see on Apple M1:
>> sage: %gap LoadPackage("semigroups");
>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>> Restarting Gap and trying again
>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>> Restarting Gap and trying again
>> ** Gap crashed or quit executing 'LoadPackage("semigroups");' **
>> Restarting Gap and trying again
>>
>> ^C---
>>
>> (You have to kill Sage or it will keep restarting Gap forever.)
>>
>> Does anyone have any ideas?
>>
>> - Marc
>>
>>
>>
>> On Saturday, February 11, 2023 at 7:47:09 AM UTC-6 Volker Braun wrote:
>>
>>> The "master" git branch has been updated to Sage-9.8. 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
>>>
>>> And as you are undoubtedly aware, the git repository is now hosted at
>>> https://github.com/sagemath/sage, so update your git remote.
>>>
>>> To commemorate the move (and because we are getting really close to
>>> .10), I'm proposing to target Sage version 10 as the next release.
>>>
>>> The changes over 9.8.rc0 are mainly housekeeping for the new repository
>>> location.
>>>
>>> I'll try to finish up merging remaining positively reviewed trac issues,
>>> and then move on to github pull requests.
>>>
>>>
>>> c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8)
>>> Updated SageMath version to 9.8
>>> 104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
>>> 17d8a73296f Merge pull request #35018 from x4/public/35017
>>> 6a4667bb5c5 Merge pull request #34983 from tobiasdiez/add-issue-templates
>>> 66b319baffb Merge pull request #35011 from dimpase/develop
>>> 872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
>>> d57804e6dec Merge pull request #34964 from x4/public/linter-20230206
>>> 698001b0e6a remove prohibition, promise details
>>> 0c5f7baf6c2 remove trac references, promise details soon
>>> 200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1
>>>
>> --
> 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/be0b9508-3a85-4219-ad3f-4fe8cd0bbb8en%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/CAAWYfq3ctFKjGhTC%3D8vSTXA4aS1%2BzZaYJBhZpFYqDM8vyOdOpQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.8 released

[Dima Pasechnik]

On Sun, Feb 12, 2023 at 5:04 PM 'Nasser M. Abbasi' via sage-release <
sage-release@googlegroups.com> wrote:

> Thanks. That was it. I did not notice the `3` was missing when I typed it.
> Now it works:
>
> >sage
> │ SageMath version 9.8, Release Date: 2023-02-11
> │ Using Python 3.11.1. Type "help()" for help.
>
> I find it very strange that sagemath ./configure will accept an invalid or
> unknown option. This should have been an error.
>
> If it had complained about it, then the user will know they have used a
> wrong option immediately.
>

it did complain, at the end of ./configure run:


config.status:4085: creating convenience symlink prefix -> local
config.status:4100: creating convenience symlink venv ->
local/var/lib/sage/venv-python3.10
configure:120940: WARNING: unrecognized options: --with-system-python
configure:
...



>
>
> This would save time and effort in the future if this happens again.
>
> --Nasser
>
>
>
>
> On Sunday, February 12, 2023 at 7:51:57 AM UTC-6 Matthias Köppe wrote:
>
>> From config.log, one can see that you typed "
>> "./configure --with-system-python=no"
>> but the correct option is "--with-system-python3=no".
>>
>> On Sunday, February 12, 2023 at 1:10:11 AM UTC-8 Nasser M. Abbasi wrote:
>>
>>> Thanks. I downloaded 9.8 and build it OK. No errors building it.
>>>
>>> But unlike 9.8 rc1, I see that 9.8 is back to using system python which
>>> is 3.10.9 and not sagemath python 3.11.1 like 9.8 rc1 did, even though I
>>> used the same exact configuration commands. These are the commands I used
>>>
>>> unset SAGE_ROOT
>>> unset SAGE_LOCAL
>>> ./configure --with-system-python=no
>>> make
>>> make install
>>>
>>>
>>> And now from a new terminal I type
>>>
>>> >which python
>>> /usr/bin/python
>>>
>>> >python --version
>>> Python 3.10.9
>>>
>>> >sage --version
>>> SageMath version 9.8, Release Date: 2023-02-11
>>>
>>> >sage --python --version
>>> Python 3.10.9
>>>
>>> >sage
>>> ──┐
>>> │ SageMath version 9.8, Release Date: 2023-02-11 │
>>> │ Using Python 3.10.9. Type "help()" for help.   │
>>> └──
>>>
>>> Any idea why 9.8 did not use sagemath python which is supposed to be
>>> 3.11.1 like 9.8 rc1 did? This is all on same Linux virtual box
>>>
>>> >lsb_release -a
>>> LSB Version:n/a
>>> Distributor ID:ManjaroLinux
>>> Description:Manjaro Linux
>>> Release:22.0.2
>>> Codename:Sikaris
>>>
>>> >uname -r
>>> 6.1.9-1-MANJARO
>>>
>>> I put the config.log and the build.log in this [folder](
>>> https://12000.org/tmp/sagemath_98_logs/)
>>>
>>> --Nasser
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Saturday, February 11, 2023 at 1:12:57 PM UTC-6 Volker Braun wrote:
>>>
 Apologies, the download link for the release is the "stable" version,
 not develop: https://www.sagemath.org/download-source.html

 At least one mirror already has it:
 https://mirrors.mit.edu/sage/src/index.html


 On Saturday, February 11, 2023 at 5:18:09 PM UTC+1 Nasser M. Abbasi
 wrote:

> Hello;
>
> When I go to  http://www.sagemath.org/download-latest.html  it says
> *sage-9.8.rc1.tar.gz*
>  as latest.
> I tried few mirrors and I do not see 9.8
>
> Is 9.8 supposed to be at one of these mirror sites to download?
>
> thanks
> --Nasser
>
> On Saturday, February 11, 2023 at 7:47:09 AM UTC-6 Volker Braun wrote:
>
>> The "master" git branch has been updated to Sage-9.8. 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
>>
>> And as you are undoubtedly aware, the git repository is now hosted at
>> https://github.com/sagemath/sage, so update your git remote.
>>
>> To commemorate the move (and because we are getting really close to
>> .10), I'm proposing to target Sage version 10 as the next release.
>>
>> The changes over 9.8.rc0 are mainly housekeeping for the new
>> repository location.
>>
>> I'll try to finish up merging remaining positively reviewed trac
>> issues, and then move on to github pull requests.
>>
>>
>> c000c953eb6 (HEAD -> develop, github/master, github/develop, tag:
>> 9.8) Updated SageMath version to 9.8
>> 104dde9eaa8 Merge pull request #35022 from
>> tobiasdiez/pr-template-title
>> 17d8a73296f Merge pull request #35018 from x4/public/35017
>> 6a4667bb5c5 Merge pull request #34983 from
>> tobiasdiez/add-issue-templates
>> 66b319baffb Merge pull request #35011 from dimpase/develop
>> 872b32b0c20 Merge pull request #34987 from
>> mezzarobba/missing_long_time
>> d57804e6dec Merge pull request #34964 from
>> x4/public/linter-20230206
>> 698001b0e6a remove prohibition, promise details

Re: [sage-release] Sage 9.8 on Debian testing

[Dima Pasechnik]

it would be interesting to have a look at logs/pkgs/singular*.log

On Sun, Feb 12, 2023 at 12:44 PM Thierry Dumont 
wrote:

>
>
> Le 12/02/2023 à 13:33, Dima Pasechnik a écrit :
> > /sage -tp src/sage/libs/singular/
>
> Ok this gives a segfault and may be other problems.
> (file joined)
> Thanks a lot.
>
> --
> 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/52337dc1-6e43-c372-03be-4dd4140d6c5e%40math.univ-lyon1.fr
> .
>

-- 
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/CAAWYfq2m2zF_o%3DaVGVythgH0KC8DBdKpWLKC8DXhf-a6KE53oA%40mail.gmail.com.

Re: [sage-release] Sage 9.8 on Debian testing

[Dima Pasechnik]

On Sun, Feb 12, 2023 at 9:19 AM Thierry Dumont 
wrote:

> Restarting from a fresh clone of 9.8 (from github):
>
> ./configure --without-system-singular (is it necessary now? it was with
> 9.8rc*)
>
> I got a problem building the documentation, which seems to be a segfault.
> Logfile is joined.
>
> But the compiled sage seems to run correctly.
>

do doctests involving Singular pass?
E.g.

./sage -tp src/sage/libs/singular/

?


>
> I got the same problem when trying to upgrade from the last 9.8rc to 9.8.
>
> My Debian testing is uptodate.
>
> t.d.
>
>
> --
> 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/fd45ed00-7b8c-0a23-957e-571c607315e8%40math.univ-lyon1.fr
> .
>

-- 
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/CAAWYfq0rPn7vt7aVbM6qnT20--UZ%2BCZtbNym%2BZErK3LRRAVcww%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.8 released

[Dima Pasechnik]

On Sun, Feb 12, 2023 at 9:10 AM 'Nasser M. Abbasi' via sage-release <
sage-release@googlegroups.com> wrote:

> Thanks. I downloaded 9.8 and build it OK. No errors building it.
>
> But unlike 9.8 rc1, I see that 9.8 is back to using system python which is
> 3.10.9 and not sagemath python 3.11.1 like 9.8 rc1 did, even though I used
> the same exact configuration commands.
>

there is absolutely nothing in the diff between 9.8.rc1 and 9.8 that would
explain this.
So it's the environment you built that was different - I don't know exactly
how.

But --with-system-python3 appears to be a noop. I could not find a place
where it is processed.
(it should be in build/pkgs/python3/spkg-configure.m4, IMHO)
I opened https://github.com/sagemath/sage/issues/35089

So it was a change in the build enviroment that made Sage accept python3



By the way, I noticed a bug in Sage along the way.
>From your config.log (and install) I see that you don't have pkg-config
installed.
It's actually a sort of a bug in configure; your system is similar to Arch
linux, and
the system package pkg-config is needed on Arch (and on Manjaro,  I suppose)
for the build to function correctly.

If you ran ./bootstrap (something should be a mandatory thing to do on
Linux for installing from source,
but let's not get into this here)
then it would force you to install pkg-config, as it is mentioned in
build/pkgs/_bootstrap/distros/arch.txt

- but you didn't, and as build/pkgs/_prereq/distros/arch.txt does not
mention pkg-config,
./configure didn't complain

I've opened https://github.com/sagemath/sage/issues/35088 for the latter
problem.




> These are the commands I used
>
> unset SAGE_ROOT
> unset SAGE_LOCAL
> ./configure --with-system-python=no
> make
> make install
>
>
> And now from a new terminal I type
>
> >which python
> /usr/bin/python
>
> >python --version
> Python 3.10.9
>
> >sage --version
> SageMath version 9.8, Release Date: 2023-02-11
>
> >sage --python --version
> Python 3.10.9
>
> >sage
> ──┐
> │ SageMath version 9.8, Release Date: 2023-02-11 │
> │ Using Python 3.10.9. Type "help()" for help.   │
> └──
>
> Any idea why 9.8 did not use sagemath python which is supposed to be
> 3.11.1 like 9.8 rc1 did? This is all on same Linux virtual box
>
> >lsb_release -a
> LSB Version:n/a
> Distributor ID:ManjaroLinux
> Description:Manjaro Linux
> Release:22.0.2
> Codename:Sikaris
>
> >uname -r
> 6.1.9-1-MANJARO
>
> I put the config.log and the build.log in this [folder](
> https://12000.org/tmp/sagemath_98_logs/)
>
> --Nasser
>
>
>
>
>
>
> On Saturday, February 11, 2023 at 1:12:57 PM UTC-6 Volker Braun wrote:
>
>> Apologies, the download link for the release is the "stable" version, not
>> develop: https://www.sagemath.org/download-source.html
>>
>> At least one mirror already has it:
>> https://mirrors.mit.edu/sage/src/index.html
>>
>>
>> On Saturday, February 11, 2023 at 5:18:09 PM UTC+1 Nasser M. Abbasi wrote:
>>
>>> Hello;
>>>
>>> When I go to  http://www.sagemath.org/download-latest.html  it says
>>> *sage-9.8.rc1.tar.gz*
>>>  as latest.  I
>>> tried few mirrors and I do not see 9.8
>>>
>>> Is 9.8 supposed to be at one of these mirror sites to download?
>>>
>>> thanks
>>> --Nasser
>>>
>>> On Saturday, February 11, 2023 at 7:47:09 AM UTC-6 Volker Braun wrote:
>>>
 The "master" git branch has been updated to Sage-9.8. 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

 And as you are undoubtedly aware, the git repository is now hosted at
 https://github.com/sagemath/sage, so update your git remote.

 To commemorate the move (and because we are getting really close to
 .10), I'm proposing to target Sage version 10 as the next release.

 The changes over 9.8.rc0 are mainly housekeeping for the new repository
 location.

 I'll try to finish up merging remaining positively reviewed trac
 issues, and then move on to github pull requests.


 c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8)
 Updated SageMath version to 9.8
 104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
 17d8a73296f Merge pull request #35018 from x4/public/35017
 6a4667bb5c5 Merge pull request #34983 from
 tobiasdiez/add-issue-templates
 66b319baffb Merge pull request #35011 from dimpase/develop
 872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
 d57804e6dec Merge pull request #34964 from x4/public/linter-20230206
 698001b0e6a remove prohibition, promise details
 0c5f7baf6c2 remove trac references, promise details soon
 200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1

Re: [sage-release] Sage 9.8 released

[Dima Pasechnik]

On Sat, Feb 11, 2023 at 10:31 PM Matthias Köppe 
wrote:

> Neither the "dist.yml" nor the "ci-..." workflows have run on the push to
> the 9.8 tag on sagemath/sage.
> I'll investigate.
>

I've also created the GitHub release 9.8 manually. (The tag was created,
the release was not)


>
> On Saturday, February 11, 2023 at 1:54:43 PM UTC-8 François Bissey wrote:
>
>> When will we have packages up on pypi? I now rely on these for stable
>> release in sage-on-gentoo.
>>
>> François
>>
>> On 12/02/23 02:47, Volker Braun wrote:
>> > The "master" git branch has been updated to Sage-9.8. 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
>> >
>> > And as you are undoubtedly aware, the git repository is now hosted
>> > at https://github.com/sagemath/sage, so update your git remote.
>> >
>> > To commemorate the move (and because we are getting really close to
>> > .10), I'm proposing to target Sage version 10 as the next release.
>> >
>> > The changes over 9.8.rc0 are mainly housekeeping for the new repository
>> > location.
>> >
>> > I'll try to finish up merging remaining positively reviewed trac
>> issues,
>> > and then move on to github pull requests.
>> >
>> > c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8)
>> > Updated SageMath version to 9.8
>> > 104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
>> > 17d8a73296f Merge pull request #35018 from x4/public/35017
>> > 6a4667bb5c5 Merge pull request #34983 from
>> tobiasdiez/add-issue-templates
>> > 66b319baffb Merge pull request #35011 from dimpase/develop
>> > 872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
>> > d57804e6dec Merge pull request #34964 from
>> x4/public/linter-20230206
>> > 698001b0e6a remove prohibition, promise details
>> > 0c5f7baf6c2 remove trac references, promise details soon
>> > 200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "sage-release" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to sage-release...@googlegroups.com
>> > .
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com
>> <
>> https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com?utm_medium=email_source=footer>.
>>
>>
> --
> 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/0386f230-5ea3-44b8-9a98-4e60b988cf1fn%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/CAAWYfq0342hoRwVnAurDb4DmwobsZgB%3D2PStOF%2BLXFUfoy0Vag%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.8 released

[Dima Pasechnik]

On Sat, Feb 11, 2023 at 4:18 PM 'Nasser M. Abbasi' via sage-release <
sage-release@googlegroups.com> wrote:

> Hello;
>
> When I go to  http://www.sagemath.org/download-latest.html  it says
> *sage-9.8.rc1.tar.gz*
>  as latest.  I
> tried few mirrors and I do not see 9.8
>
> Is 9.8 supposed to be at one of these mirror sites to download?
>

https://github.com/sagemath/sage/releases

(or just use git)


>
> thanks
> --Nasser
>
> On Saturday, February 11, 2023 at 7:47:09 AM UTC-6 Volker Braun wrote:
>
>> The "master" git branch has been updated to Sage-9.8. 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
>>
>> And as you are undoubtedly aware, the git repository is now hosted at
>> https://github.com/sagemath/sage, so update your git remote.
>>
>> To commemorate the move (and because we are getting really close to .10),
>> I'm proposing to target Sage version 10 as the next release.
>>
>> The changes over 9.8.rc0 are mainly housekeeping for the new repository
>> location.
>>
>> I'll try to finish up merging remaining positively reviewed trac issues,
>> and then move on to github pull requests.
>>
>>
>> c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8)
>> Updated SageMath version to 9.8
>> 104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
>> 17d8a73296f Merge pull request #35018 from x4/public/35017
>> 6a4667bb5c5 Merge pull request #34983 from tobiasdiez/add-issue-templates
>> 66b319baffb Merge pull request #35011 from dimpase/develop
>> 872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
>> d57804e6dec Merge pull request #34964 from x4/public/linter-20230206
>> 698001b0e6a remove prohibition, promise details
>> 0c5f7baf6c2 remove trac references, promise details soon
>> 200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1
>>
> --
> 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/be983746-2404-4087-ae3c-525f395ad8e5n%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/CAAWYfq3Boa4XN0KN6jEDrF62FNj2o5rWcdLgWEj%3DoirZBNhfoA%40mail.gmail.com.

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

[Dima Pasechnik]

On Mon, 6 Feb 2023, 15:10 fchap...@gmail.com,  wrote:

> why is the "develop" branch now two commits after the 9.8.rc1 release?
>

because they rectify misleading templates for PRs and issues, as you can
see.


> Frédéric
>
> Le dimanche 5 février 2023 à 15:14:57 UTC+1, Volker Braun a écrit :
>
>> Note: the old trac git server is already disabled and the new
>> https://github.com/sagemath/sage is still locked for migration, so you
>> will only be able to get the branch from there starting tomorrow (Monday).
>> If you are dying to see the new version you can temporarily get it from my
>> own fork at github.com:vbraun/sage, but I'd recommend waiting until
>> tomorrow.
>>
>> 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
>>
>>
>> 200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to
>> 9.8.rc1
>> 2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for
>> portability workflows
>> 1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
>> 77173ef550c Trac #34873: Deprecate
>> sage.homology.graded_resolution.GradedFreeResolution
>> 9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to
>> 9.8.rc0
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/40db8677-ab03-432e-bdd2-8ccb689e419bn%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/CAAWYfq04HHkubNX94x%3D8tOnqqvmRi-ZayXPOg6F0W_R0O1FTAg%40mail.gmail.com.

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

[Dima Pasechnik]

You also were saying that you have MAXIMA set to an installation of Maxima.

Note that Sage won't be able to use it. Sage uses Maxima in two ways:
as a Python module embedding ECL (with Maxima installed there)
and (something we work on to get rid of) interacting with Maxima built
with ECL with pexpect (Unix pipes, more or less).
While the latter may in principle use different Maxima installation,
this is not implemented.




On Sun, Feb 5, 2023 at 12:56 PM Dima Pasechnik  wrote:
>
> On Sun, Feb 5, 2023 at 12:44 PM 'Nasser M. Abbasi' via sage-release
>  wrote:
> >
> >
> > I agree with you. I think the best thing for me, is just to make a brand 
> > new Virtual box, and install a new Linux and start everything from clean 
> > system. It will take me 2-3 days as I have to install few things I need, 
> > Then will try installing sagemath again after that.
>
> you can try to temporarily move /usr/local somewhere, and see if it
> helps; no need to rebuild the whole Sage then, just rebuild
> scipy:
>
> make scipy-clean scipy-uninstall
> make scipy
>
> Then start sage
>
>  ./sage
>
> and run
>
>  sage:  import scipy
>
> there. If this works, run
>
> make
>
> to see if it finishes fine.
>
> >
> > Thanks for the help.
> > --Nasser
> >
> > On Sunday, February 5, 2023 at 5:58:14 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> I suspect you have an installation of openblas, or/and some other
> >> blas/lapack, in /usr/local - and this results in scipy being unable
> >> to link it correctly.
> >>
> >>
> >> (or perhaps it's not /usr/local, but some other location known to 
> >> pkg-config)
> >>
> >> numpy and scipy accumulated ~20 years of layer upon layer of old
> >> outdated code for recognising BLAS/LAPACK libraries, it's such a
> >> nightmare to debug.
> >>
> >>
> >>
> >> On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
> >>  wrote:
> >> >
> >> > Here is the output for the new command you posted
> >> >
> >> > >ldd 
> >> > >local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
> >> > linux-vdso.so.1 (0x7ffd883d4000)
> >> > libcblas.so.3 => /usr/lib/libcblas.so.3 (0x7f25a6532000)
> >> > libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
> >> > libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
> >> > libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
> >> > /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
> >> > libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
> >> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
> >> > >
> >> >
> >> > I've also put in same folder here a file called log_folders.tar.gz which 
> >> > is backup of the logs/ folder in my build tree of 9.8 rc0 so it will 
> >> > have the logs you asked for.
> >> >
> >> > any other information needed please let me know.
> >> > --Nasser
> >> >
> >> >
> >> > On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
> >> >>
> >> >> On Sun, Feb 5, 2023 at 9:58 AM Dima Pasechnik  wrote:
> >> >> >
> >> >> > On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
> >> >> >  wrote:
> >> >> > >
> >> >> > >
> >> >> > > Here is the output
> >> >> > >
> >> >> > > >ldd 
> >> >> > > >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> >> >> > > linux-vdso.so.1 (0x7ffc53be9000)
> >> >> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> >> >> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> >> >> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> >> >> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> >> >> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> >> >> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> >> >> > > (0x7fc232444000)
> >> >> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)

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

[Dima Pasechnik]

On Sun, Feb 5, 2023 at 12:44 PM 'Nasser M. Abbasi' via sage-release
 wrote:
>
>
> I agree with you. I think the best thing for me, is just to make a brand new 
> Virtual box, and install a new Linux and start everything from clean system. 
> It will take me 2-3 days as I have to install few things I need, Then will 
> try installing sagemath again after that.

you can try to temporarily move /usr/local somewhere, and see if it
helps; no need to rebuild the whole Sage then, just rebuild
scipy:

make scipy-clean scipy-uninstall
make scipy

Then start sage

 ./sage

and run

 sage:  import scipy

there. If this works, run

make

to see if it finishes fine.

>
> Thanks for the help.
> --Nasser
>
> On Sunday, February 5, 2023 at 5:58:14 AM UTC-6 Dima Pasechnik wrote:
>>
>> I suspect you have an installation of openblas, or/and some other
>> blas/lapack, in /usr/local - and this results in scipy being unable
>> to link it correctly.
>>
>>
>> (or perhaps it's not /usr/local, but some other location known to pkg-config)
>>
>> numpy and scipy accumulated ~20 years of layer upon layer of old
>> outdated code for recognising BLAS/LAPACK libraries, it's such a
>> nightmare to debug.
>>
>>
>>
>> On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
>>  wrote:
>> >
>> > Here is the output for the new command you posted
>> >
>> > >ldd 
>> > >local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
>> > linux-vdso.so.1 (0x7ffd883d4000)
>> > libcblas.so.3 => /usr/lib/libcblas.so.3 (0x7f25a6532000)
>> > libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
>> > libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
>> > libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
>> > /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
>> > libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
>> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
>> > >
>> >
>> > I've also put in same folder here a file called log_folders.tar.gz which 
>> > is backup of the logs/ folder in my build tree of 9.8 rc0 so it will have 
>> > the logs you asked for.
>> >
>> > any other information needed please let me know.
>> > --Nasser
>> >
>> >
>> > On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
>> >>
>> >> On Sun, Feb 5, 2023 at 9:58 AM Dima Pasechnik  wrote:
>> >> >
>> >> > On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
>> >> >  wrote:
>> >> > >
>> >> > >
>> >> > > Here is the output
>> >> > >
>> >> > > >ldd 
>> >> > > >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>> >> > > linux-vdso.so.1 (0x7ffc53be9000)
>> >> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
>> >> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
>> >> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
>> >> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
>> >> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
>> >> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
>> >> > > (0x7fc232444000)
>> >> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>> >> >
>> >> > here is how it looks on a non-broken installation.
>> >> >
>> >> > $ ldd 
>> >> > local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>> >> > linux-vdso.so.1 (0x7ffe6b935000)
>> >> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
>> >> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
>> >> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
>> >> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
>> >> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
>> >> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
>> >> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x000

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

[Dima Pasechnik]

I suspect you have an installation of openblas, or/and some other
blas/lapack, in /usr/local - and this results in scipy being unable
to link it correctly.


(or perhaps it's not /usr/local, but some other location known to pkg-config)

numpy and scipy accumulated ~20 years of layer upon layer of old
outdated code for recognising BLAS/LAPACK libraries, it's such a
nightmare to debug.



On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
 wrote:
>
> Here is the output for the new command you posted
>
> >ldd 
> >local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
> linux-vdso.so.1 (0x7ffd883d4000)
> libcblas.so.3 => /usr/lib/libcblas.so.3 (0x7f25a6532000)
> libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
> libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
> libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
> libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
> libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
> >
>
> I've also put in same folder here  a file called log_folders.tar.gz  which is 
> backup of the logs/ folder in my build tree of 9.8 rc0 so it will have the 
> logs you asked for.
>
> any other information needed please let me know.
> --Nasser
>
>
> On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
>>
>> On Sun, Feb 5, 2023 at 9:58 AM Dima Pasechnik  wrote:
>> >
>> > On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
>> >  wrote:
>> > >
>> > >
>> > > Here is the output
>> > >
>> > > >ldd 
>> > > >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>> > > linux-vdso.so.1 (0x7ffc53be9000)
>> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
>> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
>> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
>> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
>> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
>> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 (0x7fc232444000)
>> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>> >
>> > here is how it looks on a non-broken installation.
>> >
>> > $ ldd 
>> > local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>> > linux-vdso.so.1 (0x7ffe6b935000)
>> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
>> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
>> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
>> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
>> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
>> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
>> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
>> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
>> >
>> > As you see, in your case libopenblas.so is not there, and you have an
>> > error due to this.
>> > Why scipy builds such a broken module, I don't know. I'd say it's a scipy 
>> > bug.
>> >
>> > Please post logs/pkgs/numpy* and logs/pkgs/scipy*
>>
>> please also check that
>>
>> ldd 
>> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
>>
>> has openblas in its output.
>>
>> >
>> >
>> > > >
>> > >
>> > > "You should add fpylll at the end of the line in
>> > >
>> > > build/pkgs/sagemath_doc_html/dependencies
>> > >
>> > > and run ./configure and make again"
>> > >
>> > > Ok thanks. Will give this a try.
>> > >
>> > > "sage in a different directory which is in your PATH typically breaks 
>> > > things"
>> > >
>> > > but it is NOT in the path. This is the reason I do
>> > >
>> > > unset SAGE_ROOT
>> > > unset SAGE_LOCAL
>> > >
>> > > before building any new release. I make sure current installed sagemath 
>> > > (in different folder) i

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

[Dima Pasechnik]

On Sun, Feb 5, 2023 at 9:58 AM Dima Pasechnik  wrote:
>
> On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
>  wrote:
> >
> >
> > Here is the output
> >
> > >ldd 
> > >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> > linux-vdso.so.1 (0x7ffc53be9000)
> > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> > (0x7fc232444000)
> > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>
> here is how it looks on a non-broken installation.
>
> $ ldd 
> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> linux-vdso.so.1 (0x7ffe6b935000)
> libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
> libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
> libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
> libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
> libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
> libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
> /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
>
> As you see, in your case libopenblas.so is not there, and you have an
> error due to this.
> Why scipy builds such a broken module, I don't know. I'd say it's a scipy bug.
>
> Please post logs/pkgs/numpy* and logs/pkgs/scipy*

please also check that

ldd 
local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so

has openblas in its output.

>
>
> > >
> >
> > "You should add fpylll at the end of the line in
> >
> > build/pkgs/sagemath_doc_html/dependencies
> >
> > and run ./configure and make again"
> >
> > Ok thanks. Will give this a try.
> >
> > "sage in a different directory which is in your PATH typically breaks 
> > things"
> >
> > but it is NOT in the path. This is the reason I do
> >
> > unset SAGE_ROOT
> >unset SAGE_LOCAL
> >
> > before building any new release. I make sure current installed sagemath (in 
> > different folder) is not visible.
> >
> > --Nasser
> >
> > On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> On Sat, Feb 4, 2023 at 1:51 PM 'Nasser M. Abbasi' via sage-release
> >>  wrote:
> >> >
> >> > "Was it an incremental build. If so,
> >> > make distclean
> >> > and
> >> > build again from scratch."
> >> >
> >> > It was not an incremental build. I extracted the gzip file and did the 
> >> > steps I showed. So I do not need to do "make distclean" since everything 
> >> > is new.
> >> >
> >> > But I repeated now everything again using "make distclean" and got same 
> >> > error.
> >> >
> >> > "Probably the problem is linking with openblas. Do you have a number of 
> >> > openblas versions accessible to the linker?"
> >> >
> >> > I have no idea. What command should I use to check?
> >>
> >> run
> >>
> >> ldd 
> >> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> >>
> >> Post its output
> >> - there should be an openblas mentioned, the question is which one.
> >>
> >> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
> >> https://trac.sagemath.org/ticket/34940
> >>
> >> You should add fpylll at the end of the line in
> >>
> >> build/pkgs/sagemath_doc_html/dependencies
> >>
> >> and run ./configure and make again
> >>
> >>
> >>
> >>
> >> >
> >> > I am just following the instruction to download and install sagemath.
> >> >
> >> > I have giac and maxima and fricas and texlive already in

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

[Dima Pasechnik]

On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
 wrote:
>
>
> Here is the output
>
> >ldd 
> >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> linux-vdso.so.1 (0x7ffc53be9000)
> libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 (0x7fc232444000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)

here is how it looks on a non-broken installation.

$ ldd 
local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
linux-vdso.so.1 (0x7ffe6b935000)
libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
/lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)

As you see, in your case libopenblas.so is not there, and you have an
error due to this.
Why scipy builds such a broken module, I don't know. I'd say it's a scipy bug.

Please post logs/pkgs/numpy* and logs/pkgs/scipy*


> >
>
> "You should add fpylll at the end of the line in
>
> build/pkgs/sagemath_doc_html/dependencies
>
> and run ./configure and make again"
>
> Ok thanks. Will give this a try.
>
> "sage in a different directory which is in your PATH typically breaks things"
>
> but it is NOT in the path. This is the reason I do
>
> unset SAGE_ROOT
>unset SAGE_LOCAL
>
> before building any new release. I make sure current installed sagemath (in 
> different folder) is not visible.
>
> --Nasser
>
> On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
>>
>> On Sat, Feb 4, 2023 at 1:51 PM 'Nasser M. Abbasi' via sage-release
>>  wrote:
>> >
>> > "Was it an incremental build. If so,
>> > make distclean
>> > and
>> > build again from scratch."
>> >
>> > It was not an incremental build. I extracted the gzip file and did the 
>> > steps I showed. So I do not need to do "make distclean" since everything 
>> > is new.
>> >
>> > But I repeated now everything again using "make distclean" and got same 
>> > error.
>> >
>> > "Probably the problem is linking with openblas. Do you have a number of 
>> > openblas versions accessible to the linker?"
>> >
>> > I have no idea. What command should I use to check?
>>
>> run
>>
>> ldd 
>> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>>
>> Post its output
>> - there should be an openblas mentioned, the question is which one.
>>
>> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
>> https://trac.sagemath.org/ticket/34940
>>
>> You should add fpylll at the end of the line in
>>
>> build/pkgs/sagemath_doc_html/dependencies
>>
>> and run ./configure and make again
>>
>>
>>
>>
>> >
>> > I am just following the instruction to download and install sagemath.
>> >
>> > I have giac and maxima and fricas and texlive already installed on this 
>> > virtual box already. I also have sagemath 9.7 installed in different 
>> > folder.
>> >
>> > --Nasser
>> >
>> >
>> > On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
>> >>
>> >> Hello,
>> >> Was it an incremental build. If so,
>> >> make distclean
>> >> and
>> >> build again from scratch.
>> >>
>> >> Anyhow, if you look in your istall.log you'll see problems with a number 
>> >> of packages, e.g. fpylll, scipy.
>> >>
>> >> [sagemath_doc_html-none] [manifolds] ImportError: 
>> >> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.1

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

[Dima Pasechnik]

one source of trouble might be your

 LD_LIBRARY_PATH=/usr/local/lib:/mnt/g/public_html/scripts:

setting. Build systems are usually ignoring it, linking with "correct"
libraries,
but at runtime (e.g., while importing a Python module using libraries)
this might result in picking a wrong library.




On Sat, Feb 4, 2023 at 3:14 PM Dima Pasechnik  wrote:
>
> On Sat, Feb 4, 2023 at 1:51 PM 'Nasser M. Abbasi' via sage-release
>  wrote:
> >
> > "Was it  an incremental build. If so,
> >make distclean
> > and
> > build again from scratch."
> >
> > It was not an incremental build. I extracted the gzip file and did the 
> > steps I showed. So I do not need to do "make distclean" since everything is 
> > new.
> >
> > But I repeated now everything again using "make distclean" and got same 
> > error.
> >
> > "Probably the problem is linking with openblas. Do you have a number of 
> > openblas versions accessible to the linker?"
> >
> > I have no idea.  What command should I use to check?
>
> run
>
> ldd 
> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
>
> Post its output
> - there should be an openblas mentioned, the question is which one.
>
> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
> https://trac.sagemath.org/ticket/34940
>
> You should add fpylll at the end of the line in
>
> build/pkgs/sagemath_doc_html/dependencies
>
> and run ./configure and make again
>
>
>
>
> >
> > I am just following the instruction to download and install sagemath.
> >
> > I have giac and maxima and fricas and texlive already installed on this 
> > virtual box already. I also have sagemath 9.7 installed in different folder.
> >
> > --Nasser
> >
> >
> > On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> Hello,
> >> Was it  an incremental build. If so,
> >>make distclean
> >> and
> >> build again from scratch.
> >>
> >> Anyhow, if you look in your istall.log you'll see problems with a number 
> >> of packages, e.g. fpylll, scipy.
> >>
> >> [sagemath_doc_html-none] [manifolds] ImportError: 
> >> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
> >>  undefined symbol: dstevr_
> >>
> >> Probably the problem is linking with openblas. Do you have a number of 
> >> openblas versions accessible to the linker?
> >>
> >>
> >>
> >> By the way,
> >> what are you trying to achieve with exporting
> >> MAXIMA ?
> >> Sage does not support using external Maxima at the moment,
> >>
> >>
> >>
> >>
> >> On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, 
> >>  wrote:
> >>>
> >>> I get this error on Linux virtual box running
> >>>
> >>> lsb_release -a
> >>> LSB Version:n/a
> >>> Distributor ID:ManjaroLinux
> >>> Description:Manjaro Linux
> >>> Release:22.0.0
> >>> Codename:Sikaris
> >>>
> >>> After extracting the gzip file, these are the commands I did
> >>>
> >>> unset SAGE_ROOT
> >>>  unset SAGE_LOCAL
> >>>  export GIAC=/usr/local/bin/giac
> >>> export MAXIMA=/usr/local/bin/maxima
> >>> ./configure --with-system-python=no
> >>> make
> >>>
> >>> At the end I see
> >>>
> >>> -
> >>> sagemath_doc_html-none]   File 
> >>> "/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, 
> >>> in raise_errors
> >>> [sagemath_doc_html-none] raise OSError(self._error)
> >>> [sagemath_doc_html-none] OSError: 
> >>> /home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of 
> >>> sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in 
> >>> plotting chart-1
> >>> [sagemath_doc_html-none]
> >>> [sagemath_doc_html-none] Note: incremental documentation builds 
> >>> sometimes cause spurious
> >>> [sagemath_doc_html-none] error messages. To be certain that these are 
> >>> real errors, run
> >>> [sagemath_doc_html-none] "make d

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

[Dima Pasechnik]

On Sat, Feb 4, 2023 at 1:51 PM 'Nasser M. Abbasi' via sage-release
 wrote:
>
> "Was it  an incremental build. If so,
>make distclean
> and
> build again from scratch."
>
> It was not an incremental build. I extracted the gzip file and did the steps 
> I showed. So I do not need to do "make distclean" since everything is new.
>
> But I repeated now everything again using "make distclean" and got same error.
>
> "Probably the problem is linking with openblas. Do you have a number of 
> openblas versions accessible to the linker?"
>
> I have no idea.  What command should I use to check?

run

ldd 
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so

Post its output
- there should be an openblas mentioned, the question is which one.

As far as fpylll is concerned, you've hit the bug fixed in not yet merged
https://trac.sagemath.org/ticket/34940

You should add fpylll at the end of the line in

build/pkgs/sagemath_doc_html/dependencies

and run ./configure and make again




>
> I am just following the instruction to download and install sagemath.
>
> I have giac and maxima and fricas and texlive already installed on this 
> virtual box already. I also have sagemath 9.7 installed in different folder.
>
> --Nasser
>
>
> On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
>>
>> Hello,
>> Was it  an incremental build. If so,
>>make distclean
>> and
>> build again from scratch.
>>
>> Anyhow, if you look in your istall.log you'll see problems with a number of 
>> packages, e.g. fpylll, scipy.
>>
>> [sagemath_doc_html-none] [manifolds] ImportError: 
>> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
>>  undefined symbol: dstevr_
>>
>> Probably the problem is linking with openblas. Do you have a number of 
>> openblas versions accessible to the linker?
>>
>>
>>
>> By the way,
>> what are you trying to achieve with exporting
>> MAXIMA ?
>> Sage does not support using external Maxima at the moment,
>>
>>
>>
>>
>> On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, 
>>  wrote:
>>>
>>> I get this error on Linux virtual box running
>>>
>>> lsb_release -a
>>> LSB Version:n/a
>>> Distributor ID:ManjaroLinux
>>> Description:Manjaro Linux
>>> Release:22.0.0
>>> Codename:Sikaris
>>>
>>> After extracting the gzip file, these are the commands I did
>>>
>>> unset SAGE_ROOT
>>>  unset SAGE_LOCAL
>>>  export GIAC=/usr/local/bin/giac
>>> export MAXIMA=/usr/local/bin/maxima
>>> ./configure --with-system-python=no
>>> make
>>>
>>> At the end I see
>>>
>>> -
>>> sagemath_doc_html-none]   File 
>>> "/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, in 
>>> raise_errors
>>> [sagemath_doc_html-none] raise OSError(self._error)
>>> [sagemath_doc_html-none] OSError: 
>>> /home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of 
>>> sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in 
>>> plotting chart-1
>>> [sagemath_doc_html-none]
>>> [sagemath_doc_html-none] Note: incremental documentation builds 
>>> sometimes cause spurious
>>> [sagemath_doc_html-none] error messages. To be certain that these are 
>>> real errors, run
>>> [sagemath_doc_html-none] "make doc-clean doc-uninstall" first and try 
>>> again.
>>> [sagemath_doc_html-none] make[6]: *** [Makefile:28: 
>>> doc-inventory--reference-manifolds] Error 1
>>> [sagemath_doc_html-none] make[5]: *** [Makefile:45: 
>>> doc-inventory-reference] Error 2
>>> make[4]: *** [Makefile:3262: sagemath_doc_html-SAGE_DOCS-no-deps] Error 2
>>> make[3]: *** [Makefile:3262: 
>>> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/installed/sagemath_doc_html-none]
>>>  Error 2
>>> make[2]: *** [Makefile:2766: all-start] Error 2
>>> make[2]: Leaving directory '/home/me/TMP/sage-9.8.rc0/build/make'
>>>
>>> real71m30.833s
>>> user103m7.355s
>>> sys5m48.306s
>>> ***
>>> Error building Sage.
>>>
>>> The following package(s) may hav

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

[Dima Pasechnik]

On Sat, 4 Feb 2023, 13:51 'Nasser M. Abbasi' via sage-release, <
sage-release@googlegroups.com> wrote:

> "Was it  an incremental build. If so,
>make distclean
> and
> build again from scratch."
>
> It was not an incremental build. I extracted the gzip file and did the
> steps I showed. So I do not need to do "make distclean" since everything is
> new.
>
> But I repeated now everything again using "make distclean" and got same
> error.
>
> "Probably the problem is linking with openblas. Do you have a number of
> openblas versions accessible to the linker?"
>
> I have no idea.  What command should I use to check?
>
> I am just following the instruction to download and install sagemath.
>
> I have giac and maxima and fricas and texlive already installed on this
> virtual box already. I also have sagemath 9.7 installed in different folder.
>

sage in a different directory which is in your PATH typically breaks things.



> --Nasser
>
>
> On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
>
>> Hello,
>> Was it  an incremental build. If so,
>>make distclean
>> and
>> build again from scratch.
>>
>> Anyhow, if you look in your istall.log you'll see problems with a number
>> of packages, e.g. fpylll, scipy.
>>
>> [sagemath_doc_html-none] [manifolds] ImportError: 
>> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
>>  undefined symbol: dstevr_
>>
>> Probably the problem is linking with openblas. Do you have a number of 
>> openblas versions accessible to the linker?
>>
>>
>>
>> By the way,
>> what are you trying to achieve with exporting
>> MAXIMA ?
>> Sage does not support using external Maxima at the moment,
>>
>>
>>
>>
>> On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, <
>> sage-r...@googlegroups.com> wrote:
>>
>>> I get this error on Linux virtual box running
>>>
>>> lsb_release -a
>>> LSB Version:n/a
>>> Distributor ID:ManjaroLinux
>>> Description:Manjaro Linux
>>> Release:22.0.0
>>> Codename:Sikaris
>>>
>>> After extracting the gzip file, these are the commands I did
>>>
>>> unset SAGE_ROOT
>>>  unset SAGE_LOCAL
>>>  export GIAC=/usr/local/bin/giac
>>> export MAXIMA=/usr/local/bin/maxima
>>> ./configure --with-system-python=no
>>> make
>>>
>>> At the end I see
>>>
>>> -
>>> sagemath_doc_html-none]   File
>>> "/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, in
>>> raise_errors
>>> [sagemath_doc_html-none] raise OSError(self._error)
>>> [sagemath_doc_html-none] OSError:
>>> /home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of
>>> sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in
>>> plotting chart-1
>>> [sagemath_doc_html-none]
>>> [sagemath_doc_html-none] Note: incremental documentation builds
>>> sometimes cause spurious
>>> [sagemath_doc_html-none] error messages. To be certain that these
>>> are real errors, run
>>> [sagemath_doc_html-none] "make doc-clean doc-uninstall" first and
>>> try again.
>>> [sagemath_doc_html-none] make[6]: *** [Makefile:28:
>>> doc-inventory--reference-manifolds] Error 1
>>> [sagemath_doc_html-none] make[5]: *** [Makefile:45:
>>> doc-inventory-reference] Error 2
>>> make[4]: *** [Makefile:3262: sagemath_doc_html-SAGE_DOCS-no-deps] Error 2
>>> make[3]: *** [Makefile:3262:
>>> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/installed/sagemath_doc_html-none]
>>> Error 2
>>> make[2]: *** [Makefile:2766: all-start] Error 2
>>> make[2]: Leaving directory '/home/me/TMP/sage-9.8.rc0/build/make'
>>>
>>> real71m30.833s
>>> user103m7.355s
>>> sys5m48.306s
>>> *******
>>> Error building Sage.
>>>
>>> The following package(s) may have failed to build (not necessarily
>>> during this run of 'make all-start'):
>>>
>>> It is safe to delete any log files and build directories, but they
>>> contain information that is helpful for debugging build problems.
>>> WARNING: If you now run 'make' again, the build directory of the
>>> same ve

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

[Dima Pasechnik]

Hello,
Was it  an incremental build. If so,
   make distclean
and
build again from scratch.

Anyhow, if you look in your istall.log you'll see problems with a number of
packages, e.g. fpylll, scipy.

[sagemath_doc_html-none] [manifolds] ImportError:
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
undefined symbol: dstevr_

Probably the problem is linking with openblas. Do you have a number of
openblas versions accessible to the linker?



By the way,
what are you trying to achieve with exporting
MAXIMA ?
Sage does not support using external Maxima at the moment,




On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, <
sage-release@googlegroups.com> wrote:

> I get this error on Linux virtual box running
>
> lsb_release -a
> LSB Version:n/a
> Distributor ID:ManjaroLinux
> Description:Manjaro Linux
> Release:22.0.0
> Codename:Sikaris
>
> After extracting the gzip file, these are the commands I did
>
> unset SAGE_ROOT
>  unset SAGE_LOCAL
>  export GIAC=/usr/local/bin/giac
> export MAXIMA=/usr/local/bin/maxima
> ./configure --with-system-python=no
> make
>
> At the end I see
>
> -
> sagemath_doc_html-none]   File
> "/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, in
> raise_errors
> [sagemath_doc_html-none] raise OSError(self._error)
> [sagemath_doc_html-none] OSError:
> /home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of
> sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in
> plotting chart-1
> [sagemath_doc_html-none]
> [sagemath_doc_html-none] Note: incremental documentation builds
> sometimes cause spurious
> [sagemath_doc_html-none] error messages. To be certain that these are
> real errors, run
> [sagemath_doc_html-none] "make doc-clean doc-uninstall" first and try
> again.
> [sagemath_doc_html-none] make[6]: *** [Makefile:28:
> doc-inventory--reference-manifolds] Error 1
> [sagemath_doc_html-none] make[5]: *** [Makefile:45:
> doc-inventory-reference] Error 2
> make[4]: *** [Makefile:3262: sagemath_doc_html-SAGE_DOCS-no-deps] Error 2
> make[3]: *** [Makefile:3262:
> /home/me/TMP/sage-9.8.rc0/local/var/lib/sage/installed/sagemath_doc_html-none]
> Error 2
> make[2]: *** [Makefile:2766: all-start] Error 2
> make[2]: Leaving directory '/home/me/TMP/sage-9.8.rc0/build/make'
>
> real71m30.833s
> user103m7.355s
> sys5m48.306s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version of the package will, by default, be deleted. Set the
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
> ----
>
> The following folder <https://12000.org/tmp/sagemath_logs/> contains
> config.log and install.log files
>
> Thank you
> --Nasser
>
>
>
>
>
>
> On Friday, February 3, 2023 at 3:40:20 AM UTC-6 Dima Pasechnik wrote:
>
>> On Fri, Feb 3, 2023 at 7:33 AM Sébastien Labbé  wrote:
>> >
>> >
>> >
>> > On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com
>> wrote:
>> > On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé
>> wrote:
>> > ./bootstrap: 9: m4: Permission denied
>> > make: *** [Makefile:365 : configure] Erreur 1
>> >
>> > Do you have "." in PATH?
>> >
>> >
>> > No
>> >
>> > What does "which m4" say?
>> >
>> >
>> > It returns nothing! Thanks for the hint. I found the problem: when
>> reading the sage README to install sage from scratch on this new machine, I
>> installed the basic stuff as follows:
>> >
>> > $ sudo apt install gcc gfortran g++ make m4 perl ranlib tar bc
>> > [...]
>> > E: Impossible de trouver le paquet ranlib
>> >
>> > But this returned an error on ranlib and I assumed it had installed the
>> other packages in the list but no, it did not (gcc, gfortran, etc. were not
>> installed as well).
>> >
>> > Is ranlib really needed for sage? Can we remove it from the README?
>>
>> ranlib is a standard tool, and is used by various build systems. On
>> Debian it's a part of binutils package.
>>
>> RE

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

[Dima Pasechnik]

On Fri, Feb 3, 2023 at 7:33 AM Sébastien Labbé  wrote:
>
>
>
> On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com wrote:
> On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote:
> ./bootstrap: 9: m4: Permission denied
> make: *** [Makefile:365 : configure] Erreur 1
>
> Do you have "." in PATH?
>
>
> No
>
> What does "which m4" say?
>
>
> It returns nothing! Thanks for the hint. I found the problem: when reading 
> the sage README to install sage from scratch on this new machine, I installed 
> the basic stuff as follows:
>
> $ sudo apt install gcc gfortran g++ make m4 perl ranlib tar bc
> [...]
> E: Impossible de trouver le paquet ranlib
>
> But this returned an error on ranlib and I assumed it had installed the other 
> packages in the list but no, it did not (gcc, gfortran, etc. were not 
> installed as well).
>
> Is ranlib really needed for sage? Can we remove it from the README?

ranlib is a standard tool, and is used by various build systems. On
Debian it's a part of binutils package.

README is not platform-specific, and it does not tell you to install
*package* called ranlib.
However, we should add there an advice to look for what packages to install in
build/pkgs/_prereq/distros/
(e.g. for Debian it's in build/pkgs/_prereq/distros/debian.txt)

(Once our GitHub is live in few days, it's a very quick PR to do :-))



>
>
>
> --
> 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/d6aecaee-279a-45f8-a645-36483d72a382n%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/CAAWYfq0DgfZTWUC5kd8sTJyv9xgvZmKADsJw06Euh42eB_hxaw%40mail.gmail.com.

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

[Dima Pasechnik]

On Thu, 2 Feb 2023, 17:30 Sébastien Labbé,  wrote:

> On another machine running Ubuntu 22.04, installing sage from source from
> scratch, I get "m4: Permission denied" error during the "make configure".
> Should I "sudo make configure" ?
>

no. Something it either off with permissions in SAGE_ROOT, or m4 is not
installed.

Or it's a bug that slipped in due to insufficient testing on machines
without installed autotools.


Never done that before...
>
> See below:
>
> $ make configure
> ./bootstrap -d
> make[1] : on entre dans le répertoire « /home/slabbe/GitBox/sage »
> rm -rf config/install-sh config/compile config/config.guess
> config/config.sub config/missing configure build/make/Makefile-auto.in
> rm -f src/doc/en/installation/*.txt
> rm -rf src/doc/en/reference/spkg/*.rst
> rm -f environment.yml
> rm -f src/environment.yml
> rm -f src/environment-dev.yml
> rm -f environment-optional.yml
> rm -f src/environment-optional.yml
> rm -f src/Pipfile
> rm -f src/pyproject.toml
> rm -f src/requirements.txt
> rm -f src/setup.cfg
> make[1] : on quitte le répertoire « /home/slabbe/GitBox/sage »
> bootstrap:: installing 'm4/sage_spkg_configures.m4'
> ./bootstrap: installing
> /home/slabbe/GitBox/sage/build/pkgs/sagemath_environment/src/pyproject.toml
> ./bootstrap: 9: m4: Permission denied
> make: *** [Makefile:365 : configure] Erreur 1
>
> --
> 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/3005af48-d9e6-4399-9575-1ac642258308n%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/CAAWYfq15wgr0gWT1T4srb-48hn-URJrHtjpAuD0-EYHLBTMpdQ%40mail.gmail.com.

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

[Dima Pasechnik]

On Wed, Jan 25, 2023 at 3:22 PM Emmanuel Charpentier
 wrote:
>
> After re-building 9.8.beta7 + #34935, running ptestlong gets me one more 
> permanent failure :
>
> ```
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 225.1 
> --random-seed=121252713509435388240223103279859468631 
> src/sage/schemes/elliptic_curves/hom_frobenius.py  # 1 doctest failed
> Running doctests with ID 2023-01-25-16-07-54-8bb572eb.
> Git branch: t/34935/interfaces-emacs
> Git ref: 9.8.beta7-1-g49d4ff78cc2
> Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
> SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
> Using 
> --optional=debian,dot2tex,fricas,gap_jupyter,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pari_jupyter,pint,pip,pysingular,sage,sage_spkg,singular_jupyter
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
> Doctesting 1 file.
> sage -t --long --warn-long 225.1 
> --random-seed=121252713509435388240223103279859468631 
> src/sage/schemes/elliptic_curves/hom_frobenius.py
> **
> File "src/sage/schemes/elliptic_curves/hom_frobenius.py", line 461, in 
> sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual
> Failed example:
> p in (2,3) or f.dual().dual() == f
> Exception raised:
> Traceback (most recent call last):
>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in 
> compile_and_execute
> exec(compiled, globs)
>   File " sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual[17]>",
>  line 1, in 
> p in (Integer(2),Integer(3)) or f.dual().dual() == f
>   File "sage/misc/cachefunc.pyx", line 2297, in 
> sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
> self.cache = f(self._instance)
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 
> 689, in dual
> return EllipticCurveHom_composite.from_factors(phis)
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 
> 364, in from_factors
> maps = tuple(maps)
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 
> 688, in 
> phis = (phi.dual() for phi in self._phis[::-1])
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_curve_isogeny.py", 
> line 3076, in dual
> corr = find_post_isomorphism(mult, rhs)
>   File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom.py", line 
> 856, in find_post_isomorphism
> isos = [iso for iso in isos if iso._eval(im_phi) == im_psi]
>   File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom.py", line 
> 856, in 
> isos = [iso for iso in isos if iso._eval(im_phi) == im_psi]
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/weierstrass_morphism.py", 
> line 586, in _eval
> return self._codomain.base_extend(k).point(Q)
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_generic.py", line 
> 1352, in base_extend
> E = constructor.EllipticCurve([R(a) for a in self.a_invariants()])
>   File 
> "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_generic.py", line 
> 1352, in 
> E = constructor.EllipticCurve([R(a) for a in self.a_invariants()])
>   File "sage/rings/finite_rings/element_givaro.pyx", line 1355, in 
> sage.rings.finite_rings.element_givaro.FiniteField_givaroElement.__int__
> raise TypeError("Cannot coerce element to an integer.")
> TypeError: Cannot coerce element to an integer.

Is it givaro from the system?
If so, can you try if building Sage's givaro helps?

> **
> 1 item had failures:
>1 of  19 in 
> sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual
> [117 tests, 1 failure, 0.91 s]
> --
> sage -t --long --warn-long 225.1 
> --random-seed=121252713509435388240223103279859468631 
> src/sage/schemes/elliptic_curves/hom_frobenius.py  # 1 doctest failed
> --
> Total 

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

[Dima Pasechnik]

On Wed, Jan 25, 2023 at 1:25 PM Enrique Artal  wrote:
>
> I guess the snappy problem is related to Fedora 37.  A tricky solution is 
> given by upstream team in https://github.com/3-manifolds/SnapPy/issues/88

snappy ships Cython-generated C files. That's the source of trouble...
:facepalm:
>
> El jueves, 19 de enero de 2023 a las 13:01:18 UTC+1, Enrique Artal escribió:
>>
>> I tried in another computer with the system package (3.11.1) and it worked 
>> but in both cases only after make distclean.
>> I lost the logs but sagelib complained about setup.
>> Snappy fails in both cases.
>>
>> El jueves, 19 de enero de 2023 a las 12:04:24 UTC+1, Dima Pasechnik escribió:
>>>
>>> What's wrong with Fedora's 37 Python3? (3.11.0, right?)
>>> What error do you see in config.log - which tells, hopefully, why it
>>> does not want system's python3 ?
>>>
>>> On Thu, Jan 19, 2023 at 9:43 AM Enrique Artal  wrote:
>>> >
>>> > In Fedora 37 I needed to `make distclean` and use the sage package for 
>>> > python3 and not the system one. The optional package snappy does not 
>>> > compile. Anyway, thanks for the new version. Best, Enrique.
>>> >
>>> > El jueves, 19 de enero de 2023 a las 0:48:25 UTC+1, Volker Braun escribió:
>>> >>
>>> >> 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
>>> >>
>>> >> We should probably gear up for a 9.8 release soon, so get your tickets 
>>> >> ready ;)
>>> >>
>>> >> 047281e0287 (trac/develop, tag: 9.8.beta7) Updated SageMath version to 
>>> >> 9.8.beta7
>>> >> 272c557d1f3 Trac #31668: Run TestSuite on polynomial rings
>>> >> 6f8fb9ba3ef Trac #22067: generating function of integral points of 
>>> >> polyhedra
>>> >> 5544a33b815 Trac #21003: Add package pyscipopt, add MIP backend
>>> >> b0422b2536b Trac #34838: setuptools_scm, contourpy, 
>>> >> sphinxcontrib_websupport, typing_extensions: Add missing dependencies
>>> >> 30d58156a46 Trac #34717: Check the presence of lrsnash for obtain_nash()
>>> >> c7299453922 Trac #34891: fixing some E502 in tensor, dynamics, modules, 
>>> >> plot, numerical
>>> >> bc832cb3578 Trac #34889: Installation guide: On WSL, clear /mnt/c stuff 
>>> >> from PATH
>>> >> 3570a9a63bd Trac #34881: allow to remove no constraints
>>> >> 0ceb1032430 Trac #34878: MixedIntegerLinearProgram.add_constraint: 
>>> >> Option to return row indices, fix handling of empty constraints
>>> >> df74efb66d2 Trac #34859: sagelib: Remove unnecessary import of 
>>> >> typing_extensions
>>> >> b6a76d7a848 Trac #34857: bump giac's GIAC_MIN_VERSION to 1.9
>>> >> 6a8155e6e5d Trac #34854: molien_series() should not use GAP's 
>>> >> VirtualCharacter
>>> >> dddf3ca0b08 Trac #34853: sage-env: Fix misconfiguration of pip
>>> >> 6f631021ac4 Trac #34847: modernize some for loops in cython files
>>> >> 9ffabc7f3e1 Trac #34844: removal of some unused imports about string 
>>> >> conversion
>>> >> 4b50bc2af27 Trac #34843: pep8 cleanup in ore_polynomial_element.pyx
>>> >> bdd14cec19b Trac #34837: fix E502 in some pyx files
>>> >> 172ad73ae38 Trac #34836: fix E271 and E272 in rings/ and schemes/
>>> >> 3d861266040 Trac #34749: Packages dsdp, scip_sdp
>>> >> 64d232b5bfd Trac #31329: Update scipoptsuite to 8.0.2 (now open 
>>> >> source!), rename to scip
>>> >> 2dcafb3ac57 Trac #34839: Support tox 4
>>> >> ad68f15d97f Trac #34648: Developer's guide: warn the transition to 
>>> >> GitHub and add links to the transition guide
>>> >> acebbc1a9e8 Trac #34824: do not include parent in hash of parking 
>>> >> functions
>>> >> 9a7b6310dde Trac #34818: Error when defining differentials over GCA's 
>>> >> with relations.
>>> >> bb63c582122 Trac #34807: Add Construction of Hadamard matrices up to 
>>> >> order 664
>>> >> 8a0b16d93be Trac #34804: Deprecate sage.interfaces is_...Element 
>>> >> functions
>>> >> 80f8f950e95 Trac #34793: clean 3 files inside modular
>>> >> b0cc282500e Trac #34547: Interfaces: use more lazy im

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

[Dima Pasechnik]

On Tue, Jan 24, 2023 at 10:15 PM John H Palmieri  wrote:
>
> For reasons I really don't understand, removing these lines from 
> sage.interfaces.all seem to have caused this:
>
> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
> -  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
> -  'mathematica', 'mwrank', 'octave', 'r', \
> -  'singular', 'sage0', 'sage']
>
> At least if I restore those lines, or even just add a line "interfaces = []", 
> then emacs appears to work again. I haven't tried it very much, though.

perhaps cause it's used in emacs_sage_shell.py ?

>
> I have absolutely no idea why this change would make a difference...
>
>
> On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de wrote:
>>
>> I tried to comment out all the changes in all_cmdline.py, but this didn't 
>> help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I 
>> don't see what could be a problem there.
>>
>> On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>>>
>>> This was one of my guesses because that ticket could have changed global 
>>> behavior of Sage by changing some imports — most of the tickets made more 
>>> focused changes. Can you start with 9.8.beta6 and just apply some of the 
>>> changes from #34547? In particular, do things work if you don't include the 
>>> changes in all_cmdline.py?
>>>
>>> --
>>> John
>>>
>>>
>>> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:

 I just spent some time to debug this, but I failed.  The problem seems to 
 be that sage-shell:wait-for-redirection-to-complete in 
 https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
  does not return.  There is only one python file involved, 
 https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
  but I do not see what #34547 has to do with it.  Something about 
 lazy_import maybe?

 I can see that in sage-shell:run-cell-raw-output the command

 _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
  ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
 ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)

 was sent to the process (using process-send-string), and after that,

 (sage-shell:wait-for-redirection-to-complete)

 never returns.  I don't know how to debug the python code, unfortunately.  
 Most importantly, I don't see what changed - what does #34547 have to do 
 with it?

 Martin



 On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>
> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
> Not sure where to go from here.  Should I open a ticket on trac?
>
> For me personally, this is a blocker, but I have no idea how many emacs 
> users there are.
>
> Martin
>
>
> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
>> hope that all dependencies are in the branch.
>>
>> Martin
>>
>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>>
>>> Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
>>> the newly merged tickets.
>>>
>>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
>>> wrote:

 From someone called mantepse in the sage-shell-mode issue on github :

 ```
 It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
 Apparently, if I first use the beta6 one for sage-shell-mode, I can 
 then use beta7 in the same emacs session.
 ```

 I don't get it either...

 There are two short Python files in the current `sahe-shell-mode` 
 emacs package, which are my prime suspects for an incompatibility with 
 Python 3.11. Now for a strategy for debugging *this*...

 Any idea ?

 Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>
> Emacs stopped working for me again!  I don't get it.
>
> This is terrible.
>
> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
> wrote:
>>
>> This patches fix my Fricas issue indeed. But losing the Emacs 
>> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>>
>> Thank you nevertheless !
>>
>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
>> écrit :
>>>
>>> In the hopes that this will fix it, I opened 

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

[Dima Pasechnik]

as the package/build system is being updated, it's hard to escape `make
distclean`

Perhaps `make sagelib-clean sagelib-uninstall` will do in this case - but
perhaps it's some other python module guilty here.


On Fri, 20 Jan 2023, 20:30 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

> What exactly did you do to "recompile sage" ?
>
> Le vendredi 20 janvier 2023 à 16:50:00 UTC+1, axio...@yahoo.de a écrit :
>
>> I'm sorry, recompiling sage fixed the emacs problem.  I have no idea what
>> happened.
>>
>> On Friday, 20 January 2023 at 12:30:23 UTC+1 axio...@yahoo.de wrote:
>>
>>> Here is the backtrace:
>>>
>>> Debugger entered--Lisp error: (quit)
>>>   accept-process-output(nil 0 1)
>>>   sage-shell:wait-for-redirection-to-complete()
>>>   sage-shell:run-cell-raw-output("_emacs_sage_shell.print_sage_root()"
>>> :sync t :process-buffer nil :output-buffer nil :to-string t :raw nil)
>>>   sage-shell:send-command-sync("_emacs_sage_shell.print_sage_root()" nil
>>> nil t nil)
>>>
>>> sage-shell:send-command-to-string("_emacs_sage_shell.print_sage_root()")
>>>   sage-shell:after-init-function(#)
>>>   #f(compiled-function () #)()
>>>   sage-shell:run-hook-once(sage-shell:output-filter-finished-hook)
>>>   sage-shell:output-filter(#
>>> "┌─...")
>>>   read-event(nil t 2)
>>>   sit-for(2)
>>>   execute-extended-command(nil "run-sage" "run-sa")
>>>   funcall-interactively(execute-extended-command nil "run-sage" "run-sa")
>>>   call-interactively(execute-extended-command nil nil)
>>>   command-execute(execute-extended-command)
>>>
>>> On Friday, 20 January 2023 at 12:26:30 UTC+1 axio...@yahoo.de wrote:
>>>
 All of a sudden, emacs sage-shell-mode seems not to work any more?  The
 last message I get is

 Checking IPython version... Done. To disable this checking, set
 ‘sage-shell:check-ipython-version-on-startup’ to ‘nil’.
 error in process filter: Quit [2 times]

 The last beta worked.

 Anyone else experiencing this?

 Martin
 On Thursday, 19 January 2023 at 00:48:25 UTC+1 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
>
> We should probably gear up for a 9.8 release soon, so get your tickets
> ready ;)
>
> 047281e0287 (trac/develop, tag: 9.8.beta7) Updated SageMath version to
> 9.8.beta7
> 272c557d1f3 Trac #31668: Run TestSuite on polynomial rings
> 6f8fb9ba3ef Trac #22067: generating function of integral points of
> polyhedra
> 5544a33b815 Trac #21003: Add package pyscipopt, add MIP backend
> b0422b2536b Trac #34838: setuptools_scm, contourpy,
> sphinxcontrib_websupport, typing_extensions: Add missing dependencies
> 30d58156a46 Trac #34717: Check the presence of lrsnash for
> obtain_nash()
> c7299453922 Trac #34891: fixing some E502 in tensor, dynamics,
> modules, plot, numerical
> bc832cb3578 Trac #34889: Installation guide: On WSL, clear /mnt/c
> stuff from PATH
> 3570a9a63bd Trac #34881: allow to remove no constraints
> 0ceb1032430 Trac #34878: MixedIntegerLinearProgram.add_constraint:
> Option to return row indices, fix handling of empty constraints
> df74efb66d2 Trac #34859: sagelib: Remove unnecessary import of
> typing_extensions
> b6a76d7a848 Trac #34857: bump giac's GIAC_MIN_VERSION to 1.9
> 6a8155e6e5d Trac #34854: molien_series() should not use GAP's
> VirtualCharacter
> dddf3ca0b08 Trac #34853: sage-env: Fix misconfiguration of pip
> 6f631021ac4 Trac #34847: modernize some for loops in cython files
> 9ffabc7f3e1 Trac #34844: removal of some unused imports about string
> conversion
> 4b50bc2af27 Trac #34843: pep8 cleanup in ore_polynomial_element.pyx
> bdd14cec19b Trac #34837: fix E502 in some pyx files
> 172ad73ae38 Trac #34836: fix E271 and E272 in rings/ and schemes/
> 3d861266040 Trac #34749: Packages dsdp, scip_sdp
> 64d232b5bfd Trac #31329: Update scipoptsuite to 8.0.2 (now open
> source!), rename to scip
> 2dcafb3ac57 Trac #34839: Support tox 4
> ad68f15d97f Trac #34648: Developer's guide: warn the transition to
> GitHub and add links to the transition guide
> acebbc1a9e8 Trac #34824: do not include parent in hash of parking
> functions
> 9a7b6310dde Trac #34818: Error when defining differentials over GCA's
> with relations.
> bb63c582122 Trac #34807: Add Construction of Hadamard matrices up to
> order 664
> 8a0b16d93be Trac #34804: Deprecate sage.interfaces is_...Element
> functions
> 80f8f950e95 Trac #34793: clean 3 files inside modular
> b0cc282500e Trac #34547: Interfaces: use more lazy imports, restore
> top-level functions maxima_console etc.
> 5905da7ebfc Trac #33915: inseparable elliptic-curve isogenies

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

[Dima Pasechnik]

is XCode up to date?

On Fri, 20 Jan 2023, 15:04 David Coudert,  wrote:

> And here is file sagely-9.8.beta7.log (zipped)
> Best,
> David.
>
> --
> 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/63E1078C-1158-40FE-8648-6F9E901FDF37%40gmail.com
> 
> .
>
> Le 20 janv. 2023 à 15:52, David Coudert  a écrit
> :
>
> Hello,
>
> I'm unable to compile on MacBook Pro M1 with macOS 12.6.1, updated
> homebrew, after distclean, using a fresh shell, and running ./bootstrap,
> source .homebrew-build-env, ./configure
> --enable-download-from-upstream-url, and make build.
>
> Help is more than welcome. I don’t know how to fix that.
>
> I have attached the install.log file (zipped).
>
> The last lines are:
> ==
> [sagelib-9.8.beta7] sage/tests/stl_vector.cpp:5426:13: warning: unused
> variable '__pyx_doc_4sage_9structure_7richcmp_8revop' [-Wunused-variable]
> [sagelib-9.8.beta7] static char
> __pyx_doc_4sage_9structure_7richcmp_8revop[] = "revop(int op) -> int\nFile:
> sage/structure/richcmp.pxd (starting at line 199)\n\nReturn the reverse
> operation of ``op``.\n\nFor example, <= becomes >=, etc.\n\n
> EXAMPLES::\n\nsage: from sage.structure.richcmp import revop\n
>   sage: [revop(i) for i in range(6)]\n[4, 5, 2, 3, 0, 1]\n";
> [sagelib-9.8.beta7] ^
> [sagelib-9.8.beta7] sage/tests/stl_vector.cpp:5707:18: warning: unused
> function '__pyx_pw_4sage_7cpython_6string_1bytes_to_str' [-Wunused-function]
> [sagelib-9.8.beta7] static PyObject
> *__pyx_pw_4sage_7cpython_6string_1bytes_to_str(PyObject *__pyx_self,
> PyObject *__pyx_args, PyObject *__pyx_kwds) {
> [sagelib-9.8.beta7]  ^
> [sagelib-9.8.beta7] sage/tests/stl_vector.cpp:5706:13: warning: unused
> variable '__pyx_doc_4sage_7cpython_6string_bytes_to_str' [-Wunused-variable]
> [sagelib-9.8.beta7] static char
> __pyx_doc_4sage_7cpython_6string_bytes_to_str[] = "bytes_to_str(b,
> encoding=None, errors=None) -> unicode\nFile: sage/cpython/string.pxd
> (starting at line 28)\n\nConvert ``bytes`` to ``str``.\n\nThis
> decodes the given ``bytes`` to a Python 3 unicode ``str`` using\nthe
> specified encoding.  It is a no-op on ``str`` input.\n\nEXAMPLES::\n\n
>   sage: from sage.cpython.string import bytes_to_str\nsage: s =
> bytes_to_str(b'\\xcf\\x80')\nsage: s == u'\317\200'\n
> True\nsage: bytes_to_str([])\nTraceback (most recent call
> last):\n...\nTypeError: expected bytes, list found\n";
> [sagelib-9.8.beta7] ^
> [sagelib-9.8.beta7] sage/tests/stl_vector.cpp:5912:18: warning: unused
> function '__pyx_pw_4sage_7cpython_6string_3str_to_bytes' [-Wunused-function]
> [sagelib-9.8.beta7] static PyObject
> *__pyx_pw_4sage_7cpython_6string_3str_to_bytes(PyObject *__pyx_self,
> PyObject *__pyx_args, PyObject *__pyx_kwds) {
> [sagelib-9.8.beta7]  ^
> [sagelib-9.8.beta7] sage/tests/stl_vector.cpp:5911:13: warning: unused
> variable '__pyx_doc_4sage_7cpython_6string_2str_to_bytes'
> [-Wunused-variable]
> [sagelib-9.8.beta7] static char
> __pyx_doc_4sage_7cpython_6string_2str_to_bytes[] = "str_to_bytes(s,
> encoding=None, errors=None) -> bytes\nFile: sage/cpython/string.pxd
> (starting at line 54)\n\nConvert ``str`` or ``unicode`` to
> ``bytes``.\n\nIt encodes the given ``str`` to a Python 3 ``bytes``\n
> using the specified encoding.  It is a no-op on ``bytes`` input.\n\n
> EXAMPLES::\n\nsage: from sage.cpython.string import str_to_bytes\n
>   sage: bs = [str_to_bytes(u'\317\200')]\nsage: all(b ==
> b'\\xcf\\x80' for b in bs)\nTrue\nsage: str_to_bytes([])\n
>   Traceback (most recent call last):\n...\nTypeError:
> expected str... list found\n";
> [sagelib-9.8.beta7] ^
> [sagelib-9.8.beta7] 19 warnings generated.
> [sagelib-9.8.beta7] INFO: g++ -std=gnu++11 -bundle -undefined
> dynamic_lookup -isysroot
> /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
> -L/Users/dcoudert/sage/local/lib -Wl,-rpath,/Users/dcoudert/sage/local/lib
> -L/Users/dcoudert/sage/local/lib -Wl,-rpath,/Users/dcoudert/sage/local/lib
> -g -O2 build/temp.macosx-12-arm64-cpython-310/sage/tests/stl_vector.o -lgmp
> -o build/lib.macosx-12-arm64-cpython-310/sage/tests/
> stl_vector.cpython-310-darwin.so -lpari
> [sagelib-9.8.beta7] ld: warning: -undefined dynamic_lookup may not
> work with chained fixups
> [sagelib-9.8.beta7] error: Command "gcc -Wno-unused-result
> -Wsign-compare -Wunreachable-code -fno-common