potiuk opened a new pull request, #72058:
URL: https://github.com/apache/airflow/pull/72058

   `ibm-db` publishes no Linux aarch64 wheel and its sdist fails to build there 
with `NameError: name 'arch_' is not defined`, so every `linux/arm64` CI image 
build has failed since the ibm.db2 provider merged — blocking the scheduled ARM 
run on `main`.
   
   This applies the mechanism already used for `ibm.mq`: declare 
`excluded-platforms` in `provider.yaml` so the provider leaves the ARM test 
matrix, and translate that into install-time environment markers so it is never 
pulled in there. `ibm-db-sa` is pure Python but depends on `ibm-db`, so it 
carries the same marker.
   
   While doing so it corrects that mechanism. `EXCLUDED_PLATFORM_MACHINES` 
mapped `linux/arm64` to both `aarch64` and `arm64`, which is wrong in general — 
`platform.machine()` reports `aarch64` on Linux and `arm64` on macOS, so those 
are distinct targets rather than two spellings of one. IBM *does* ship 
`macosx_*_arm64` wheels for `ibm-db`, so excluding `arm64` would have removed a 
working driver from Apple Silicon for no reason. Each platform now contributes 
only its own machine spelling, and a provider that is unusable on every ARM 
target says so by listing both platforms — which is what `ibm.mq` now does. Its 
generated markers in the meta-package are unchanged, so that provider's 
behaviour is identical.
   
   Supersedes #72021, which fixes the same build failure but leaves `ibm.db2` 
in the ARM test matrix.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Opus 5 (1M context)
   
   Generated-by: Claude Opus 5 (1M context) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to