environment.yml ResolvePackageNotFound

[sousocheat]

Windows 10 64bit

Using Anaconda API: https://api.anaconda.org
Fetching package metadata .................

ResolvePackageNotFound:
  - freetype 2.5.5 2

[Aki1987]

ResolvePackageNotFound describe all packages not installed yet. That you need to move ResolvePackageNotFound to below pip: sentence looks like:

Best, Thu

[sousocheat]

Thank you. It worked.

[EniasCailliau]

The whole concept of using yml files is to simplify environment installation on other computers. Why does the conda env export command generate a file that only works on the originating host?

[Yp17ra]

Ubuntu
Using Anaconda API: https://api.anaconda.org
Solving environment: failed

ResolvePackageNotFound:

• opencv3==3.0.0=py35_0
• tbb==4.3_20141023=0

Though I've placed these two requirements under pip section in .yml file im getting the same error. Can you help me out?

[HS-YN]

It seems that menpo tbb is for osx-64 only, and jlaura::opencv3=3.0.0 is not available for some reason. By slightly omitting the detail in environment.yml:

• tbb==4.3_20141023=0 to tbb
• jlaura::opencv3==3.0.0=py35_0 to opencv3

The initial error was resolved, but I faced another error like this:

UnsatisfiableError: The following specifications were found to be in conflict:

• libtiff==4.0.6=3 -> jpeg=9
• qt==5.6.2=2 -> jpeg=8

There will be more elaborate ways to handle this error, but I took a simple detour like this:

• libtiff==4.0.6=3 to libtiff
• qt==5.6.2=2 to qt

[vinisalazar]

The whole concept of using yml files is to simplify environment installation on other computers. Why does the conda env export command generate a file that only works on the originating host?

This is still haunting me.

[Vinod-Koli]

@Aki1987 that worked!! thank you.

ResolvePackageNotFound describe all packages not installed yet. That you need to move ResolvePackageNotFound to below pip: sentence looks like:

Best, Thu

[bitic]

I had the same problem. It is frustrating, because precisely the point of anaconda is to manage this automatically.

I didn't have any pip packages in my environment.yml, all were packages installed by conda. How come conda cannot reproduce and environment I created with conda?

The solution I found was to remove all the packages that were installed as dependencies and just leave the packages I myself had installed with conda install packagename. Still, basemap was failing. I removed basemap and it worked.

Then I installed basemap with conda install basemap.

Finally, I did a _conda env export, which again was full of dependencies (not only the primary I want). I copied the line corresponding to basemap and I manually edited my environment.yml adding this line there. So, now in environment.yml I only have tha packages I would have installed with conda install when I first created the environment.

This way, except basemap, the package I import in my python scripts will have the same version they had in the environment. Then, the dependencies are those that conda choses.

[bitic]

Later I had the same problem importing another environment from an environment.yml.

I followed a better procedure than in my previous comment.

1. I removed from environment.yml the 4 packages that were failing (could not be installed by conda).
2. I installed the environment. Now it worked.
3. From those 4 packages that failed, only one was "primary" (a package I import on my scripts), so I installed it manually with conda install. This installed this package and the other 3 that were failing, but with new versions.
4. I exported the new environment to environment.yml.

Now the environment is almost identical, except for 4 packages whose version changed.

[irockafe]

Just here to commiserate - environment.yml from an Ubuntu project wouldn't install on on OS X.

Added a --no-build flag to my export reduced me from loads of packages not found to just 4. I removed those and everything was basically fine.[credit]