You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For new builds to be available, via cross-compilation, a migration is required for
1261
+
the package and its dependencies. To request a migration for a particular package
1262
+
and all its dependencies:
1263
+
1264
+
1. Check the feedstock in question to see if there is already an issue or pull request.
1265
+
Opening an issue here is fine, as it might take a couple iterations of the below,
1266
+
especially if many dependencies need to be built as well.
1267
+
2. If nothing is under way, look at the current `conda-forge-pinning <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/osx_arm64.txt>`_.
1268
+
3. If the package is not listed there, make a PR, adding the package
1269
+
name to the end of ``osx_arm64.txt``. The migration bot should start making automated
1270
+
pull requests to the repo and its dependencies.
1271
+
4. Within a few hours, the `status page <https://conda-forge.org/status/#armosxaddition>`_
1272
+
should reflect the progress of the package in question, and help you keep track
1273
+
of progress. Help out if you can!
1274
+
5. The feedstock maintainers (who very likely *do not* have an M1) will work to make
1275
+
any changes required to pass continuous intgration. If you have insight into
1276
+
the particular package, **please** chime in, but most of all **be patient and polite**.
1277
+
6. Once the new builds are available from ``anaconda.org``, please help the maintainers
1278
+
by testing the packages, and reporting back with any problems... but also successes!
0 commit comments