Re: [sage-devel] asking for setting up cythonizing compiling

2022-01-21 Thread Randall
I am carefully following the steps on the https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source webpage but 2 things already have come up. The latest download version on the tar ball page is version 9.4 sage. The latest git clone version is 9.5 rc3, but the i

[sage-devel] Re: patchbot owners, please update to 3.0.3

2022-01-21 Thread Frédéric Chapoton
lrslib doctests in game_theory/parser.py are fixed in #33101 (positive review) Le vendredi 21 janvier 2022 à 13:40:17 UTC+1, Samuel Lelievre a écrit : > Hi Frédéric, > > I have upgraded to sage-patchbot 3.0.4 on "pascaline". > > On Sage 9.5.rc2, "ticket 0" failed with > -

[sage-devel] Re: patchbot owners, please update to 3.0.3

2022-01-21 Thread Samuel Lelievre
Hi Frédéric, I have upgraded to sage-patchbot 3.0.4 on "pascaline". On Sage 9.5.rc2, "ticket 0" failed with -- SEED=94195001484901963602666886307845237936 alias sagetest=".sage -t --long --random-seed=$SEED" sagetest src/sage/fea

Re: [sage-devel] Re: patchbot owners, please update to 3.0.3

2022-01-21 Thread Dima Pasechnik
On Fri, Jan 21, 2022 at 9:43 AM 'jonatha...@googlemail.com' via sage-devel wrote: > > Hi Frédéric, > > due to https://trac.sagemath.org/ticket/33027 I have given up on running my > patchbot. I've made this ticket a blocker. Everyone who has an idea about sage-cleaner, please have a look. Natura

[sage-devel] Re: patchbot owners, please update to 3.0.3

2022-01-21 Thread 'jonatha...@googlemail.com' via sage-devel
Hi Frédéric, due to https://trac.sagemath.org/ticket/33027 I have given up on running my patchbot. Jonathan Frédéric Chapoton schrieb am Montag, 17. Januar 2022 um 21:31:31 UTC+1: > and to fix the remaining doc-cleaning issue, please upgrade again to the > master branch of github (aka tag 3.0

Re: [sage-devel] trouble pushing to a ticket

2022-01-21 Thread Markus Wageringel
> > OpenSSH 8.8 (recently stable on Gentoo) disables RSA with SHA-1. You > can work around it, but probably the best long-term solution is to > replace your RSA key with an ECDSA one (ssh-keygen -t ecdsa) and re- > upload it to trac. By the way, the trac server seems to be using an old versi