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

Hi John, thanks for the report; fixed in https://github.com/sagemath/sage/pull/37929 On Friday, May 3, 2024 at 9:45:20 AM UTC-7 John H Palmieri wrote: After running `make configure`, the git repository is not clean: % git status On branch develop Your branch is up to date with

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

This error is fixed in https://github.com/sagemath/sage/pull/37646 On Wednesday, March 27, 2024 at 6:57:36 PM UTC-7 John H Palmieri wrote: > And on two OS X Apple Silicon machines running Sonoma 14.4.1, new Xcode > command line tools, sagelib fails to build, as reported here: >

[sage-release] Re: Sage 10.3 released

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

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

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

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

I have a workaround for the pillow/openjpeg problem in https://github.com/sagemath/sage/pull/37505 On Wednesday, February 28, 2024 at 5:47:04 PM UTC-8 Matthias Köppe wrote: > Can confirm also on macOS x86_64 with just upgraded openjpeg. > And upgrading to pillow-10.2.0 (latest) does NO

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

Can confirm also on macOS x86_64 with just upgraded openjpeg. And upgrading to pillow-10.2.0 (latest) does NOT help. On Wednesday, February 28, 2024 at 2:22:08 PM UTC-8 John H Palmieri wrote: > The failing command: > > gcc -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common >

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

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

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

Try the updated instructions from the 10.3.beta7 installation guide: https://deploy-livedoc--sagemath.netlify.app/html/en/installation/conda#using-conda-to-provide-system-packages-for-the-sage-distribution, which uses lock files On Saturday, February 17, 2024 at 12:01:09 AM UTC-8

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

That's fixed in https://github.com/sagemath/sage/pull/36885 On Tuesday, December 19, 2023 at 12:16:11 AM UTC-8 vdelecroix wrote: > Build does not work if python-flit is not present > > [editables-0.5] ModuleNotFoundError: No module named 'flit_core' > [editables-0.5] Error building a wheel for

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

Thanks for the report. editables was missing a dependency; this is fixed in https://github.com/sagemath/sage/pull/36885 On Friday, December 15, 2023 at 4:32:56 AM UTC-8 furutaka@gmail.com wrote: > I tried to build this version on two Fedora-39 machines. > The build completed w/o any

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

On Monday, December 11, 2023 at 7:59:38 AM UTC-8 Antonio Rojas wrote: Is 'sagemath-pari' actually a thing? I can't find any other mention to it in the sage source. Not yet. https://github.com/sagemath/sage/pull/35095 adds it. -- You received this message because you are subscribed to the

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

Fixed in https://github.com/sagemath/sage/pull/36859 On Monday, December 11, 2023 at 7:59:38 AM UTC-8 Antonio Rojas wrote: > On my distro, sagelib-only build, the new file > 'src/sage/libs/pari/convert_sage_matrix.pyx' is not being cythonized or > built. This causes major breakage, with many

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

Try if https://github.com/sagemath/sage/pull/36823 helps with this On Saturday, December 9, 2023 at 8:52:54 AM UTC-8 david@gmail.com 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

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

Looking good, let's ship it! On Thursday, November 30, 2023 at 3:33:48 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 > > >

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

On Tuesday, November 21, 2023 at 2:21:57 PM UTC-8 emanuel.c...@gmail.com wrote: Le mardi 21 novembre 2023 à 17:55:09 UTC+1, matthia…@gmail.com a écrit : Try "make sage_conf-no-deps" This worked (in the sense of make -j8 claiming to have completed the upgrade). Thank you very much ! I have

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

Try "make sage_conf-no-deps" On Monday, November 20, 2023 at 9:47:14 PM UTC-8 emanuel.c...@gmail.com wrote: > Le lundi 20 novembre 2023 à 17:04:58 UTC+1, Emmanuel Charpentier a écrit : > > On Debian testing running on core i7 + 16 GB RAM, upgrading from 10.2.rc2 > to 10.2.rc4 fails ; the error

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

Which package, Dima? 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: > &

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

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

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

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

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

It's probably time to work on https://github.com/sagemath/sage/wiki/Sage-10.2-Release-Tour On Saturday, October 21, 2023 at 9:53:24 AM 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

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

