Hi Greg, in the meantime, I found a solution: I added a "conda update" as final step when I build my base python/conda container. The RDKit container is build on top of that and now it finds RDKit 2018.09.2 without telling conda the version number explicitly. Why this worked beforehand without this step and why it is necessary although I start building the containers basically from scratch and the newest version, I still don't know.
Best, Markus On Sat, Feb 23, 2019 at 12:29 AM Dimitri Maziuk via Rdkit-discuss < rdkit-discuss@lists.sourceforge.net> wrote: > On 2/22/19 5:01 PM, Markus Sitzmann wrote: > > > It is odd, but one thing I learned from using conda is, sometimes it > helps > > to ignore problems and wait for a bit and they might go away ... well, I > > have similar experiences with maven :-) ... but most likely I do > something > > stupid which I don't see right now :-) > > Simple test is to make a clean one and install only rdkit and nothing > else and see what happens. It's pretty common for packagers to do > something-that-may-or-may-not-be-stupid and have a dependency on an > specific version of some other package that depends on a specific > version of another package that depends on... turtles all the way down. > > -- > Dimitri Maziuk > Programmer/sysadmin > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > _______________________________________________ > Rdkit-discuss mailing list > Rdkit-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rdkit-discuss >
_______________________________________________ Rdkit-discuss mailing list Rdkit-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
