llvmdev v13.0.1 (redux)

[h-vetinari]

Merges #139 with the rc-work of #134.

Also:

• picking up @xhochy as maintainer as per @conda-forge-admin, please add user @xhochy #136 / [ci skip] adding user @xhochy #137.
• adding myself to maintainers as per this comment

Closes #139
Closes #137
Closes #136

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[h-vetinari]

@conda-forge/llvmdev
This is green and should IMO be good to go. It's effectively just a merge of the rc branch with master, plus some pending maintainership updates.

[h-vetinari]

@isuruf, somehow the CI didn't run after merging this...

I'd be happy to retrigger it if I knew how (I remember I encountered this somewhere else already, where you or someone else then managed a restart without an extra commit).

[h-vetinari]

@conda-forge/llvmdev
Can someone reactivate/unblock the CI on master? Otherwise I'm going to try pushing an empty commit to retrigger in ~12 hours.

[h-vetinari]

Thanks to whoever restarted the CI! Can you share the magic sauce of how to do that, or is it core-only?

[h-vetinari]

Can you share the magic sauce of how to do that, or is it core-only?

Looks like core-only:

[jakirkham]

Are you able to login to Azure with your GH account?

[h-vetinari]

Are you able to login to Azure with your GH account?

Yes, but I've never been able to restart anything from Azure, so it's perhaps a question of privileges?. I always need to go through the github trigger to restart jobs (and that page doesn't exist when the CI didn't run).