Hi Greg, unfortunately, the problem persist - well, it isn't a big one since if I explicitly say it should install 2018.09.2 it does that. Only when I just ask to install rdkit, it is still delivers version 2018.09.1 (when I ask the very same conda instance then to search me all available rdkit packages, it even finds 2018.09.2 ).
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 :-) Anyway, thanks for your reply. Markus On Fri, Feb 22, 2019 at 9:05 AM Greg Landrum <greg.land...@gmail.com> wrote: > Hi Markus, > > I can't reproduce that. Here's what I get when I create a new environment: > > (tmp) glandrum@otter:~/Code/rdkit_containers/docker$ conda install > conda-forge::rdkit > Collecting package metadata: done > Solving environment: done > > ## Package Plan ## > > environment location: /other_linux/home/glandrum/anaconda3/envs/tmp > > added / updated specs: > - conda-forge::rdkit > > > The following packages will be downloaded: > > package | build > ---------------------------|----------------- > cairo-1.16.0 | ha4e643d_1000 1.5 MB > conda-forge > > <snip> > > rdkit-2018.09.2 | py37h270f4b7_0 20.0 MB > conda-forge > > <snip> > > ------------------------------------------------------------ > Total: 32.6 MB > > The following NEW packages will be INSTALLED: > > blas pkgs/main/linux-64::blas-1.0-mkl > > boost conda-forge/linux-64::boost-1.68.0-py37h8619c78_1001 > > boost-cpp conda-forge/linux-64::boost-cpp-1.68.0-h11c811c_1000 > <snip> > rdkit conda-forge/linux-64::rdkit-2018.09.2-py37h270f4b7_0 > > <snip> > > Maybe it was connected to the new version just having appeared? Do you > still have the same problem? > > -greg > > > > > > On Fri, Feb 22, 2019 at 12:43 AM Markus Sitzmann < > markus.sitzm...@gmail.com> wrote: > >> Hi Greg, >> >> I just saw it is available in the conda-forge channel (with a time stamp >> of 2 hours + a few minutes), however, if I install it from there (in a >> fresh container) I receive 2018_09_1 - only when I explicitly force version >> 2018_09_2 I receive it (and at a very fast glance it is running). >> >> But why do I have to request version _02 explicitly (right at the moment) >> ... this is one of the few things I never will get with conda? >> >> Markus >> >> >> On Thu, Feb 21, 2019 at 5:32 PM Greg Landrum <greg.land...@gmail.com> >> wrote: >> >>> Dear all, >>> >>> I normally don't announce the patch releases, but there are a couple of >>> changes with the conda builds, so I figured I should probably mention it. >>> :-) >>> >>> This time I did builds for: >>> Python 3.7: Mac, Linux, Windows >>> Python 3.6: Mac, Linux, Windows >>> Python 2.7: Mac, Linux >>> >>> The boost and numpy dependencies have also been changed. >>> >>> The conda-forge channel should be updated in the near future as well. >>> >>> The release notes and source download are here: >>> https://github.com/rdkit/rdkit/releases/tag/Release_2018_09_2 >>> >>> Hopefully this all works smoothly, but I'm not 100% optimistic about >>> that; please let me know if you encounter any problems with the new builds! >>> -greg >>> >>> _______________________________________________ >>> 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
