[gentoo-dev] dev-python/llvmlite update to 0.32

[gentoo-dev] dev-python/llvmlite update to 0.32

[Aisha Tammy]

Hey all,
  I was hoping to upgrade the dev-python/numba jit compiler in proxy-maint but it depends on dev-python/llvmlite >=0.31
Current version of llvmlite is stuck at 0.30 which is preventing the numba package from being upgraded.
It is at a risk of last rite retiring because its stuck at 3.6

Can anyone bump it to 0.32.1? It just came out 2 days ago so might be best to just work with that.

additional information: don't use the 0.33.* releases as they are testing releases and prone to breaking.

Thanks a lot for the work,
Aisha

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Michał Górny]

W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha Tammy
napisał:
> Hey all,
>   I was hoping to upgrade the dev-python/numba jit compiler in proxy-
> maint but it depends on dev-python/llvmlite >=0.31
> Current version of llvmlite is stuck at 0.30 which is preventing the
> numba package from being upgraded.
> It is at a risk of last rite retiring because its stuck at 3.6

It is more likely to be last rited because upstream still didn't manage
to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't have
the resources to build 3 different LLVM versions.

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Aisha Tammy]

On 5/10/20 2:02 AM, Michał Górny wrote:
> W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha Tammy
> napisał:
>> Hey all,
>>   I was hoping to upgrade the dev-python/numba jit compiler in proxy-
>> maint but it depends on dev-python/llvmlite >=0.31
>> Current version of llvmlite is stuck at 0.30 which is preventing the
>> numba package from being upgraded.
>> It is at a risk of last rite retiring because its stuck at 3.6
> 
> It is more likely to be last rited because upstream still didn't manage
> to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't have
> the resources to build 3 different LLVM versions.
> 
The following issue tells that LLVM 9 is now supported :)
https://github.com/numba/llvmlite/issues/523

They haven't updated their documentation correctly.

PS: regarding lack of resources.
I have a spare computer and am willing to use that to do some testing for 
interesting packages like these. I hope it can help us keep a few more
packages that would otherwise be killed off.

PPS: an aside, but i was always curious where the term last rited came from.
I feel like I am part of the mafia when I use that term XD

Cheers,
Aisha

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Aisha Tammy]

On 5/10/20 7:21 AM, Aisha Tammy wrote:
> On 5/10/20 2:02 AM, Michał Górny wrote:
>> W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha Tammy
>> napisał:
>>> Hey all,
>>>   I was hoping to upgrade the dev-python/numba jit compiler in proxy-
>>> maint but it depends on dev-python/llvmlite >=0.31
>>> Current version of llvmlite is stuck at 0.30 which is preventing the
>>> numba package from being upgraded.
>>> It is at a risk of last rite retiring because its stuck at 3.6
>>
>> It is more likely to be last rited because upstream still didn't manage
>> to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't have
>> the resources to build 3 different LLVM versions.
>>
> The following issue tells that LLVM 9 is now supported :)
> https://github.com/numba/llvmlite/issues/523
> 
another issue which shows that even tests are now working :)
https://github.com/easybuilders/easybuild-easyconfigs/pull/10133

Aisha

> They haven't updated their documentation correctly.
> 
> PS: regarding lack of resources.
> I have a spare computer and am willing to use that to do some testing for 
> interesting packages like these. I hope it can help us keep a few more
> packages that would otherwise be killed off.
> 
> PPS: an aside, but i was always curious where the term last rited came from.
> I feel like I am part of the mafia when I use that term XD
> 
> Cheers,
> Aisha
> 

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Luca Barbato]

On 10/05/2020 13:21, Aisha Tammy wrote:
> On 5/10/20 2:02 AM, Michał Górny wrote:
>> W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha Tammy
>> napisał:
>>> Hey all,
>>>    I was hoping to upgrade the dev-python/numba jit compiler in proxy-
>>> maint but it depends on dev-python/llvmlite >=0.31
>>> Current version of llvmlite is stuck at 0.30 which is preventing the
>>> numba package from being upgraded.
>>> It is at a risk of last rite retiring because its stuck at 3.6
>>
>> It is more likely to be last rited because upstream still didn't manage
>> to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't have
>> the resources to build 3 different LLVM versions.
>>
> The following issue tells that LLVM 9 is now supported :)
> https://github.com/numba/llvmlite/issues/523
> 
> They haven't updated their documentation correctly.
> 
> PS: regarding lack of resources.
> I have a spare computer and am willing to use that to do some testing for
> interesting packages like these. I hope it can help us keep a few more
> packages that would otherwise be killed off.
> 
> PPS: an aside, but i was always curious where the term last rited came from.
> I feel like I am part of the mafia when I use that term XD

