Building more than one recipe fails

[jakirkham]

Seems conda-build-all has had a wrench thrown in it with the recent conda-build release (1.21.7). Not really sure what is causing it, but it seems to have some issues identifying where source should be extracted. See this comment for one example. Also here is another that springs up in this build. It would be nice to figure out why source extraction is getting messed up in these cases.

cc @jjhelmus @patricksnape @msarahan

[jakirkham]

Updated the title to be more accurate. In short, we seem to be losing the -all part of conda-build-all.

[jakirkham]

Just a reminder about this one, @pelson and @msarahan.

[pelson]

I can't reproduce this @jakirkham.

find my_recipes -name meta.yaml -exec echo {} \; -exec cat {} \;
my_recipes/recipe_a/meta.yaml
package:
  name: recipe_a
  version: 2.4

requirements:
  run:
    - python
  build:
    - python

my_recipes/recipe_b/meta.yaml
package:
  name: recipe_b
  version: 3.2

requirements:
  build:
    - recipe_a
    - numpy x.x
  run:
    - recipe_a
    - python
    - numpy x.x

And

CONDA_NPY=10 conda build-all my_recipes --matrix-conditions 'python >=2.7'
Using Anaconda Cloud api site https://api.anaconda.org
Fetching package metadata .........
Resolving distributions from 2 recipes... 
Computed that there are 9 distributions from the 2 recipes:
Resolved dependencies, will be built in the following order: 
    recipe_a-2.4-py27_0 (will be built: True)
    recipe_a-2.4-py34_0 (will be built: True)
    recipe_a-2.4-py35_0 (will be built: True)
    recipe_b-3.2-np110py27_0 (will be built: True)
    recipe_b-3.2-np111py27_0 (will be built: True)
    recipe_b-3.2-np110py34_0 (will be built: True)
    recipe_b-3.2-np111py34_0 (will be built: True)
    recipe_b-3.2-np110py35_0 (will be built: True)
    recipe_b-3.2-np111py35_0 (will be built: True)

> conda info
Current conda install:

             platform : osx-64
        conda version : 4.1.9
    conda-env version : 2.5.2
  conda-build version : 1.21.5
       python version : 2.7.12.final.0
     requests version : 2.9.1
     root environment : /Users/pelson/miniconda  (writable)
  default environment : /Users/pelson/miniconda/envs/_dev_conda_build_all
     envs directories : /Users/pelson/miniconda/envs
        package cache : /Users/pelson/miniconda/pkgs
         channel URLs : https://conda.anaconda.org/t/<TOKEN>/conda-forge/osx-64/
                        https://conda.anaconda.org/t/<TOKEN>/conda-forge/noarch/
                        https://repo.continuum.io/pkgs/free/osx-64/
                        https://repo.continuum.io/pkgs/free/noarch/
                        https://repo.continuum.io/pkgs/pro/osx-64/
                        https://repo.continuum.io/pkgs/pro/noarch/
          config file : /Users/pelson/.condarc
         offline mode : False
    is foreign system : False

[pelson]

I'm just looking into why conda info isn't reflecting my local imported versions... 😞

[pelson]

OK, that seems to have done it. I am able to reproduce the problem now. Additionally, all of the unit tests are passing 😞 .