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

:41:24 UTC+2, Emmanuel Charpentier a écrit : > On Ubuntu 24.04running under WSL2/Windows11 on core i7 = 32 GB rAM; > upgrading 10.5.beta3 to 10.5.beta4 and running ptestlong gives two > transient failures : > sage -t --long --warn-long 92.0 >

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

On Ubuntu 24.04running under WSL2/Windows11 on core i7 = 32 GB rAM; upgrading 10.5.beta3 to 10.5.beta4 and running ptestlong gives two transient failures : sage -t --long --warn-long 92.0 --random-seed=215891992822319941402876332559304583711 src/sage/plot/animate.py # 1 doctest failed sage -t

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

Same result on Ubuntu 24.04 runnong under WSL2/Windows 11 on core i7 + 32 GB RAM. HTH, Le samedi 27 juillet 2024 à 08:43:49 UTC+2, Emmanuel Charpentier a écrit : > On Debian testing running on core i7 + 16 GB, upgrading 10.4 to 10.5?beta0 > needed rebuilding the documentation ; pte

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

On Debian testing running on core i7 + 16 GB, upgrading 10.4 to 10.5?beta0 needed rebuilding the documentation ; ptestlong reports the same cosmetic failure on Fricas as the previous versions. HTH, ​ Le jeudi 25 juillet 2024 à 00:35:43 UTC+2, Volker Braun a écrit : > As always, you can get th

[sage-release] Re: Sage 10.4 released

