Loosen pyarrow pin

[jdblischak]

Background:

• Currently getting aws-sdk-solver errors in update TileDB-VCF to 0.29.0 #111, likely due to pyarrow 11 no longer being built against the latest conda-forge pins
• TileDB-VCF was migrated to use the arrow C data interface in Migrate to Arrow C data interface TileDB-VCF#653
• tiledb-feedstock now installs aws-sdk-cpp from conda-forge (Install the AWS SDK from conda-forge. conda-forge/tiledb-feedstock#241)
• We recently dropped the py37 builds in Drop py37 linux-64 build to fix TileDB-VCF 0.28.1 build #112

[jdblischak]

At least we're making progress. No more aws-sdk-cpp solver errors. Now they're all failing with the libgoogle-cloud solver errors!

[jdblischak]

I'm working on fixing the solver errors upstream in tiledb-feedstock, eg conda-forge/tiledb-feedstock#246

[jdblischak]

I just merged conda-forge/tiledb-feedstock#246. It builds tiledb 2.19 against google-cloud-cpp 2.21. Once the binaries are uploaded, I'll restart the CI here to see if that helps the solver

[jdblischak]

So I built libtiledb 2.19 against libgoogle-cloud 2.21, but the conda solver is still failing because it still hasn't been built against the latest abseil:

    Could not solve for environment specs
    The following packages are incompatible
    ├─ libabseil ==20240116.1 cxx17_h59595ed_2 is requested and can be installed;
    ├─ libcurl ==8.5.0 hca28451_0 is requested and can be installed;
    ├─ libgoogle-cloud ==2.21.0 h72bcb37_2 is requested and can be installed;
    ├─ libtiledbvcf 0.28.1**  is installable with the potential options
    │  ├─ libtiledbvcf 0.28.1 would require
    │  │  └─ tiledb 2.19.*  with the potential options
    │  │     ├─ tiledb [2.19.0|2.19.1] would require
    │  │     │  └─ libcurl >=7.88.1,<8.0a0 , which conflicts with any installable versions previously reported;
    │  │     ├─ tiledb [2.19.0|2.19.1] would require
    │  │     │  └─ openssl >=1.1.1w,<1.1.2a , which can be installed;
    │  │     ├─ tiledb [2.19.0|2.19.1] would require
    │  │     │  └─ libgoogle-cloud >=2.12.0,<2.13.0a0 , which conflicts with any installable versions previously reported;
    │  │     └─ tiledb 2.19.1 would require
    │  │        └─ libabseil >=20230802.1,<20230803.0a0 , which conflicts with any installable versions previously reported;
    │  └─ libtiledbvcf 0.28.1 conflicts with any installable versions previously reported;
    └─ openssl ==3.2.1 hd590300_0 is not installable because it conflicts with any installable versions previously reported.

I'm hoping a bot will auto-open the libabseil migration PR (just like the one it sent to update 2.20 in main, conda-forge/tiledb-feedstock#245). But if that doesn't happen soon, I'll try to manually perform the migration.

[ihnorton]

Migration here: conda-forge/tiledb-feedstock#250

[jdblischak]

Superseded by 7aede11 in #111, merged as 5f11910