-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebuild for icu70 #32
Rebuild for icu70 #32
Conversation
…nda-forge-pinning 2022.03.31.01.43.29
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please restart ci |
OSX error is:
Any ideas? |
Turns out it is compiling against |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/xerces-c-feedstock/actions/runs/2074001716. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2022.05.09.07.08.30
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/xerces-c-feedstock/actions/runs/2394124208. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2022.06.03.11.00.48
Yay! |
@gillins Mhm, the final builds for both osx targets failed after merging. Seems like the server providing the xerces source code was not available at the time of running:
Can you rerun these jobs or does this need a new PR & build version bump? |
I don't seem to have the power to do this (or at least cannot work out how). @ocefpaf is this something you can do? Otherwise maybe we do need to do a new PR... |
Hi, you should be able to. Go to this link: Hit "Re-run.." on the top right https://github.com/conda-forge/xerces-c-feedstock/runs/6737817423 |
Hey that's amazing! I'd never seen that before - thanks. Just done that seems to be running and will keep an eye on it. |
Thank YOU! This PR was surprisingly holding up quite a few things for some reason, e.g. gdal, so hopefully it will improve things ecosystem-wide. I think you ended up rerunning all jobs, which is okay --- but usually there should be an option to rerun only the failed ones. No worries though, because only the new ones will get actually uploaded :) |
I did click the option to re-run failed jobs (I think) but seemed to decide the whole lot needed to be re-run for some reason... Yeah this one has been broken for ages, couldn't work out what was needed to fix it. Did you have to change conda-smithy for this to work? |
No idea... I was just keeping an eye on it for a bit to help move things Funnily enough....... this little CI error is a disaster 😆
|
I will go ahead an fix those manually once the rerun is completed. |
All done @ngam ! |
This PR has been triggered in an effort to update icu70.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/2069113332, please use this URL for debugging.