On Monday, October 9, 2023 at 4:15:59 PM UTC-7 Dima Pasechnik wrote: On Tue, Oct 10, 2023 at 12:02 AM Matthias Köppe wrote: > pythran does not have any build dependencies other than setuptools. > It's pure Python, nothing needs compiling. Really? https://github.com/serge-sans-

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

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 SAG

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

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

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

The failure involving setuptools_scm is likely fixed by https://github.com/sagemath/sage/pull/36400, which is waiting for review. On Sunday, October 8, 2023 at 7:47:02 PM UTC-7 furutaka@gmail.com wrote: > A build "Using conda to provide system packages for the Sage distribution >

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

Thanks for the report. This is fixed in https://github.com/sagemath/sage/pull/36429, and before that you can work around it by using "make -k build" until everything has been built. On Sunday, October 8, 2023 at 7:43:11 PM UTC-7 furutaka@gmail.com wrote: > Hi, > > A conventional build

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

Thanks for sharing the logs for these installation problems; this is valuable information. I agree that there seems to be something wrong with the installation of setuptools in this environment. The command "conda list" could provide additional helpful information. You could try if "make

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

Thanks for the report. A fix for the ecm build failure is in https://github.com/sagemath/sage/pull/36345 (needs review) On Monday, September 25, 2023 at 12:50:45 AM UTC-7 Kenji Iohara wrote: > On MacOS 13.5.2, with updated homebrew, updated python, the first built > compilation failed owing

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

The real error is further up in the log file: INFO: gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-rpath-link,/home/eric/sage/10.2/local/lib -L/home/eric/sage/10.2/local/lib -Wl,-rpath,/home/eric/sage/10.2/local/lib -g -O2

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

After an upgrade of macOS and Xcode CLT, I also see this problem on my system. There is an open issue https://github.com/mesonbuild/meson/issues/12282 for this. On Thursday, September 21, 2023 at 4:52:56 PM UTC-7 John H Palmieri wrote: > A new problem, after upgrading to OS X 13.6 and the

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

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

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

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

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

cvxopt may be installed systemwide, but Sage does not use Python packages from the system. "make cvxopt-uninstall cvxopt" should fix the problem On Tuesday, August 1, 2023 at 12:38:04 PM UTC-7 emanuel.c...@gmail.com wrote: > Le mardi 1 août 2023 à 13:42:40 UTC+2, Dima Pasechnik a écrit : > >

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

