From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: singular: update to 4.3.1p2 (fix gcc 12 build)
Date: Mon, 10 Oct 2022 22:31:05 +0200 [thread overview]
Message-ID: <20221010203105.9xCif2M5hFNoiFXxlX0PnhZmWR_47G_0CDqbmh3VocM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39866@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/39866#issuecomment-1273792233
Comment:
> Sure, that's fine with me. Just incorporate this one there?
Sure, I will.
Just FYI, a few doctest failures in sagemath 9.5 are expected, mostly safe to ignore. Right now I have all doctests passing with sagemath 9.7 + a few patches (less than in 9.5). However, that's using matplotlib 3.5.3. I haven't yet started working on matplotlib 3.6 (which causes most of the failures you have here, #39857 is a first step that I'm yet to test, but I'm not sure that will be enough).
I will include this in my sagemath PR, together with other updates I've been doing (some of which work ok independently of sagemath, others like singular need rebuild of sagemath).
> Also perhaps have a look at the python3.11 update, I think it's also updating sage.
Sure, but locking sagemath update to python update seems more difficult. OTOH locking singular and sagemath seems more reasonable (unless you have a pressing reason to update singular, if so don't wait for me).
Anyway, maybe worth testing the sagemath update with python 3.11 just to make sure everything works.
BTW, the stupid limit recent python imposed on "int(s)" is also causing a few failures but they will go away with sagemath 9.7 (they just disable the limit).
next prev parent reply other threads:[~2022-10-10 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 14:47 [PR PATCH] " dkwo
2022-10-10 18:08 ` [PR PATCH] [Updated] " dkwo
2022-10-10 19:01 ` tornaria
2022-10-10 19:47 ` dkwo
2022-10-10 20:31 ` tornaria [this message]
2022-10-10 20:37 ` dkwo
2022-10-10 21:23 ` tornaria
2022-10-10 21:28 ` [PR PATCH] [Updated] " dkwo
2022-10-10 21:37 ` tornaria
2022-10-10 21:43 ` [PR PATCH] [Updated] " dkwo
2022-10-10 21:50 ` tornaria
2022-10-11 13:47 ` dkwo
2022-10-12 11:27 ` leahneukirchen
2022-10-12 12:08 ` tornaria
2022-10-12 12:16 ` leahneukirchen
2022-10-12 14:50 ` dkwo
2022-10-12 14:50 ` [PR PATCH] [Closed]: " dkwo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221010203105.9xCif2M5hFNoiFXxlX0PnhZmWR_47G_0CDqbmh3VocM@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).