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

2024-03-29 Thread 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

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

2024-03-29 Thread 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 backdoor

[sage-release] xz/liblzma has been compromised

2024-03-29 Thread 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

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

2024-03-20 Thread Dima Pasechnik
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 f

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

2024-03-20 Thread 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:

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

2024-03-18 Thread 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 par

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

2024-03-18 Thread 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

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

2024-03-11 Thread 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

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

2024-03-11 Thread 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: >

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

2024-02-27 Thread 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

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

2024-02-15 Thread 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

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

2024-01-24 Thread 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

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

2023-12-15 Thread 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

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

2023-12-09 Thread 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,

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

2023-12-09 Thread Dima Pasechnik
t. 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 a

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

2023-12-09 Thread 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

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

2023-11-15 Thread 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, IM

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

2023-11-15 Thread 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

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

2023-11-15 Thread 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

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

2023-11-13 Thread 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

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

2023-11-10 Thread 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. >

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

2023-11-01 Thread 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 fo

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

2023-11-01 Thread 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 implemen

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

2023-11-01 Thread 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): > .

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

2023-11-01 Thread 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) ==

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

2023-10-31 Thread 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

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

2023-10-16 Thread 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 i

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

2023-10-16 Thread Dima Pasechnik
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/patche

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

2023-10-16 Thread 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 : > &

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

2023-10-16 Thread 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 fo

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

2023-10-16 Thread 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

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

2023-10-16 Thread 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.lo

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

2023-10-16 Thread Dima Pasechnik
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

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

2023-10-16 Thread Dima Pasechnik
77s > *** > 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:

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

2023-10-09 Thread 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 >

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

2023-10-09 Thread Dima Pasechnik
onday, 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,

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

2023-10-09 Thread 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 th

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

2023-10-09 Thread 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, s

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

2023-10-09 Thread 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 : >

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

2023-10-09 Thread Dima Pasechnik
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 :

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

2023-10-09 Thread 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

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

2023-10-09 Thread 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

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

2023-10-09 Thread 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 : >

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

2023-09-24 Thread Dima Pasechnik
ot 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 P

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

2023-09-24 Thread Dima Pasechnik
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 >> c

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

2023-09-23 Thread Dima Pasechnik
arranty; 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

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

2023-09-23 Thread Dima Pasechnik
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 ins

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

2023-09-23 Thread Dima Pasechnik
; 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? &

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

2023-09-22 Thread 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

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

2023-09-18 Thread Dima Pasechnik
>>> ./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' &

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

2023-09-17 Thread 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"

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

2023-08-14 Thread 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, w

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

2023-08-14 Thread 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 |

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

2023-08-02 Thread 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 : > > > > *

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

2023-08-01 Thread 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 > >

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

2023-08-01 Thread 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 >

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

2023-07-02 Thread 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 >

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

2023-06-28 Thread 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 >>

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

2023-06-22 Thread 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 >

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

2023-06-16 Thread 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

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

2023-05-23 Thread 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

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

2023-05-23 Thread 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

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

2023-05-21 Thread 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

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

2023-05-21 Thread 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: > > &

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

2023-05-21 Thread 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/sagema

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

2023-05-21 Thread 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

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

2023-05-14 Thread 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

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

2023-05-06 Thread 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 >

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

2023-04-26 Thread 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

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

2023-04-03 Thread 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 >

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

2023-03-27 Thread 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

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

2023-03-27 Thread 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 > >

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

2023-02-19 Thread 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

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

2023-02-19 Thread 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

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

2023-02-12 Thread 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

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

2023-02-12 Thread 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 pro

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

2023-02-12 Thread 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. > >

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

2023-02-12 Thread 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

Re: [sage-release] Sage 9.8 released

2023-02-11 Thread 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

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

2023-02-11 Thread 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

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

2023-02-06 Thread 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 : > >>

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

2023-02-05 Thread Dima Pasechnik
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: > > > > &g

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

2023-02-05 Thread Dima Pasechnik
./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

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

2023-02-05 Thread Dima Pasechnik
(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 >

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

2023-02-05 Thread 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-py

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

2023-02-05 Thread Dima Pasechnik
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. >

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

2023-02-04 Thread Dima Pasechnik
ng 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 fro

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

2023-02-04 Thread Dima Pasechnik
ing 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 UT

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

2023-02-04 Thread Dima Pasechnik
l 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 incremen

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

2023-02-04 Thread Dima Pasechnik
t 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

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

2023-02-03 Thread 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]

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

2023-02-02 Thread 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

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

2023-01-25 Thread 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 >

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

2023-01-25 Thread Dima Pasechnik
>> 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

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

2023-01-24 Thread 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',

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

2023-01-20 Thread 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>

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

2023-01-20 Thread 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

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

2023-01-19 Thread Dima Pasechnik
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

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

2022-12-22 Thread Dima Pasechnik
to make -j20 after > [sagemath_doc_html-none] successfully installed. > in order to speed up the real tests. > > Guillermo > > On Thu, 22 Dec 2022 at 10:57, Dima Pasechnik wrote: > >> does it happen if you explicitly call ./sage -docbuild ? >> (it's pr

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

2022-12-22 Thread Dima Pasechnik
does it happen if you explicitly call ./sage -docbuild ? (it's probably related to our parallel docbuilding code...) On Thu, Dec 22, 2022 at 6:06 AM John H Palmieri wrote: > > And it would be great if we could fix it, but I don't know what the problem > is. I've seen it on both Apple Silicon

  1   2   3   4   5   6   >