It is more about being an undertaker :)

lu

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Michał Górny]

W dniu nie, 10.05.2020 o godzinie 07∶21 -0400, użytkownik Aisha Tammy
napisał:
> On 5/10/20 2:02 AM, Michał Górny wrote:
> > W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha
> > Tammy
> > napisał:
> > > Hey all,
> > >   I was hoping to upgrade the dev-python/numba jit compiler in
> > > proxy-
> > > maint but it depends on dev-python/llvmlite >=0.31
> > > Current version of llvmlite is stuck at 0.30 which is preventing
> > > the
> > > numba package from being upgraded.
> > > It is at a risk of last rite retiring because its stuck at 3.6
> > 
> > It is more likely to be last rited because upstream still didn't
> > manage
> > to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't
> > have
> > the resources to build 3 different LLVM versions.
> > 
> The following issue tells that LLVM 9 is now supported :)
> https://github.com/numba/llvmlite/issues/523
> 
> They haven't updated their documentation correctly.

I suppose this means using the fancy variable to disable LLVM version
checks, correct?

> 
> PS: regarding lack of resources.
> I have a spare computer and am willing to use that to do some testing
> for 
> interesting packages like these. I hope it can help us keep a few
> more
> packages that would otherwise be killed off.

Well, my hardware died two days ago, so I should have more resources
mid-next week.  Until then, only minimal work that can be done with
backup hardware.

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Aisha Tammy]

On 5/10/20 2:11 PM, Michał Górny wrote:
> W dniu nie, 10.05.2020 o godzinie 07∶21 -0400, użytkownik Aisha Tammy
> napisał:
>> On 5/10/20 2:02 AM, Michał Górny wrote:
>>> W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha
>>> Tammy
>>> napisał:
>>>> Hey all,
>>>>   I was hoping to upgrade the dev-python/numba jit compiler in
>>>> proxy-
>>>> maint but it depends on dev-python/llvmlite >=0.31
>>>> Current version of llvmlite is stuck at 0.30 which is preventing
>>>> the
>>>> numba package from being upgraded.
>>>> It is at a risk of last rite retiring because its stuck at 3.6
>>>
>>> It is more likely to be last rited because upstream still didn't
>>> manage
>>> to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't
>>> have
>>> the resources to build 3 different LLVM versions.
>>>
>> The following issue tells that LLVM 9 is now supported :)
>> https://github.com/numba/llvmlite/issues/523
>>
>> They haven't updated their documentation correctly.
> 
> I suppose this means using the fancy variable to disable LLVM version
> checks, correct?
> 
lol, you seem to be experienced with this kind of behaviour :P .
I won't even ask how many times this may have burned you XD .
Indeed, they have changed the version checking feature pretty recently
though nothing too coherent has been given out yet.

Here's to hoping they do it over summer.

>>
>> PS: regarding lack of resources.
>> I have a spare computer and am willing to use that to do some testing
>> for 
>> interesting packages like these. I hope it can help us keep a few
>> more
>> packages that would otherwise be killed off.
> 
> Well, my hardware died two days ago, so I should have more resources
> mid-next week.  Until then, only minimal work that can be done with
> backup hardware.
> 
That sucks, hardware failure is the bane of everyones existence T.T

Cheers and hope things get better,
Aisha

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Michał Górny]

W dniu nie, 10.05.2020 o godzinie 14∶54 -0400, użytkownik Aisha Tammy
napisał:
> On 5/10/20 2:11 PM, Michał Górny wrote:
> > W dniu nie, 10.05.2020 o godzinie 07∶21 -0400, użytkownik Aisha
> > Tammy
> > napisał:
> > > On 5/10/20 2:02 AM, Michał Górny wrote:
> > > > W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha
> > > > Tammy
> > > > napisał:
> > > > > Hey all,
> > > > >   I was hoping to upgrade the dev-python/numba jit compiler
> > > > > in
> > > > > proxy-
> > > > > maint but it depends on dev-python/llvmlite >=0.31
> > > > > Current version of llvmlite is stuck at 0.30 which is
> > > > > preventing
> > > > > the
> > > > > numba package from being upgraded.
> > > > > It is at a risk of last rite retiring because its stuck at
> > > > > 3.6
> > > > 
> > > > It is more likely to be last rited because upstream still
> > > > didn't
> > > > manage
> > > > to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't
> > > > have
> > > > the resources to build 3 different LLVM versions.
> > > > 
> > > The following issue tells that LLVM 9 is now supported :)
> > > https://github.com/numba/llvmlite/issues/523
> > > 
> > > They haven't updated their documentation correctly.
> > 
> > I suppose this means using the fancy variable to disable LLVM
> > version
> > checks, correct?
> > 
> lol, you seem to be experienced with this kind of behaviour :P .
> I won't even ask how many times this may have burned you XD .
> Indeed, they have changed the version checking feature pretty
> recently
> though nothing too coherent has been given out yet.