Identical result, modulo the transient failure, on Ubuntu 24.04 running under WSL2/Windows 11 on core i7 + 32 GB RAM. HTH, Le samedi 20 juillet 2024 à 16:54:43 UTC+2, Emmanuel Charpentier a écrit : > On Debian testing running on core i7, I get the same permanent failure > (already re

[sage-release] Re: Sage 10.4 released

On Debian testing running on core i7, I get the same permanent failure (already reported for about 5 betas (fricas(R(pi)) gets a deprecatuin warning interpreted as an error), and a transient failure (timeout and interrupt failure in src/sage/libs/flint/nmod_poly_linkage.pxi, which passes when

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

On Ubuntu 24.04 running under WSL2/Windows 11, ptestlong still gives the same single permanent failure as before. HTH, ​ Le mercredi 17 juillet 2024 à 01:01:32 UTC+2, Volker Braun a écrit : > As always, you can get the l

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

Same reult in Debian testing running on core i7 + 16 GB RAM HTH, Le mardi 16 juillet 2024 à 10:16:15 UTC+2, Emmanuel Charpentier a écrit : > On Ubuntu 24-04 running under WSL2/Windows 11 on core i7 + 32 GB RAM, > upgrading to 10.4.rc3 and running ptestlong gives one single permanent >

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

On Ubuntu 24-04 running under WSL2/Windows 11 on core i7 + 32 GB RAM, upgrading to 10.4.rc3 and running ptestlong gives one single permanent failure already reported . HTH, ​ Le samedi 13 juillet 2024 à 10:51:30 UTC+2, Vol

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

Identical result (same unique permanent failure) for 10.4.rc2 in Ubuntu 24.04 running under WSL2/Windows 11 on core i7 + 32 GB RAM. HTH, Le mercredi 10 juillet 2024 à 14:34:09 UTC+2, Emmanuel Charpentier a écrit : > FWIW, after some recent update of Debian testing, I had to upgrade, si

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

FWIW, after some recent update of Debian testing, I had to upgrade, since the sage command started to fail with a message amounting to Python being unable to find the sage module, IIRC. On Debian testing running on core i7 + 16 GB RAM, a “normal” upgrade (fetch from upstream; bootstrap, make

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

On Ununtu 24.04 running under WSL 2/Windows 11 on core i7 + 32 GB RAM, upgrading 10.4.beta9 to 10.4.rc1 and running ptestlong gives two transient failures (tests pass when ran standalone) : -- sage -t --long --warn-long 89.0

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.4.beta9 to 10.4.rc0 and running ptestlong gives one perlanent failure : -- sage -t --long --warn-long 240.4 --random-seed=323704012932463514602012395260168321916

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

-- sage -t --long --warn-long 86.5 --random-seed=243166338554774216379729945104943256431 src/sage/rings/real_mpfr.pyx # 1 doctest failed -- Total time for a

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

On Debian testing running on core i7 + 16 GB Ram, opgrading 10.4.beta8 to 10.4.beta9 andrunning ptestlong returns one permanent failure : -- sage -t --long --warn-long 237.5 --random-seed=77490887220742187450748251931007409634

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

On Debian testing running on core i7 + 16 GB RAM, upgrading10.4.beta7 to 10.4.beta8 and rinning ptestlong gives one permanent failure (already reported for a couple of previous betas) : -- sage -t --long --warn-long 253.4 --r

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

Le dimanche 2 juin 2024 à 21:48:18 UTC+2, Emmanuel Charpentier a écrit : Le dimanche 2 juin 2024 à 12:16:52 UTC+2, furutaka….@gmail.com a écrit : Fedora 40, x86_64. Build OK, without any problems. Not specific to this particular beta release, but it seems there're no packages named ta

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

Le dimanche 2 juin 2024 à 12:16:52 UTC+2, furutaka….@gmail.com a écrit : Fedora 40, x86_64. Build OK, without any problems. Not specific to this particular beta release, but it seems there're no packages named tachyon{,-devel}: `Error: Unable to find a match: tachyon tachyon-devel` In Debian

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

397818908026740447949112662303559 src/sage/plot/animate.py # 1 doctest failed ------ Total time for all tests: 64.2 seconds cpu time: 36.6 seconds cumulative wall time: 63.6 seconds Features detected for doctes

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 9.4.beta6 to 9.4.beta7 and running ptestlong gives two permanent failures : -- sage -t --long --warn-long 238.3 --random-seed=287407045809936856009614328219870119801

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

On Debian testing (updated daily) running on core i7 + 16 GB RAM, upgrading 10.4.beta5 to 10.4.beta6 and running ptestlong gives one permanent failure : -- sage -t --long --warn-long 241.4 --random-seed=13762535939771961672143

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

On Debian testing running on core i7n + 16 GB RAM, upgrading 10.4.beta4 to 10.4.beta5 and running ptestlong gives one permanent failure : -- sage -t --long --warn-long 237.3 --random-seed=20991438179762496164662365457806748009

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

On Debian testing running on core i7 + 16 GB RAM, upgrading from 10.4.beta2 to 10.4.beta4 and running ptestlong gives one permanent failure : ``` -- sage -t --long --warn-long 218.4 --random-seed=17561197619656807254209499413420

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

On Ubuntu 24.04 (upgraded from 22.04) running under WSL2 on Windows 11, a few things may worth mention :     - The upgrade entailed a new version of `gcc`, which entailed failures with system's `brial` (as already reported). Reconfiguration excluding system's `brial` and forced installation of Sag

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

FWIW, upgrading 10.4.beta1 to 10.4.beta2 and running ptestlong succeedes without any failure on both Debian testing and Ubuntu 22.04 LTS running under WSL2 on Windows 11. HTH, Le mardi 9 avril 2024 à 01:19:53 UTC+2, Volker Braun a écrit : > As always, you can get the latest beta version from t

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

Same results in Ubuntu 22.04LTS running under WSL2 on Windows 11 (long story...). HTH, Le mercredi 3 avril 2024 à 11:58:40 UTC+2, Emmanuel Charpentier a écrit : > On Debian testing, uograding directly from 10.3 to 10.4.beta1 went > uneventfully ; running ptestlong didn't trigger

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

On Debian testing, uograding directly from 10.3 to 10.4.beta1 went uneventfully ; running ptestlong didn't trigger any failure whatsoever. HTH, Le lundi 1 avril 2024 à 01:20:13 UTC+2, Volker Braun a écrit : > As always, you can get the latest beta version from the "develop" git > branch. Alter

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

FWIW, Debian's security has reverted to 5.4.1 on Mar 28. Many thanks for the lookup ! Le vendredi 29 mars 2024 à 20:18:20 UTC+1, Dima Pasechnik a écrit : > 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 h

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

` when re-running `ptestlong`. However, souldn't this dependency be tested by `./configure` ? 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

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

On debian testing running on core i7 + 16 GB RAM, upgrading from 10.3.beta1 to 10.3.beta3 works without any problem. Running ptestlong gives nine *transient* failures : -- sage -t --long --warn-long 233.7 --random-seed=569683

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

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

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

Your suggestion was efficient : forcing Sage’s brial installation by sage -i brial (thus avoiding Debian’s brial) allowed these tests to pass. Thanks a lot ! ​ Le jeudi 15 février 2024 à 19:34:45 UTC+1, Antonio Rojas a écrit : > El jueves, 15 de febrero de 2024 a las 17:36:35 UTC+1, > emanuel

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.beta8 to 10.3.rc0 initially failed ; deleting and rebuilding the documentation succeeded. Running ptestlong initially raised the seven polybori-related failures already reported

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

? (10.3b8) singular_jupyter0.9.7 (0.9.7) stanio..? (0.3.0) tqdm? (4.66.2) ptestlong still fails the seven polybori tests already reported. I”m stuck… HTH, ​ Le jeudi 15 février 2024 à 10:3

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

On Deblan testing running on core i7 + 16 GB RAM, the 7 tests relative to polybori still fail the same way : chash, with gdb indicating ! [Inferior 1 (process 120886) detached] 30 ../sysdeps/unix/sysv/linux/wait4.c: Aucun

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.beta5 succeeds ; running `ptestlong` results in 8 nw permanent failures : ``` -- sage -t --long --warn-long 225.3 --random-seed=14330382712856266914913764249554711

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

FWIW, on Debian testing running on core i7 + 16 GB RAM, upgrading 10.3.beta3 to 10.3.beta4 and running ptestlong passes without any failure. HTH, ​ Le mardi 26 décembre 2023 à 13:47:17 UTC+1, Volker Braun a écrit : > As always, you can get the latest beta version from the "develop" git > bran

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

On Debian testing, upgraing 10.3.beta2 to 10.3.beta3 and running ptestlong passes without any failure. HTH, Le mardi 19 décembre 2023 à 01:23:15 UTC+1, Volker Braun a écrit : > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained sou

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

On Debian testing running on, core i7 + 16 GB RAM, upgrading 10.3.beta1 to 10.3.beta2 and running ptestlong passes without any failure. HTH, ​ Le jeudi 14 décembre 2023 à 01:42:36 UTC+1, Volker Braun a écrit : > As always, you can get the latest beta version from the "develop" git > branch. A

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

Forcing the reinstallation of cvxopt (sage -f cvxopt ; make -j8) allowed all the failed tests to pass without failure. I still do not have any explanation for the initial cvxopt failure… HTH, ​ Le mercredi 13 décembre 2023 à 18:43:27 UTC+1, Emmanuel Charpentier a écrit : > Missing text

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

doctests failed -- ``` All seem to be related to a missing cvxopt library (logs and config enclosed). Any hint welcome ! Le mercredi 13 décembre 2023 à 18:39:00 UTC+1, Emmanuel Charpentier a écrit : > -- You received t

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

UTC+1, Emmanuel Charpentier a écrit : > 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

Thank you ! Le mardi 21 novembre 2023 à 23:46:30 UTC+1, matthia...@gmail.com a écrit : > 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

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

er’s guide (as published for 10.1). Care to give some explanation ? make -j8 ptestlong underway… 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 +

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

; 1372 cdef cl_object o -> 1373 o=ecl_safe_eval(python_to_ecl(s, True)) 1374 return ecl_wrap(o) 1375 File /usr/local/sage-10/src/sage/libs/ecl.pyx:321, in sage.libs.ecl.ecl_safe_eval() 319 raise KeyboardInterrupt("ECL says: {}".format(message)) 320 else: --> 321 raise RuntimeError("

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

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 seems to be triggered by the documentation of 3D plots. Log enclosed. I'm still stuck. Suggestions ? --

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

On Debian testing running on core i7 + 16 GB RAM, same single permanent failure (`src/sage/functions/special.py`) than before. And the behaviour of `view()` is fixed. HTH, Le dimanche 12 novembre 2023 à 22:42:41 UTC+1, Volker Braun a écrit : > As always, you can get the latest beta version fro

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

FWIW, on Debian testing r GB RAM, upgading 10.2.beta9 to 10.2.rc1 and running ptestlong results in one permanent failure : sage -t --long --warn-long 291.5 --random-seed=166120603893570771975522737524674489931 src/sage/functions/special.py # 2 doctests failed And, BTW, using view() from a co

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

ex.py: replace tmp_dir() > > A case of a review “a bit hasty” ? > > Do you need a new ticket ? > > HTH, > ​ > Le dimanche 22 octobre 2023 à 22:27:18 UTC+2, Emmanuel Charpentier a > écrit : > >> On Debian testing running on core i7 + 16 GB RAM, upgrading 10.7.be

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

Opened [a new issue](https://github.com/sagemath/sage/issues/36526). HTH, Le lundi 23 octobre 2023 à 17:31:48 UTC+2, Emmanuel Charpentier a écrit : > Uh, oh. > > This one is new : view((1/(1+e^(-a*x+b))).diff(x)) doesn’t display > anything, with an error displayed in the PDF vi

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

er ou répertoire de ce type In the update list for this beta : 4a60001a052 gh-36436: src/sage/misc/latex.py: replace tmp_dir() A case of a review “a bit hasty” ? Do you need a new ticket ? HTH, ​ Le dimanche 22 octobre 2023 à 22:27:18 UTC+2, Emmanuel Charpentier a écrit : > On Debian testing

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

n fichier ou répertoire de ce type ``` In the update list for this beta : ``` 4a60001a052 gh-36436: src/sage/misc/latex.py: replace tmp_dir() ``` A case of a review "a bit hasty" ? Do you need a new ticket ? HTH, Le dimanche 22 octobre 2023 à 22:27:18 UTC+2, Emmanuel Charpentier a

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.7.beta7 to 10.2.beta8 and running ptestlong gives the same permanent failures already reported for a few betas : -- sage -t --long --warn-long 219.0 --random-seed

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.7.beta7 to 10.2.beta8 and running `ptestlong` gives the same Le samedi 21 octobre 2023 à 18:53:24 UTC+2, Volker Braun a écrit : > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the se

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

failed both having been already reported for a few previous betas. HTH, ​ Le mardi 17 octobre 2023 à 08:38:25 UTC+2, Emmanuel Charpentier a écrit : > ``` > make sagelib-clean sagelib-uninstall > make cython-clean cython-uninstall > git pull upstream pull/36332/head > make cyth

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

ter.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+

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

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

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

ctobre 2023 à 22:38:52 UTC+2, Emmanuel Charpentier a écrit : > 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: > > &g

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

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

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

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

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

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

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

tories, 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]:

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

Nope... `make cython` succeeds. Bit `make build fails : ``` [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

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta6 to 10.2.beta7 fails with fthe following last lines of test.log : [ 50626 lines omitted… ] [sagelib-10.2.beta7] [287/293] Cythonizing sage/rings/real_mpfr.pyx [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: [sage

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

sage -t --long --warn-long 214.7 --random-seed=243887514724930233678848752823063984447 src/sage/functions/special.py # 2 doctests failed ------ Already seen. I still do not understand it. H

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

Seems to have worked.Now compiling... Le lundi 9 octobre 2023 à 23:44:30 UTC+2, Dima Pasechnik a écrit : > 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 : > &g

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

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

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

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

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

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,

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

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

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

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

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

manuel Charpentier a écrit : > On Debian testing running oncore i7 + 16 GB RAM, upgrading 10.2.beta4 to > 10.2.beta5 *fails* ; the problems seem to be bound to Cython. > > Log follows in a followup mail (can’t be atached in a Google Groups mail…). > > — > Emmanuel Charpentier > ​

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

On Debian testing running oncore i7 + 16 GB RAM, upgrading 10.2.beta4 to 10.2.beta5 *fails* ; the problems seem to be bound to Cython. Log follows in a followup mail (can’t be atached in a Google Groups mail…). — Emmanuel Charpentier ​ Le jeudi 28 septembre 2023 à 00:56:29 UTC+2, Volker Braun

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

FWIW, upgradong 10.2.beta3 to 10.2.beta4 and running ptestlong gives me the two permanent failures already reported for a couple of previous betas : sage -t --long --warn-long 218.5 --random-seed=16428889549013772006977694375024902563 src/sage/combinat/posets/posets.py # 1 doctest failed sage

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

FWW, on Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta2 to 10.2.beta3 went smoothly (without having to mess with meson) ; ptestlong gives two permanent failures : -- sage -t --long --warn-long 217.3 --rand

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta1 to 10.2.beta2 and running ptestlong gives two permanent failures : -- sage -t --long --warn-long 215.1 --random-seed=11366728099969244340071199215411689548

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

On Debian testing, : - Upgrading 10.2.beta0 to beta0 to 10.2.beta1 fails by *repeatedly* failing to create one 3D plot in the documentation (lost exact reference, sorry…) ; rebuilding all documatation fails also. - After make distclean, I had to specify --with-sysem

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

On Debian testing running on core i7 + 16 GB RAM, upgarong 10.1.rc0 to 10.2.beta0 gives three new persistent failures : charpent@zen-book-flip:/usr/local/sage-10$ sage -t --long --warn-long 216.1 --random-seed=336915508420415526544989948662812522502 src/sage/rings/integer.pyx # 1 doctest faile

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

Le lundi 14 août 2023 à 18:10:32 UTC+2, Emmanuel Charpentier a écrit : [ Snip… ] `ptestlong` underway... -- sage -t --long --warn-long 198.3 --random-seed=206512876243836917842474214856246458168 src/sage/algebras

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

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 inc

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

./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?=(aucun

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

On debian testing running on core i7+ 16 GB RAM, upgrading 10.1.beta7 to 10.1.beta8 and rinning ptestlong gives : sage -t --long --warn-long 223.1 --random-seed=151297934955640179888039541819674259295 src/sage/coding/linear_code.py # 2 doctests failed Cosmetic, already reported. charpent@zen

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

[ Snip... ] Now running the whole ptestlong suite again. Stay tuned ! No other failures in the full `ptestlong`. -- 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

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

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_geometr

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

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 M

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

Le mardi 1 août 2023 à 13:42:40 UTC+2, Dima Pasechnik a écrit : 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 fa

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

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 d

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

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.1.beta6 to 10.1.beta7 and ruunning ptestlong gives one new permanent failure : -- sage -t --long --warn-long 212.6 --random-seed=1946128050711283528023160916127626

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

On Debian testing running on core i7 + 16 GB RAM, upgrading from 10.1.beta5 failed, due to a (series of) errors during the building of the documentation for plots : ECL complained to be unable to find Maxima. Removing the documentation and rebuilding it was ineffective. What was efficient was

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

On Debian testing running on core I7 + 16 GB RAM, upgrading 10.1.beta4 to 10.1.beta5 and running ptestlong gives one *transient* failure : -- sage -t --long --warn-long 221.1 --random-seed=1303775157646206312340990154089190106

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

Passes without any failure. Thanks ! HTH, Le vendredi 23 juin 2023 à 13:50:05 UTC+2, Emmanuel Charpentier a écrit : > sed -e s/younge/older/, of course. Silly me… > ​ > Le vendredi 23 juin 2023 à 13:42:30 UTC+2, Emmanuel Charpentier a écrit : > >> ./configure --with-system-ar

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

sed -e s/younge/older/, of course. Silly me… ​ Le vendredi 23 juin 2023 à 13:42:30 UTC+2, Emmanuel Charpentier a écrit : > ./configure --with-system-arb=no was enough to be able to build > successfully. > > I note that the build process downloaded and installed arb-2.22.1, >

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

? Running ptestlong now. HTH, ​ Le jeudi 22 juin 2023 à 19:38:30 UTC+2, Emmanuel Charpentier a écrit : > Le jeudi 22 juin 2023 à 18:01:28 UTC+2, matthia…@gmail.com a écrit : > > Earlier error: > [sagelib-10.1.beta4] /usr/bin/ld : ne peut pas trouver -larb : Aucun > fichier ou dos

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

age_conf-no-deps build" fixes the problem Nope. Same problem… Should I try ./configure --with-system-arb=no ? Or even with-system-flint=no ? On Thursday, June 22, 2023 at 3:26:07 AM UTC-7 emanuel.c...@gmail.com wrote: Log enclosed On Thu, Jun 22, 2023 at 7:15 AM Emmanuel Charpentier wr

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

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

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

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

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

On Debian testing, upgrading 10.1.beta1 to 10.1.b eta2, installing ytest and rinning ptestlong gives -- sage -t --long --warn-long 216.6 --random-seed=28094084161727346775594736114467427734 src/sage/coding/linear_code.py # 2

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

On Debian testing, upgrading 10.0 to 10.0.beta1 and running ptestlong gibes the three permanent failures reported for 10.0 : sage -t --long --warn-long 196.8 --random-seed=74389171265200921011491634830844765513 src/sage/c

[sage-release] Re: Sage 10.0 released

Wups ! Incorrect link to the Jupyter kernel problem. See rather here <https://github.com/emacs-jupyter/jupyter/issues/446#issuecomment-1531362962> … Sorry for the noise… ​ Le lundi 22 mai 2023 à 15:19:49 UTC+2, Emmanuel Charpentier a écrit : > On a slightly larger machine (core i7 +

[sage-release] Re: Sage 10.0 released

-seed=70054243461324019656106910472128436065 src/sage/repl/ipython_kernel/kernel.py # 1 doctest failed but I have already met it <https://github.com/emacs-jupyter/jupyter/issues/449> and it seems unrelated to Sage *itself*. HTH, ​ Le lundi 22 mai 2023 à 11:38:32 UTC+2, Emmanuel Charpen

  1   2   3   4   5   6   7   >