Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Update primesieve to 8.0 and primecount to 7.4.
Date: Sun, 09 Oct 2022 18:19:50 +0200	[thread overview]
Message-ID: <20221009161950.kl4oTVUl64NeJCLemftkblL_1bEsa09xd1DJiPlQLHI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39837@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

There's a merged pull request on the void-packages repository

Update primesieve to 8.0 and primecount to 7.4.
https://github.com/void-linux/void-packages/pull/39837

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

Note: `primesieve` had a soname bump, but it's only used directly by `primecount`. The latter did not bump soname.

Moreover the only use of these libraries in our repo is in `sagemath`, and only through `python3-primecountpy` which does NOT need revbump. Everything can be tested directly in the cli:
```
$ sage -c 'print(prime_pi(10^15))'
29844570422669
$ python -c 'from primecountpy import prime_pi ; print(prime_pi(10**15))'
29844570422669
$ primecount $[10**15]
29844570422669
$ xbps-query --regex -s 'prime(count|sieve)|sagemath-'
[*] primecount-7.4_1             Fast prime counting function
[*] primecount-devel-7.4_1       Fast prime counting function - development files
[*] primesieve-8.0_1             Fast prime number generator
[*] primesieve-devel-8.0_1       Fast prime number generator - development files
[*] python3-primecountpy-0.1.0_1 Python interface to the C++ library primecount
[*] sagemath-9.5_2               Open source mathematics software
```



<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      reply	other threads:[~2022-10-09 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 14:55 [PR PATCH] " tornaria
2022-10-09 16:19 ` classabbyamp [this message]

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=20221009161950.kl4oTVUl64NeJCLemftkblL_1bEsa09xd1DJiPlQLHI@z \
    --to=classabbyamp@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).