<div dir="ltr">2014-10-17 16:00 GMT+02:00 Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>></span>:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Fri, Oct 17, 2014 at 2:56 PM, Adam Jackson <<a href="mailto:ajax@redhat.com">ajax@redhat.com</a>> wrote:<br>
> Yep, this again. I'm just as thrilled as you are. 3.5 is necessary for<br>
> proper ppc64le support, as well as some minor radeonsi features in Mesa.<br>
<br>
</span>And massively improved aarch64 support<br>
<span class=""><br>
> One problem this time around appears to be python-llvmpy, which appears<br>
> to have decided that llvm 3.2/3.3 are the only versions it will support:<br>
><br>
> <a href="https://github.com/llvmpy/llvmpy/commit/1e141931b874dd0bc3d8e9d801b949939430ad4e" target="_blank">https://github.com/llvmpy/llvmpy/commit/1e141931b874dd0bc3d8e9d801b949939430ad4e</a><br>
><br>
> We're already shipping it built against 3.4, so that's truly charming.<br>
> I'm open to suggestions here.<br>
<br>
</span>It doesn't look, with a basic repoquery test, that anything in the<br>
core distro needs python-llvmpy so my general feeling is to query<br>
upstream to see what their intentions are regarding support of newer<br>
releases and if they don't intend to keep up then just drop<br>
python-llvmpy at least for the time being unless the Fedora maintainer<br>
plans to fix it RSN.<br></blockquote><div><br><br></div><div>I initially had intentions to package numba, and other pyhton goodies that depend<br></div><div>on python-llvmpy, but I haven't worked on it on a very long time.<br><br></div><div>So I'm OK with retiring python-llvmpy if a patch doesn't appear soon.<br></div><div>in the tracking bug for 3.5<br><a href="https://github.com/llvmpy/llvmpy/issues/106">https://github.com/llvmpy/llvmpy/issues/106</a></div><div> <br></div><div>Sergio<br></div></div></div></div>