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

2023-11-12 Thread Kenji Iohara
On Mac OS 13.6.1 with Intel Core i5, I should run ./configure —with-system-gfortran=no to compile from the first built. > 11/11/2023 20:09、John H Palmieri のメール: > > Same on OS X Apple M2 chip. In both this and the earlier case, I ran > `./configure` — no need to do `./configure

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

2023-11-12 Thread Volker Braun
Reset a local branch: git reset --hard e349b002499 force push to the remote branch of your choice as usual. On Sunday, November 12, 2023 at 9:39:56 AM UTC+1 david@gmail.com wrote: > > > I just corrected a mistake, so if your head commit is not e349b002499 > then please reset. > > Can

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

2023-11-12 Thread David Coudert
> I just corrected a mistake, so if your head commit is not e349b002499 then > please reset. Can anyone explain me the proper procedure to do that ? Should I reset head in the branch develop and then force push to the develop branch of my GitHub clone ? I’m not a git / GitHub expert.

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

[sage-release] Sage 10.2.rc1 released

2023-11-10 Thread Volker Braun
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html I just corrected a mistake, so if your head commit is not e349b002499 then please reset. e349b002499 (tag: