> Instead of modifying the .gitattributes file, you could try adding it to
> .git/info/attributes which is local to your repository.
>
>
Thank you. I will try that next time.
I am a little hesitant to modify the full repo .gitattributes with this as
this might have a number of other unintended
On Monday, February 14, 2022 at 1:25:50 PM UTC-8 jus...@mac.com wrote:
> Built w/o problems on macOS 10.15.7 (2019 MBP, 8-core Core i9). All tests
> (‘ptestlong’) passed!
>
> Quick! Ship it!!
>
+1 on starting a release candidate cycle soon
--
You received this message because you are subs
Built w/o problems on macOS 10.15.7 (2019 MBP, 8-core Core i9). All tests
(‘ptestlong’) passed!
Quick! Ship it!!
Justin
On Feb 13, 2022, at 04:02, Volker Braun wrote:
As always, you can get the latest beta version from the "develop" git branch.
Alternatively, the self-contained source tarb
Built w/o problems on macOS 10.15.7 (2019 MBP, 8-core Core i9).
Testing (‘ptestlong’) yielded 8 failures. Seven were do directly to “bad CPU
ID” in Imagemagick/convert” (all due to my failure to get Imagemagick updated).
One seems related to Volker’s note below:
File "src/sage/misc/latex.py",
On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from Sage 9.6.beta0 with system python (3.8.10)
failed with the error:
[sagemath_doc_html-none] ImportError: libflint.so.15: cannot open shared
object file: No such file or directory
Running "make sagelib-clean" as s
On Sun, Feb 13, 2022 at 12:08:09PM -0800, Matthias Köppe wrote:
> Running "make sagelib-clean" could help.
Thanks, it seems to unlock most patchbots.
Ciao,
Thierry
>
> On Sunday, February 13, 2022 at 9:30:21 AM UTC-8 sage-goo...@lma.metelu.net
> wrote:
>
> > Hi,
> >
> > Thanks for the releas
