Let's see how this goes.

[mingwandroid]

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

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

I do have some suggestions for making it better though...

For recipe:

• Using toolchain directly in this manner is deprecated. Consider using the compilers outlined here.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [162]

For recipe:

• Using toolchain directly in this manner is deprecated. Consider using the compilers outlined here.

[mingwandroid]

Can anyone at @conda-forge/r help figure this out?

  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/match_spec.py", line 43, in __call__
    return super(MatchSpecType, cls).__call__(**parsed)
  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/match_spec.py", line 180, in __init__
    self._match_components = self._build_components(**kwargs)
  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/match_spec.py", line 367, in _build_components
    return frozendict(_make(key, value) for key, value in iteritems(kwargs))
  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/match_spec.py", line 367, in <genexpr>
    return frozendict(_make(key, value) for key, value in iteritems(kwargs))
  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/match_spec.py", line 361, in _make
    matcher = _implementors[field_name](value)
  File "/Users/travis/miniconda3/lib/python3.7/site-packages/conda/models/version.py", line 439, in __new__
    raise InvalidVersionSpecError(spec)
conda.exceptions.InvalidVersionSpecError: Invalid version spec: $

I cannot reproduce it locally using the following command line (and also saw no weird specs with conda-render):

conda-build -m ./.ci_support/osx_.yaml -c conda-forge recipe

[bgruening]

@mingwandroid this is the typo. Also there is a meta.yaml.orig included in this PR.

[mingwandroid]

Urgh! How did I not spot that (and why is it not happening locally .. questions for myself)? OK. thanks.

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

I do have some suggestions for making it better though...

For recipe:

• Using toolchain directly in this manner is deprecated. Consider using the compilers outlined here.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[mingwandroid]

@isuruf, msys2 packages use an epoch package / mechanism to manage pinning. It's different than our usual way but works just fine! I'd rather not pin beyond that personally since then you have two mechanisms in play.

[isuruf]

msys2 packages use an epoch package / mechanism to manage pinning.

I have some questions about this,

1. Shouldn't this package depend on msys2-conda-epoch then?
2. I looked at the requirements of some msys2 packages and they depend on msys2-conda-epoch >=20160418 and not on something like msys2-conda-epoch 20160418. If msys2-conda-epoch is updated, how is it guaranteed that this package will not use a package from a new epoch?

[mingwandroid]

Given the two points yes. Depend on the exact epoch version here, good point. I may rebuild them later for exact pinning too.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

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

I do have some suggestions for making it better though...

For recipe:

• Using toolchain directly in this manner is deprecated. Consider using the compilers outlined here.

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

[mingwandroid]

Thanks for taking this further.

[mariusvniekerk]

Restarted travis which seemed to die for no good reason.

[scopatz]

Thanks @mingwandroid!

[mingwandroid]

Thanks all!

[CJ-Wright]

Woooooo awesome! Thank you everyone for your hard work and perseverance!!