From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pari seadata and seadata-big , fix wildcard on vcopy
Date: Thu, 17 Sep 2020 10:39:44 +0200 [thread overview]
Message-ID: <20200917083944.wgkbwKaQidaePJrPKz9H4G_-ekcmpLJCCNMjoEqKSe0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24946@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
New comment by motorto on void-packages repository
https://github.com/void-linux/void-packages/pull/24946#issuecomment-694086338
Comment:
> So they need to be placed inside `/usr/share/pari` instead of `/usr/share/pari/seadata`? If yes, all other `pari-*` needs to be fixed too.
Yes @sgn , that was the problem, (and the ??? ) , well I tried the other packages with the test upstream offers , and they all work.
> D. To test whether a package is available.
>
> Here are sample commands that will fail if a given package is not available:
>
> ellinit("11a1") /* package: elldata */
> galoisgetpol(8) /* package: galpol */
> galoisgetname(12,1) /* package: galpol 4.0 and up */
> ellmodulareqn(11) /* package: seadata */
> polgalois(x^8-2) /* package: galdata */
https://pari.math.u-bordeaux.fr/packages.html
Edit:
------
Checked the other packages and they all seem to copy to /usr/share/pari , so they are okay !
next prev parent reply other threads:[~2020-09-17 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 19:14 [PR PATCH] " motorto
2020-09-16 20:39 ` [PR PATCH] [Updated] " motorto
2020-09-17 0:26 ` sgn
2020-09-17 0:27 ` [PR REVIEW] " sgn
2020-09-17 8:10 ` dkwo
2020-09-17 8:33 ` [PR PATCH] [Updated] " motorto
2020-09-17 8:35 ` motorto
2020-09-17 8:37 ` motorto
2020-09-17 8:39 ` motorto [this message]
2020-09-17 8:39 ` motorto
2020-09-21 14:55 ` [PR PATCH] [Merged]: " sgn
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=20200917083944.wgkbwKaQidaePJrPKz9H4G_-ekcmpLJCCNMjoEqKSe0@z \
--to=motorto@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).