Well, I've noticed it when I checked if they finally stopped requiring
8.*.  I presumed they've added it instead of proper support for LLVM 9
but didn't expect it to actually pass tests (modulo two silly tests,
one checking version and other exact error message).

> 
> Here's to hoping they do it over summer.
> 
> > > PS: regarding lack of resources.
> > > I have a spare computer and am willing to use that to do some
> > > testing
> > > for 
> > > interesting packages like these. I hope it can help us keep a few
> > > more
> > > packages that would otherwise be killed off.
> > 
> > Well, my hardware died two days ago, so I should have more
> > resources
> > mid-next week.  Until then, only minimal work that can be done with
> > backup hardware.
> > 
> That sucks, hardware failure is the bane of everyones existence T.T
> 

Well, hardware upgrade was long overdue, so there is the bright side. 
My plan was to keep the old PC as backup distcc node but I guess it
wouldn't amount to much.  It was Athlon64 x2 3800+ (from the times when
they still called it 'Athlon64').

In any case, I've just tested the version bump and will push it
shortly.  Thanks!

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] dev-python/llvmlite update to 0.32

[Aisha Tammy]

On 5/11/20 2:35 AM, Michał Górny wrote:
> W dniu nie, 10.05.2020 o godzinie 14∶54 -0400, użytkownik Aisha Tammy
> napisał:
>> On 5/10/20 2:11 PM, Michał Górny wrote:
>>> W dniu nie, 10.05.2020 o godzinie 07∶21 -0400, użytkownik Aisha
>>> Tammy
>>> napisał:
>>>> On 5/10/20 2:02 AM, Michał Górny wrote:
>>>>> W dniu sob, 09.05.2020 o godzinie 22∶39 -0400, użytkownik Aisha
>>>>> Tammy
>>>>> napisał:
>>>>>> Hey all,
>>>>>>   I was hoping to upgrade the dev-python/numba jit compiler
>>>>>> in
>>>>>> proxy-
>>>>>> maint but it depends on dev-python/llvmlite >=0.31
>>>>>> Current version of llvmlite is stuck at 0.30 which is
>>>>>> preventing
>>>>>> the
>>>>>> numba package from being upgraded.
>>>>>> It is at a risk of last rite retiring because its stuck at
>>>>>> 3.6
>>>>>
>>>>> It is more likely to be last rited because upstream still
>>>>> didn't
>>>>> manage
>>>>> to port it to LLVM 9.  I don't have LLVM 8 anymore, and I don't
>>>>> have
>>>>> the resources to build 3 different LLVM versions.
>>>>>
>>>> The following issue tells that LLVM 9 is now supported :)
>>>> https://github.com/numba/llvmlite/issues/523
>>>>
>>>> They haven't updated their documentation correctly.
>>>
>>> I suppose this means using the fancy variable to disable LLVM
>>> version
>>> checks, correct?
>>>
>> lol, you seem to be experienced with this kind of behaviour :P .
>> I won't even ask how many times this may have burned you XD .
>> Indeed, they have changed the version checking feature pretty
>> recently
>> though nothing too coherent has been given out yet.
> 
> Well, I've noticed it when I checked if they finally stopped requiring
> 8.*.  I presumed they've added it instead of proper support for LLVM 9
> but didn't expect it to actually pass tests (modulo two silly tests,
> one checking version and other exact error message).
> 
>>
>> Here's to hoping they do it over summer.
>>
>>>> PS: regarding lack of resources.
>>>> I have a spare computer and am willing to use that to do some
>>>> testing
>>>> for 
>>>> interesting packages like these. I hope it can help us keep a few
>>>> more
>>>> packages that would otherwise be killed off.
>>>
>>> Well, my hardware died two days ago, so I should have more
>>> resources
>>> mid-next week.  Until then, only minimal work that can be done with
>>> backup hardware.
>>>
>> That sucks, hardware failure is the bane of everyones existence T.T
>>
> 
> Well, hardware upgrade was long overdue, so there is the bright side. 
> My plan was to keep the old PC as backup distcc node but I guess it
> wouldn't amount to much.  It was Athlon64 x2 3800+ (from the times when
> they still called it 'Athlon64').
> 
> In any case, I've just tested the version bump and will push it
> shortly.  Thanks!
> 

Oooooh, thanks a lot for your work!

Aisha