Repin conda-build to 1

[jakirkham]

Re-adds the conda-build version 1 pinning. Thus reverting commit ( df4c69e ).

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

Sorry had to repin this until we actually start using the fixed upload script, @jjhelmus.

[DPeterK]

@jakirkham perhaps pinning to conda-build <v1.21.12 would be a good idea to avoid the failures that we are seeing in conda-forge/basemap-feedstock#7, for example?

[jakirkham]

My recommendation would be to comment the conda inspect line in that recipe for now.

Fiddling with this pinning further is only going to prevent us from spending time on the required tasks to get to conda-build 2, which I believe is where we all want to go.

Literally the only reason I had to add this back is we haven't merged PR ( conda-forge/conda-smithy#301 ) and made a conda-smithy release. Once that happens conda-smithy is unblocked for conda-build 2. The only other question we need to figure out is what is going on with the 64 packages whose prefix status is unknown ( conda-forge/conda-forge.github.io#171 (comment) ).

Edit: Added the 26 packages who are known, but whose prefix info was undetermined, to the 38 packages which are simply unknown (we know they exist, but not their names ATM).

[patricksnape]

Agree - definitely want to get to conda-build 2 asap to avoid having to end up essentially forking conda-build!