[CFEP-03] Manual upload for `osx-arm64` packages

[hadim]

pypdfium2 packages cannot be built using the c-f CI infra (see https://github.com/conda-forge/pypdfium2-feedstock/pull/6 for details). But osx-arm64 builds are supported and works fine when running natively on an osx-arm64 machine (tested on both local machine and using GHA osx-arm64 runners).

As of today, c-f does not allow using GHA for building packages (see https://conda-forge.zulipchat.com/#narrow/channel/457337-general/topic/GitHub.20Actions.20for.20aarch64.3F and https://conda-forge.zulipchat.com/#narrow/channel/457337-general/topic/Native.20CI.20for.20osx-arm64.20and.20linux-aarch64).

It might be possible in the future, but even if it does, it might take time.

I have successfully built pypdfium2 on a private GH forge relying on rattler-build and all the packages have been uploaded to https://prefix.dev/channels/pypdfium2-public/packages/pypdfium2.

@conda-forge/core would that be acceptable and possible to manually upload those packages to the c-f channel? I can always move those packages to an anaconda channel if that is preferred, and also provide the build logs for every package.

[hadim]

I want to add that building pdfium on c-f might help the cross compilation but after giving it a shot, I finally gave up given how complex the build seems to be (and I am also not super familiar with the chromium/depot_tools infra builds). See https://github.com/conda-forge/pypdfium2-feedstock/issues/4#issuecomment-2469192619 for details.

[jaimergp]

See https://github.com/conda-forge/admin-requests#request-a-cfep-3-copy-to-conda-forge for instructions. I think we need the packages in an anaconda.org channel, to begin with, so we can use anaconda copy.

[hadim]

Thank you @jaimergp. Here is the admin request: https://github.com/conda-forge/admin-requests/pull/1398