Not intentional pytorch 2.8.0 upload on osx-arm64?

[traversaro]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

While investigating an unrelated issue (conda-forge/torchcodec-feedstock#27) I looked into the pytorch package in https://conda-metadata-app.streamlit.app/, and I noticed that for both libtorch and pytorch there are 2.8.0 packages only on osx-arm64:

• https://anaconda.org/conda-forge/libtorch/files
• https://anaconda.org/conda-forge/pytorch/files

Given that #409 is still ongoing, I guess this was an error? Perhaps we should mark them as broken, and ensure that in #409 we set the initial build number to 1?

Installed packages

.

Environment info

.

[traversaro]

Apparently the package were built by f140b9f, not sure how they ended up uploaded. fyi @mgorny

[mgorny]

Oh shit, I've accidentally pushed the branch to the wrong remote back then; I've immediately removed it, and I really expected the workflows to fail due to removed branch. Lemme file an admin request to have them removed.

[h-vetinari]

Once the CI is started, removing the branch doesn't make a difference. Only thing you can do is cancel the CI run itself (which you can't do through the GH UI, you need the rights in azure pipelines; in such a case, ping someone - like me or Isuru - who has those).

[hmaarrfk]

There are 2 branches that still exist on the conda-forge feedstock main fork, can we delete those?

[traversaro]

Thanks a lot for the quick fix!