From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sagemath-9.5: package updates and fixes
Date: Mon, 04 Apr 2022 22:22:56 +0200 [thread overview]
Message-ID: <20220404202256.fBlmNGfOIjMxOiv44Hnr5mPIn9K_vnSDG5FCilPqHh0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
There's a merged pull request on the void-packages repository
sagemath-9.5: package updates and fixes
https://github.com/void-linux/void-packages/pull/36420
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
This includes
- upgrade to lrcalc-2.1 (from #36209)
- _already merged_ ~upgrade to sympy-1.10.1 (from #36397)~
- _postponed_ ~upgrade to SuiteSparse-5.11.0, igraph-0.9.7, planarity-3.0.2.0, python3-cvxopt-1.3.0 (from #36423)~
- _already merged_ ~upgrade to giac-1.7.0.53 (from #36421)~
- _already merged_ ~upgrade to gp2c-0.0.12pl1 (from #36422)~
- new package threejs-sage for 3d plots (#36504)
- backported fixes for sagemath-9.5 to accomodate these upgrades, and also ipython and scipy upgrades which are already merged
~I want to see if the CI can cope with this. Otherwise I'll just split this in a few separate PR. Except for the upgrade to lrcalc-2.1, which must be coordinated with sage, everything else can be handled separately.~
cc: @dkwo
EDIT: I ended up making 3 new PR to handle the packages that can be upgraded separately from sagemath (#36397, #36421, #36422, #36423 should be ok to merge if CI passes).
EDIT 2: this PR is now just to upgrade lrcalc to 2.1 (will be needed for sagemath-9.6) and fix sagemath-9.5 so it works with lrcalc 2.1 (and several minor doctest fixes for upgrades to ipython, scipy, sympy).
EDIT 3: rebased on top of #36504 (new package threejs-sage) and fix sagemath config to use it, now 3d plots work
next prev parent reply other threads:[~2022-04-04 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 13:55 [PR PATCH] " tornaria
2022-03-30 14:48 ` dkwo
2022-04-01 16:07 ` Eloitor
2022-04-01 16:20 ` tornaria
2022-04-01 16:29 ` Eloitor
2022-04-01 16:46 ` dkwo
2022-04-01 19:57 ` [PR PATCH] [Updated] " tornaria
2022-04-03 15:24 ` tornaria
2022-04-04 1:24 ` tornaria
2022-04-04 20:22 ` leahneukirchen [this message]
2022-04-09 0:25 ` Duncaen
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=20220404202256.fBlmNGfOIjMxOiv44Hnr5mPIn9K_vnSDG5FCilPqHh0@z \
--to=leahneukirchen@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).