For the "# needs" tags (and block-scoped # optional tags) to have an effect, we need #35749, of course. But I prepared #35919 and #35951 in a way that all tests of the monolithic Sage library pass. On Friday, July 21, 2023 at 1:03:29 PM UTC-7 Kwankyu Lee wrote: > #35919 and #35951 merged here

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

That's already fixed in https://github.com/sagemath/sage/pull/35749, which is why that PR is marked critical. On Tuesday, July 18, 2023 at 3:30:21 PM UTC-7 Volker Braun wrote: > I just found out that > > sage -t --long --random-seed=0 > src/sage/schemes/elliptic_curves/heegner.py > >

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

Earlier error: [sagelib-10.1.beta4] /usr/bin/ld : ne peut pas trouver -larb : Aucun fichier ou dossier de ce type Try if "make sage_conf-no-deps build" fixes the problem On Thursday, June 22, 2023 at 3:26:07 AM UTC-7 emanuel.c...@gmail.com wrote: > Log enclosed > > > On Thu, Jun 22, 2023

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

Making pytest a standard package is https://github.com/sagemath/sage/issues/31110 On Sunday, June 4, 2023 at 1:21:19 AM UTC-7 tdumont wrote: > When upgrading from 10.0 to 10.1 (Debian testing, up to date): > > * compilation ok. > * make ptestlong, I got : > pytest is not installed in the venv,

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

Probably introduced in #35619 On Sunday, May 28, 2023 at 5:06:10 PM UTC-7 John H Palmieri wrote: > stdin.info is not in the tarball, but rather produced by `./configure`. > My best guess it that it's created somewhere in the check for the SPKG > "info". > > On Sunday, May 28, 2023 at 3:16:49 

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

Same with debian-bookworm for 10.1.beta0 (https://github.com/sagemath/sage/actions/runs/5051084836/jobs/9066916642#step:10:883) On Tuesday, May 23, 2023 at 1:11:50 PM UTC-7 Matthias Köppe wrote: > On Monday, May 22, 2023 at 11:39:09 PM UTC-7 tdumont wrote: > > > On debian tes

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

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

Re: [sage-release] Sage 10.0 released

is Bissey wrote: > >> >> >> On 22/05/23 06:14, Matthias Köppe wrote: >> > On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote: >> > >> > I am preparing the sage-on-gentoo release. I just noticed the file >> > sage/graphs/bli

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

On Sunday, May 21, 2023 at 1:18:09 PM UTC-7 Dima Pasechnik wrote: 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. &

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

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

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

On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote: 2023-05-21 01:00 UTC, Matthias Köppe: > > I have created a changelog at > https://github.com/sagemath/sage/releases/tag/10.0 > (automatically generated from the merged PRs by GitHub; > then lightly edited). T

Re: [sage-release] Sage 10.0 released

On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote: I am preparing the sage-on-gentoo release. I just noticed the file sage/graphs/bliss.pyx is missing from the pypi tarball of sagemath-standard. I have a feeling I will find it in the sage-bliss package. However I did not

[sage-release] Re: Sage 10.0 released

Thanks for preparing the release! I have created a changelog at https://github.com/sagemath/sage/releases/tag/10.0 (automatically generated from the merged PRs by GitHub; then lightly edited). Some notes: - The list of "New Contributors" was also automatically generated by GitHub. It did not

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

Note that what's left in the 10.0 milestone is already hand-picked. https://github.com/sagemath/sage/milestone/152 In particular, could you please merge https://github.com/sagemath/sage/pull/35460 (the update to our developer's guide for GitHub -- didn't you say the transition to GitHub is

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

Thanks for the new rc. Tests ran at https://github.com/sagemath/sage/actions/runs/4962805314 All "standard" configurations on the tested Linux platform look OK - except: - ubuntu-kinetic-standard (https://github.com/sagemath/sage/actions/runs/4962805314/jobs/8884806221): Segmentation faults in

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

There is a number of important PRs for platform support (including conda) that I recommend to merge. See https://github.com/sagemath/sage/milestone/152 On Sunday, May 7, 2023 at 5:02:30 AM UTC-7 Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git >

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

Thanks for the new rc. According to the platforms tests at https://github.com/sagemath/sage/actions/runs/4834936696: - build on *archlinux* fails. This is fixed by https://github.com/sagemath/sage/pull/35524 (needs review). - on *fedora-38-minimal*, *archlinux-minimal*,

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

These warnings will be fixed by https://github.com/sagemath/sage/pull/35570, needs review On Monday, April 24, 2023 at 10:57:55 PM UTC-7 jonatha...@googlemail.com wrote: > Hi, > > almost everything works installed from scratch with recommended system > packages on manjaro. > > I get some

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

This is fixed in https://github.com/sagemath/sage/pull/35477, waiting for review On Monday, April 24, 2023 at 2:22:21 AM UTC-7 furutaka@gmail.com wrote: > With the same OS (Fedora-38), failed to build libgd-2.3.2 (with freetype > in sage). > The log attached. > > Kazuyoshi > > >

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

Thanks for reporting this. I've opened https://github.com/sagemath/sage/issues/35557 for it. On Sunday, April 23, 2023 at 10:33:54 PM UTC-7 Clemens Heuberger wrote: > On two Linux Mint 20.3 machines, I got doctest errors which I have not > seen > before in the previous betas, see below. > >

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

Thanks for preparing the rc. I'll note that a number of important PRs for platform support are waiting for review, and a few critical issues without PR are open: givaro, zeromq: Add patches for GCC 13 support sage.libs.eclib.homspace fails to build

[sage-release] Re: Sage 10.0 Release Tour

So far we have: Sage 10.0 Release Tour - Documentation - Graphics

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

The matrix failures come from the homebrew openblas update. See https://github.com/sagemath/sage/pull/35377 On Tuesday, March 28, 2023 at 5:52:45 PM UTC-7 list...@gmail.com wrote: > > FWIW, this is on Apple Silicon Macs ("M" series) with Homebrew up to date > (make and make pytest and make

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

Could you provide the output of "ls -l /usr/local/opt/openblas/lib/pkgconfig/openblas.pc local/lib/pkgconfig/*.pc" please, and also the file

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

Please post config.log On Sunday, March 26, 2023 at 2:49:42 PM UTC-7 Kenji Iohara wrote: > Hello, > > On my Mac Book Pro with Intel Core i5, OS 13.2.1 and updated homebrew, > It didn’t compile from the first built owing to the error : > > package: scipy-1.10.1 > > last build time:

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

Thanks, Volker. I have closed the corresponding GitHub issues. On Sunday, February 12, 2023 at 3:54:51 PM UTC-8 Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at >

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

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

[sage-release] Re: Sage 9.8 released

>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

Re: [sage-release] Sage 9.8 released

The sdists are now up on PyPI. On Saturday, February 11, 2023 at 2:43:59 PM UTC-8 Matthias Köppe wrote: > I've created a new PyPI deployment token and made it available to our > repos. > I've started https://github.com/sagemath/sage/actions/workflows/dist.yml > manually. >

Re: [sage-release] Sage 9.8 released

I've created a new PyPI deployment token and made it available to our repos. I've started https://github.com/sagemath/sage/actions/workflows/dist.yml manually. On Saturday, February 11, 2023 at 2:33:12 PM UTC-8 Dima Pasechnik wrote: > On Sat, Feb 11, 2023 at 10:31 PM Matthias Köppe >

Re: [sage-release] Sage 9.8 released

Neither the "dist.yml" nor the "ci-..." workflows have run on the push to the 9.8 tag on sagemath/sage. I'll investigate. 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-release] Re: Sage 9.8 Release Tour

I've added a bit on the GitHub migration to the release tour: https://github.com/sagemath/sage/wiki/Sage-9.8-Release-Tour#sage-development-has-moved-from-trac-to-github On Friday, February 10, 2023 at 1:11:18 AM UTC-8 Kwankyu Lee wrote: > The release tour for the upcoming 9.8 release is now

[sage-release] Re: Sage 9.8 Release Tour

The link to it from https://wiki.sagemath.org/ReleaseTours will have to be adjusted after the renames. On Friday, February 10, 2023 at 1:11:18 AM UTC-8 Kwankyu Lee wrote: > The release tour for the upcoming 9.8 release is now found at > >

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

I've fast-forwarded develop to 9.8.rc1 on https://github.com/sagemath/sage On Sunday, February 5, 2023 at 9:21:45 AM UTC-8 Volker Braun wrote: > tag is pushed! > > On Sunday, February 5, 2023 at 5:58:59 PM UTC+1 matthia...@gmail.com > wrote: > >> Thanks for the new rc. It's currently not tagged

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

Thanks for the new rc. It's currently not tagged on vbraun/sage though; could you push the tag please? On Sunday, February 5, 2023 at 6:14:57 AM UTC-8 Volker Braun wrote: > Note: the old trac git server is already disabled and the new > https://github.com/sagemath/sage is still locked for

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

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? What does "which m4" say? -- You received this message because you are subscribed to the Google Groups

[sage-release] Re: Sage 9.8 Release Tour

So far we have: 1. 1. Linear algebra 1. Submodules of tensor modules with prescribed symmetries

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

>From looking at that file: https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py#L159 In 9.8.beta7: sage: isinstance(axiom, sage.interfaces.expect.Expect) False On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote: > I just spent some time to debug

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

./configure --without-system-nauty On Monday, January 23, 2023 at 4:30:05 PM UTC-8 tsc...@ucdavis.edu wrote: > Would it be better to just remove nauty or is there a way to force Sage to > build and link with its own copy of nauty? > > Thanks, > Travis > > > On Monday, January 23, 2023 at

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

./configure --without-system-libnauty On Monday, January 23, 2023 at 4:30:05 PM UTC-8 tsc...@ucdavis.edu wrote: > Would it be better to just remove nauty or is there a way to force Sage to > build and link with its own copy of nauty? > > Thanks, > Travis > > > On Monday, January 23, 2023 at

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

I've opened https://trac.sagemath.org/ticket/34932 for this On Monday, January 23, 2023 at 1:51:45 AM UTC-8 François Bissey wrote: > It is indeed a known issue with nauty on debian/ubuntu. That's the first > time someone mentioned it in a while but it is definitely broken. > > On 23/01/23

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

Yes, Python 3.11 is not yet supported. https://trac.sagemath.org/ticket/33842 adds support for it and is waiting for review. On Tuesday, November 29, 2022 at 11:07:18 PM UTC-8 Kenji Iohara wrote: > Is Python3.11 on Mac OS too new too build Sage 9.8.beta4 ? > This seems to be related to some

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

https://trac.sagemath.org/ticket/21003 (PySCIPopt) adds a much better MILP solver, which has the potential for replacing GLPK as our standard solver. On Monday, November 28, 2022 at 12:19:04 PM UTC-8 david@gmail.com wrote: > This is again the MILP formulation of

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

If you're testing https://trac.sagemath.org/ticket/34658, you'll need "./configure --enable-download-from-upstream-url". On Tuesday, November 22, 2022 at 7:36:28 PM UTC-8 Kenji Iohara wrote: > With my Mac OS 13.0.1, with Intel Core i5, and several packages with > Homebrew, I have a problem

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

I think this will be fixed by the meson-python upgrade in https://trac.sagemath.org/ticket/34658, please test On Tuesday, November 22, 2022 at 10:34:52 AM UTC-8 John H Palmieri wrote: > scipy fails to build for me (OS X 13.0.1, Intel, with various homebrew > packages, Sage built from a new

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

See https://trac.sagemath.org/wiki/ReleaseTours/sage-9.7#AvailabilityofSage9.7andinstallationhelp "known issues and workarounds" On Sunday, October 2, 2022 at 1:03:58 PM UTC-7 Kenji Iohara wrote: > With Pari 2.15, on MacBookPro, I even couldn't recompile Sage 9.7. .. > Kenji > >

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

On Friday, September 30, 2022 at 4:15:55 AM UTC-7 emanuel.c...@gmail.com wrote: > DeprecationWarning: implementations of Modules().TensorProducts() now > must define the method tensor_factors > See https://trac.sagemath.org/34393 for details.The ticket pointed to by > the error message

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

Thanks for the new beta! Developers should be aware of the tightened compiler requirements: https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8#Configurationchanges On Sunday, September 25, 2022 at 1:47:59 PM UTC-7 Volker Braun wrote: > As always, you can get the latest beta version from the

[sage-release] Re: Sage 9.7 released

Awesome! On Monday, September 19, 2022 at 3:53:04 PM UTC-7 Volker Braun wrote: > The "master" git branch has been updated to Sage-9.7. As always, you can > get the latest beta version from the "develop" git branch. Alternatively, > the self-contained source tarball is at >

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

On Tuesday, August 30, 2022 at 6:15:10 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 > > cae9ee5177a (HEAD -> develop, tag:

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

I've opened https://trac.sagemath.org/ticket/34268 (Reduce R to a dummy package, upgrade rpy2 to 3.4.5) On Tuesday, August 2, 2022 at 11:34:22 AM UTC-7 Matthias Köppe wrote: > Yes, our R package is wildly outdated, which is problematic given that it > is a standard package. > > &g

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

Rf_match > ``` > > On Tue, Aug 2, 2022 at 1:06 PM Matthias Köppe > wrote: > >> On Tuesday, August 2, 2022 at 10:51:04 AM UTC-7 isu...@gmail.com wrote: >> >>> We build conda packages regularly with non-Xcode clang on macOS. >>> >>

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

On Tuesday, August 2, 2022 at 10:51:04 AM UTC-7 isu...@gmail.com wrote: > We build conda packages regularly with non-Xcode clang on macOS. > Yes, we do also test the Sage distribution build on conda-forge-macos, which uses clang. conda-forge-macos-standard succeeds, using lots of conda

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

I've added the sentence "An alternative is to use a sufficiently recent version of clang (LLVM)." But having more details would be better. On Tuesday, August 2, 2022 at 10:46:32 AM UTC-7 Dima Pasechnik wrote: > > > On Tue, 2 Aug 2022, 18:33 Matthias Köppe, wrote: > &

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

Pasechnik wrote: > > > On Tue, 2 Aug 2022, 18:33 Matthias Köppe, wrote: > >> On Tuesday, August 2, 2022 at 10:24:39 AM UTC-7 Dima Pasechnik wrote: >> >>> >>> there is a bit of vagueness there: >>> Support for system GCC older than 6.3 dropped

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

On Tuesday, August 2, 2022 at 10:24:39 AM UTC-7 Dima Pasechnik wrote: > > there is a bit of vagueness there: > Support for system GCC older than 6.3 dropped ¶ > > > Building Sage from source now

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

On Tuesday, August 2, 2022 at 10:13:05 AM UTC-7 david@gmail.com wrote: > With this new beta, I see that the source code and the compiled code are > mixed. > For instance > sapristi:sage dcoudert$ ll src/sage/graphs/ > total 76264 > drwxr-xr-x 123 dcoudert coati 3936 2 aoû 16:10 . >

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

I've opened https://trac.sagemath.org/ticket/34181 for this. On Thursday, July 14, 2022 at 7:36:15 AM UTC-7 Matthias Köppe wrote: > On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > >> When I did an incremental build with the venv-python3.10.3 in place, a

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

On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > If I delete all of the venvs before starting an incremental build will the > build still work, and will it create a new venv that is appropriate for its > python, even if the python version has not changed? > Yes. --

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

On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > When I did an incremental build with the venv-python3.10.3 in place, a new > venv named python3.10.5 was created. But that new venv depends on the old > 3.10.3 venv. In fact, there are at least 16 executable files in

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

Yes, you can delete the old venv. We do not uninstall other venvs that may have been built previously. On Wednesday, July 13, 2022 at 1:08:57 PM UTC-7 marc@gmail.com wrote: > After working around the issues with the bootstrap script and symengine_py > I have managed to build 9.7.beta5 on

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

On Monday, July 11, 2022 at 8:11:38 AM UTC-7 Dima Pasechnik wrote: > that's a bug in ./bootstrap then. > Yes, see https://trac.sagemath.org/ticket/34152 for a proposed fix -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from

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

Yes, we also see this in the CI for optional packages - https://github.com/sagemath/sage/actions/runs/2632874850 This is fallout from upgrading setuptools in https://trac.sagemath.org/ticket/33866 Looks like this is already fixed in upstream symengine.py. I've opened

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

On Thursday, June 16, 2022 at 5:56:46 AM UTC-7 egourg...@gmail.com wrote: > this is the first version of Sage that refuses to use the system Python, > which is 3.8.10. Although only Python 3.7 is officially dropped by this > version, configure says: > > checking for python3 >= 3.8.0, < 3.11.0

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

On Sunday, June 12, 2022 at 6:16:00 AM UTC-7 Volker Braun wrote: > a6e696e91d (tag: 9.7.beta2, trac/develop) Updated SageMath version to > 9.7.beta2 > [...] > fa1477350a Trac #32937: Drop Python 3.7 support in Sage 9.7 > Python 3.8 language and library features can now be used in the Sage

Re: [sage-release] Final 9.6 upgrade is catastrophic on Debian testing

We automatically test on debian-bookworm ("testing") on GH Actions. Here's the run for the 9.6 release tag: https://github.com/sagemath/sage/runs/6443847112 (all good). On Tuesday, May 17, 2022 at 10:56:12 AM UTC-7 maxime...@inria.fr wrote: > On 5/16/22 23:56, Emmanuel Charpentier wrote: > >

Re: [sage-release] Sage 9.6 released

On Monday, May 16, 2022 at 11:05:28 PM UTC-7 François Bissey wrote: > How long until we have stuff on pypi? That’s when I will pick up the work > in sage-on-gentoo in the current framework. > It's all in place. It's pushed automatically on each release tag on GH Actions. -

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

c/cocalc-docker > > -- William > > > On Sun, May 15, 2022 at 3:33 PM Matthias Köppe > wrote: > > > > Yay! Thanks a lot, Volker. > > > > On Sunday, May 15, 2022 at 3:27:40 PM UTC-7 Volker Braun wrote: > >> > >> The "master

  1   2   3   4   >