Pin winpty to a working mingw build

[ccordoba12]

No description provided.

[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.

[ccordoba12]

@conda-forge-admin, please rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I rerendered the feedstock and it seems to be already up-to-date.

[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.

[ccordoba12]

@jakirkham, @ocefpaf, how can we pin a package to a particular build number? We need winpty 0.4.3 build 4, but (for some reason) conda build is pulling winpty 0.4.3 build 2.

[ocefpaf]

Looks like a typical bad solution from the coda solver :-/
I guess that 0.4.3 build 2 has less dependencies, has unpinned deps, or pinned to easy to solve deps... Anyway, since they are same version but you want a higher build number I guess that the best thing to do is to move the lower build number to the "broken" label.

[ccordoba12]

Thanks @ocefpaf, that's what we needed!