We have discovered that for later version of conda (4.6, at least), there is a conflict that occurs if the pinned file conflicts with an explicit historical version request. That conflict would result in a package/version pair added to the conda install command anyway, so there is no need for the pin at that point. So we're going to remove that pin from the file for the duration of the conda install command, and replace it once the install is complete.
We have discovered that for later version of conda (4.6, at least), there is a conflict that occurs if the
pinnedfile conflicts with an explicit historical version request. That conflict would result in a package/version pair added to the conda install command anyway, so there is no need for the pin at that point. So we're going to remove that pin from the file for the duration of the conda install command, and replace it once the install is complete.