Creating conda env for older versions of fenics

installation
1

Hi

I would like to ask if it is possible to build a conda env for fenics using an older version of fenics e.g. 2016.1.0. I have some code that I inherited and my pre-existing pipeline works pretty well for 2016.1.0, so if I could build that conda env on my local and work from there, that would be really helpful!

Thanks!

2

You can specify the version of the package with conda. To create the environment and install fenics 2016.1.0 you can use the following command:

conda create -n fenics2016 -c conda-forge fenics=2016.1.0
3

Hi! So sorry for the delay. I seem to be having issues with such an installation:

Collecting package metadata (repodata.json): done
Solving environment: failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Package mpich conflicts for:
fenics=2016.1.0 -> mpich
Package six conflicts for:
fenics=2016.1.0 -> six
Package python conflicts for:
fenics=2016.1.0 -> python[version='2.7.*|3.4.*|3.5.*']
Package petsc conflicts for:
fenics=2016.1.0 -> petsc=3.7
Package petsc4py conflicts for:
fenics=2016.1.0 -> petsc4py=3.7
Package zlib conflicts for:
fenics=2016.1.0 -> zlib=1.2
Package ply conflicts for:
fenics=2016.1.0 -> ply
Package boost conflicts for:
fenics=2016.1.0 -> boost=1.61
Package gcc conflicts for:
fenics=2016.1.0 -> gcc
Package eigen conflicts for:
fenics=2016.1.0 -> eigen
Package swig conflicts for:
fenics=2016.1.0 -> swig[version='>=3']
Package cmake conflicts for:
fenics=2016.1.0 -> cmake
Package sympy conflicts for:
fenics=2016.1.0 -> sympy
Package ptscotch conflicts for:
fenics=2016.1.0 -> ptscotch
Package numpy conflicts for:
fenics=2016.1.0 -> numpy
Package slepc4py conflicts for:
fenics=2016.1.0 -> slepc4py=3.7
Package pkg-config conflicts for:
fenics=2016.1.0 -> pkg-config
Package slepc conflicts for:
fenics=2016.1.0 -> slepc=3.7

I suspect this is an issue with conda and ill look it up and post back when I figure it out.

4

You also have to specify the version of the other packages you are working with, e.g.
conda create -n fenics2016 -c conda-forge fenics=2016.1.0 python=3.5
Had the same problem with FEniCS 2017 and had to try out versions of every package I wanted to use. Hope that helps.