On 2020-11-28 07:32 -0400, David Bremner wrote:
> Wookey writes:
>
> > On 2020-11-27 10:28 -0400, David Bremner wrote:
> >
> >> I'm talking about remove polymake/arm64, not perl.
> >
> > Right, but perl build-depends on polymake, so with no polymake we
> > can't update perl (e.g. for security
Wookey writes:
> On 2020-11-27 10:28 -0400, David Bremner wrote:
>
>> I'm talking about remove polymake/arm64, not perl.
>
> Right, but perl build-depends on polymake, so with no polymake we
> can't update perl (e.g. for security reasons)
>
That doesn't make sense to me. Polymake is software
On 2020-11-27 10:28 -0400, David Bremner wrote:
> I'm talking about remove polymake/arm64, not perl.
Right, but perl build-depends on polymake, so with no polymake we
can't update perl (e.g. for security reasons)
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
Wookey writes:
>> At the risk of being repetitive, this is only a workaround for the perl
>> transition, it does almost nothing for polymake on arm64. The package is
>> still RC buggy since it is compiled with a non-default version of
>> gcc. I'm still looking at an arch-specific removal for
On 2020-11-27 06:52 -0400, David Bremner wrote:
> Wookey writes:
>> On 2020-11-17 21:19 +, Dominic Hargreaves wrote:
>>> Thanks for your work on this. As of today polymake has been uploaded
>>> to use gcc-9 which doesn't have this problem, so the perl transition
>>> has been unblocked.
>>
>>
5 matches
Mail list logo
