Update to V1.2.4

[stewartboogert]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[stewartboogert]

@conda-forge-admin, please rerender

[github-actions]

        Hi! This is the friendly automated conda-forge-linting service.

        I wanted to let you know that I linted all conda-recipes in your             PR (```recipe/meta.yaml```) and found some lint.

        Here's what I've got...

For recipe/meta.yaml:

• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like I wasn't able to push to the v1.2.4 branch of g4edge/pyg4ometry-feedstock. Did you check the "Allow edits from maintainers" box?

NOTE: Our webservices cannot push to PRs from organization accounts or PRs from forks made from organization forks because of GitHub permissions. Please fork the feedstock directly from conda-forge into your personal GitHub account.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pyg4ometry-feedstock/actions/runs/11085054444.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[stewartboogert]

@chrisburr @tomlatham

I think after much messing around (basically learning about Conda-forge) I have an updated feedstock for pyg4ometry. It builds for linux and osx-64, but not osx-arm65.I would like to confirm the build for osx-arm64, but hit a strange bug where the python appears to be for the wrong arch. Take a look at the failing tests on azure, I copy the error here

4:44:10.5726880Z +DEBUG_CXXFLAGS=-ftree-vectorize -fPIC -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -fmessage-length=0 -Og -g -Wall -Wextra -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/pyg4ometry-1.2.4 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix 2024-10-01T14:44:10.6949070Z /Users/runner/miniforge3/conda-bld/pyg4ometry_1727793576695/work/conda_build.sh: line 4: /Users/runner/miniforge3/conda-bld/pyg4ometry_1727793576695/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehol/bin/python: Bad CPU type in executable

Any help or thoughts would be appreciated.

[tomlatham]

Thanks for this, @stewartboogert, it looks in much better shape than I managed in #15, which I've now closed.

I'm not sure what's going on with the osx-arm64 build but maybe @chrisburr might have an idea.

[chrisburr]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like I wasn't able to push to the v1.2.4 branch of g4edge/pyg4ometry-feedstock. Did you check the "Allow edits from maintainers" box?

NOTE: Our webservices cannot push to PRs from organization accounts or PRs from forks made from organization forks because of GitHub permissions. Please fork the feedstock directly from conda-forge into your personal GitHub account.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13124420857. Examine the logs at this URL for more detail.}