conda-forge missing Windows Packages

[WillAyd]

Got this error when trying to install the windows adbc packages in pandas CI:

   error    libmamba Could not solve for environment specs
      The following packages are incompatible
      ├─ adbc-driver-postgresql >=0.7.0  is not installable because it requires
      │  └─ adbc-driver-manager >=0.7.0,<1.0a0 , which does not exist (perhaps a missing channel);
      └─ adbc-driver-sqlite >=0.7.0  is not installable because it requires
         └─ adbc-driver-manager >=0.7.0,<1.0a0 , which does not exist (perhaps a missing channel).

[lidavidm]

We've punted on Windows on conda-forge so far because we couldn't resolve build issues, it may be time to fix that

[lidavidm]

Let's see how this goes: conda-forge/arrow-adbc-split-feedstock#17

[lidavidm]

Ah, so we need to trick CMake into using gcc for the go build and cl for everything else...

[paleolimbot]

This came up in OSGeo/gdal#11003 (comment) (GDAL wants to use the conda driver manager but can't on Windows because packaging is diabled:

https://github.com/conda-forge/arrow-adbc-split-feedstock/blob/6f2af5a9b0de9cbdf895ec0ab1e516c306abac67/recipe/meta.yaml#L31

[lidavidm]

I can see about trying this again...I think we "just" need to force Go-on-Windows to use gcc and not MSVC

[paleolimbot]

Or we could skip the Go drivers for the first attempt? The missing driver manager is the part that was causing some uncertainty/doubt as to whether ADBC worked on Windows.

[lidavidm]

Hmm, that should work.

[lidavidm]

Also see conda-forge/arrow-adbc-split-feedstock#17

[lidavidm]

I'm going to give the non-Go packages a shot. It turns out the m2w64-gcc package is now archived, so we can't rely on that either for the Go packages...

[lidavidm]

I've updated the feedstock to build the non-Go packages. I'm not sure how we can build the Go packages without GCC packaged for Windows in conda-forge.

[xhochy]

You should be able to use the mingw toolchain with Go on conda-forge on Windows (you might need to add the migrator to the new MinGW toolchain manually). If you have a failing open PR on the conda-forge side, I'm happy to look into it and see whether there are some tricks to get it working.

[lidavidm]

Ah, thanks for the info. I thought I saw that the MinGW toolchain was deprecated, if not then I know we just need a patch on our side (to force Go to use GCC and not MSVC via overriding CC)

[xhochy]

This migration will give you a new MinGW version: https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/migrations/r-base44_and_m2w64-ucrt.yaml

For the R Arrow package, we actually use clangto fuse MinGW and MSVC dependencies and I documented that approach over here: https://uwekorn.com/2020/06/14/r-arrow-for-conda-windows.html If you can avoid it, you're better off.