Update subpackage pin versions for generic packages

[sshockwave]

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.

Fixes: #124 (comment)

pin_subpackage defaults to min_pin='x.x.x.x.x.x and max_pin='x'. exact=True also includes the build string, which limits the platform of the dependencies to the one used to build the generic package. Both are unintended.

[conda-forge-webservices]

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) and found it was in an excellent condition.

[sshockwave]

@conda-forge-admin please rerender

[github-actions]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[sshockwave]

@conda-forge-admin please restart ci

[pkgw]

The Cargo build tests on the Linux cross-arch platforms are getting killed:

+ cargo install --force xsv
    Updating crates.io index
/home/conda/feedstock_root/build_artifacts/rust-split_1683256056938/test_tmp/run_test.sh: line 10:  3283 Killed                  cargo install --force xsv

I don't think that this is simply due to a timeout or anything, but I don't see any hints about why this is happening ☹️

[isuruf]

If it takes too much memory, then the process might get killed.

[pkgw]

Has anything changed about the Azure infrastructure recently? This PR shouldn't affect anything like that, I'd hope. (One could do a test and see what happens if the main branch is rebuilt as-is.)

(edit: or maybe the Crates.io index just passed some size threshold that leads to problems on these platforms, perhaps??)

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[sshockwave]

(edit: or maybe the Crates.io index just passed some size threshold that leads to problems on these platforms, perhaps??)

@pkgw I agree. These two platforms seem to be using QEMU containers for emulation. Similar OOM issues are reported in rust-lang/cargo#10583 (comment) where replacing libgit2 with git cli is a workaround.

However, I believe that HTTP-based sparse-registry rust-lang/cargo#11224 (comment) is the future-proof way for CIs. Should be available since rust 0.68.0.

[isuruf]

Thanks