As discussed in #gentoo-portage yesterday: After a new EAPI has been
approved, there is a period during which there is no stable Portage
version supporting the new EAPI, and ebuilds for the new EAPI should
not be stabilised during that period. Add a new "eapis-testing" key
to layout.conf, so that d
# Mike Gilbert (2021-06-17)
# rescan-scsi-bus.sh is installed by >=sys-apps/sg3_utils-1.44, rendering
# this package redundant.
# Removal on 2021-07-17.
sys-apps/rescan-scsi-bus
> On Thu, 17 Jun 2021, Guilherme Amadio wrote:
> There's actually a much simpler solution to this:
> $ is_prime() { test $(factor $1 | cut -d: -f2 | wc -w) == 1; }
> $ for n in $(seq 0 10); do is_prime $n && echo $n is prime; done
> 2 is prime
> 3 is prime
> 5 is prime
> 7 is prime
> $ time f
On Fri, 2021-06-18 at 18:26 +0200, Ulrich Müller wrote:
> As discussed in #gentoo-portage yesterday: After a new EAPI has been
> approved, there is a period during which there is no stable Portage
> version supporting the new EAPI, and ebuilds for the new EAPI should
> not be stabilised during that
> On Fri, 18 Jun 2021, Michał Górny wrote:
>> +Post-History: 2021-05-19 2021-06-18
> Sorry for failing to notice it earlier but you've missed a comma between
> the dates.
Thanks. Updated locally.
signature.asc
Description: PGP signature
>
> This depends on the actual domain of numbers. If the primes involved
> have 20 digits as in your example, then factor should be used of course.
>
> I suspect though that we're talking about small numbers (below 100?)
> here, in which case a solution in pure bash would be preferable.
>
If so
Am Freitag, 18. Juni 2021, 21:10:27 CEST schrieb Michael Orlitzky:
> > This depends on the actual domain of numbers. If the primes involved
> > have 20 digits as in your example, then factor should be used of course.
> >
> > I suspect though that we're talking about small numbers (below 100?)
> >