Closed matthewfeickert closed 1 week ago
iirc, at the time when I was testing this package either there was no cython 3 for python 3.12 in conda-forge or it wasn't working. I was planning to revisit this at some point but completely forgot about it. Let me lift the restriction and see what does the CI say.
(there were no problems in linux so probably host
should also have the cross-compilation qualifier)
So, it is still broken (https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=999872&view=logs&j=1b8be447-c2bd-5772-b66a-a1146441bf88&t=0da7bde9-21e8-5d19-f418-738876121ca7&l=1970) but maybe the problem can be patched away.
Thanks @scarlehoff. If you post the full error log as a text file I can try to debug later this upcoming week.
Is the log from the CI not public?
I can just merge or close that PR and you can open one remvoing the <3
.
In any case, I can leave it here (also in pastebin)
Is the log from the CI not public?
No, it is public. I was on my phone when responding and forgot that unlike GitHub Actions logs, Azure Pipeline logs are public.
In any case, I can leave it here (also in pastebin)
Thanks. Having that is useful as a reference artifact.
Comment:
In PR https://github.com/conda-forge/lhapdf-feedstock/pull/18 an upper bound on
cython
v3
was added for both thebuild
andhost
requirementshttps://github.com/conda-forge/lhapdf-feedstock/blob/5cd40801ba1be899220dcb85d3259ed779ae7bd6/recipe/meta.yaml#L20-L23
https://github.com/conda-forge/lhapdf-feedstock/blob/5cd40801ba1be899220dcb85d3259ed779ae7bd6/recipe/meta.yaml#L30-L32
It wasn't super clear from the PR why this was necessary. Is this still required?
Upper bounds on library dependencies can lead to breakage or installation problems in the future, so more curious if this can get changed to a lower bound to avoid breakage, or if there is a fundamental incompatibility with the
lhapdf
source code withcython
v3
that would require a change in the project code itself.