On 02/23/2017 05:57 AM, Jeroen Demeyer wrote:
> Sorry, but I do not like your idea. I don't feel like being forced to run
>
> ./configure --with-gcc --with-zlib --with-mpir --with-r --with-glpk
> --with-git --with-ppl --with-pari --with-libgap ... # 80 packages more
>
> just because I don't have
On 11/05/2016 07:19 PM, 'Bill Hart' via sage-release wrote:
>
> Someone reported the issue to us, but we have never heard of PIE, much
> less do we know what to do about it.
>
PIE is like PIC, but for executables. Shared libraries can't rely on
fixed addresses because multiple programs may have
On 10/01/2016 07:49 PM, Francois Bissey wrote:
> Do you know what is the status in Gentoo? I haven’t seen anything
> about it but you could have.
>
According to kentnl, upstream is even considering the change for
perl-5.22.3 and perl-5.24.1. The perl team plans to patch it out of
v5.22.3 for sure
On 10/01/2016 03:19 PM, Francois Bissey wrote:
> OK looking closer the perl module is in pari’s sources in `src/desc`.
> It looks like pari relies on “.” being part of `@INC` but it is false in your
> case.
>
This should be fixed in PARI:
https://lists.debian.org/debian-devel-announce/2016/08/m
This is still a problem in the new sage-7.3:
https://trac.sagemath.org/ticket/20646
The fix for GSL is to apply the Gentoo patch.. it looks like the easiest
way to fix linbox might be with an upgrade, since linbox-1.4.1.ebuild
drops the associated hack.
--
You received this message because yo
On 03/12/2016 01:05 PM, Volker Braun wrote:
> IMHO that test is ridiculously slow for what it does. How does
> min_rays=7 test anything that isn't already tested with min_rays=4, say?
> It just grinds CPU cycles, but doesn't cover any new line of code.
>
It's easy to get four rays in three dimens
On 03/12/2016 12:54 AM, Andrey Novoseltsev wrote:
> On Friday, 11 March 2016 03:08:47 UTC-7, Volker Braun wrote:
>
> I've seen that before on the buildbot. The doctest in question
> generates a random cone, it might randomly pick a very hard problem
> (even though we should be fixing t
On 01/30/2016 05:31 AM, Jeroen Demeyer wrote:
> On 2016-01-30 10:32, Nathann Cohen wrote:
>> I think that' s what the .p1, .p2, .p are useful for.
> No. The .p1... is for adding patches or changing spkg-install with the
> *same* tarball.
>
The "patch level" or "revision" suffix that all package
