Environment.yml fails to build development environment

[jvfe]

• Bug:

When I try conda env create --file environment.yml I get several installations failing:

Solving environment: failed

ResolvePackageNotFound: 
  - openssl==1.1.1h=haf1e3a3_0
  - certifi==2020.6.20=py37h2987424_2
  - libcxx==11.0.0=h439d374_0
  - setuptools==49.6.0=py37h2987424_2
  - xz==5.2.5=haf1e3a3_1
  - tk==8.6.10=hb0a8c7a_1
  - prodigal==2.6.3=h01d97ff_2
  - python==3.7.8=hc9dea61_1_cpython
  - zlib==1.2.11=h7795811_1010
  - sqlite==3.33.0=h960bd1c_1
  - libffi==3.2.1=hb1e8313_1007
  - readline==8.0=h0678c8f_2
  - ncurses==6.2=hb1e8313_2

• Specs:
  OS: Linux Debian 10 (Buster)
  conda version: 4.8.5

Apparently this is a common issue with conda (Unfortunately), here's an example.

I've found that removing the version hashes in the environment file (i.e. prodigal=2.6.3=h516909a_2 -> prodigal=2.6.3) fixes it and gets me an environment with the same software and versions. Though this is a very weird and not very practical solution, I can submit a pull request for it.

[jvfe]

Found out the problem: The build hashes are platform-specific, something I didn't know.

Generating the environment via conda env export -f environment.yml --no-builds should make it so that any platform can download it.