Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve the documentation on `arch_rebuild.txt`

See original GitHub issue

Where should the content be added?

No response

What should be added?

See https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/2679#issuecomment-1084100146. We need to add perhaps to the knowledge base that any feedstocks that could benefit from a rebuild targeting different architectures/platforms should add themselves to this arch_rebuild.txt list. The current mention is too short & terse.

Additional information

No response

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

leofangcommented, Jun 30, 2022

IIRC, the migration bot will send a migration PR to the feedstocks (and their dependencies) listed in arch_rebuild.txt and enable the aarch64/ppc64le builds. It’s very similar to the idea of osx_arm64.txt for the Apple Silicon migration, which is well documented here: https://conda-forge.org/docs/maintainer/knowledge_base.html#apple-silicon-builds

0reactions

ssurbhi560commented, Jun 30, 2022

@jakirkham @leofang, I am working on this, but its still not very clear to me that how does adding a feedstock to arch_rebuild.txt takes care of migrating the feedstocks. Can you please explain this in a little more detail?