Open greglandrum opened 4 weeks ago
Ok, that was easy. The first problematic build on linux is py312h7b4b7d0_1
That was done on July 24, so it was PR #158 :
I'm AFK until Wednesday but I'll take a look when I get back.
On Fri, Aug 16, 2024, 7:32 AM Greg Landrum @.***> wrote:
Ok, that was easy. The first problematic build on linux is py312h7b4b7d0_1 That was done on July 24, so it was PR #158 https://github.com/conda-forge/rdkit-feedstock/pull/158 :
— Reply to this email directly, view it on GitHub https://github.com/conda-forge/rdkit-feedstock/issues/170#issuecomment-2293338292, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHITGL3MYSVTPYSMIRVNATZRXPLDAVCNFSM6AAAAABMT4KKM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTGMZTQMRZGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Ah... I think I have this figured out: rdkit-targets.cmake
is part of the librdkit deliverable, and that doesn't have a python version associated with it. Currently there are things in that package that do have a python version dependency though
It doesn't feel right to have the python dependency in librdkit, so I'm going to see if this is something we can fix upstream
Should this approach for fixing this be removing anything python-related from librdkit as opposed to bringing in python-specific things? The base build itself should respect the python version; maybe we have to fix that instead?
Solution to issue cannot be found in the documentation.
Issue
Here's a demonstration of the problem:
Here's the first build of v2024.03.5:
That one looks ok
I will try and track down which build this started with in order to help figure out what happened.
Installed packages
Environment info