[CI][Packaging] conda build failures

[asfimport]

It seems many of the conda packaging nightly builds are failing due to conda dependency resolution errors, example here:
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=12793&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=3049

Reporter: Antoine Pitrou / @pitrou
Assignee: Joris Van den Bossche / @jorisvandenbossche

Related issues:

• [Packaging] Dependency resolution issues in the nightly conda builds (supercedes)

PRs and other links:

• GitHub Pull Request #12492

_{Note: This issue was originally created as ARROW-14256. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
@xhochy

[asfimport]

Uwe Korn / @xhochy:
This seems to be a general conda/conda-build issue with the release of OpenSSL 3.0. Not all dependencies of arrow-cpp support it yet but conda aggressively updates it to 3.0 and thus generates the conflicts.

[asfimport]

Uwe Korn / @xhochy:
Upstream issue: conda-forge/conda-forge.github.io#1528

[asfimport]

Jonathan Keane / @jonkeane:
Once the upstream issue is resolved, remove the tasknames with ~ in front of them to re-add these to our nightly set:

arrow/dev/tasks/tasks.yml

Lines 146 to 159 in 987d47a

	# ARROW-14256
	- ~conda-linux-gcc-py310-arm64
	- ~conda-linux-gcc-py310-cuda
	- ~conda-linux-gcc-py36-arm64
	- ~conda-linux-gcc-py37-arm64
	- ~conda-linux-gcc-py37-cpu-r41
	- ~conda-linux-gcc-py37-cuda
	- ~conda-linux-gcc-py38-arm64
	- ~conda-linux-gcc-py38-cpu
	- ~conda-linux-gcc-py38-cuda
	- ~conda-linux-gcc-py39-arm64
	- ~conda-linux-gcc-py39-cpu
	- ~conda-linux-gcc-py39-cuda
	- ~conda-win-vs2017-py37-r41

[asfimport]

Joris Van den Bossche / @jorisvandenbossche:
Issue resolved by pull request 12492
#12492