Update/2023.2

[oleksandr-pavlyk]

Checklist

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

Updated sources to use bits from oneAPI 2023.2

[conda-forge-webservices[bot]]

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) and found some lint.

Here's what I've got...

For recipe:

• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• pin_compatible should be used instead of pin_subpackage for dpcpp_impl_win-64 because it is not a known output of this recipe: ['intel-cmplr-lic-rt', 'intel-cmplr-lib-rt', 'intel-fortran-rt', 'intel-opencl-rt', 'dpcpp-cpp-rt', 'dpcpp_impl_linux-64', 'dpcpp_linux-64', 'oneccl-devel', 'intel-compiler-repack'].

[oleksandr-pavlyk]

@beckermr I attempted to bump sysroot to 2.28 here, but it failed. I see that alma8 docker image has been added already (https://github.com/conda-forge/docker-images/pull/235). How should I instruct conda-forge to use it?

[beckermr]

Yes we've had to stop our roll out of 2.28 due to all of the upheaval with rhel and the rest of the ecosystem. Can this pr wait?

[oleksandr-pavlyk]

@beckermr I would prefer to publish 2023.2 with 2.17 and increment build number of the next PR where sysroot version is bumped. Thank you for the update!

[beckermr]

That sounds great! Thank you so much for keeping this up to date!