[Bot] Update dependencies #1652
Conversation
![manylinux-bot[bot]](https://avatars.githubusercontent.com/in/133399?s=60&v=4){kind=small}
mayeut
force-pushed
the
update-dependencies-pr
branch
from
ae28d78
to
ba71968
Compare
|
@mayeut can we trigger this bot to run again, to update to Python 3.13.0rc1? |
manylinux-bot
bot
force-pushed
the
update-dependencies-pr
branch
from
ba71968
to
eb893d3
Compare
mayeut
force-pushed
the
update-dependencies-pr
branch
from
eb893d3
to
6359a9e
Compare
|
CI is green, looks like this fixes it! I think the issue originated by epel-7 being removed from dl.fedoraproject.org? Moving to epel 8 or 9 is probably a separate effort, right? |
|
travis ci ppc (and apparently s390x) builds have not been running for what appears to be about a week. Conda-forge has been dealing with this as well: conda-forge/status#185 with no apparent status communication from travis about what appears to be a complete outage on given architectures for at least several days. |
|
ppc64 /s390x failure: https://travis-ci.community/t/ppc64-s390x-failing-on-startup/14358 |
The version of EPEL is linked to the RHEL derivative version we use (in the case of manylinux2014, a derivative of RHEL 7) |
Is this failure blocking for the Python 3.13.0rc1 update? |
For ppc64/s390x images only. I'll merge this now, prepare a workaround using GHA with qemu (if it does not time out...) and wait for a feedback from travis-ci for which I now have a support ticket created. |
Update the versions of our dependencies.
PR generated by "Update dependencies" workflow.