Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add recipe for OCW #1606

Closed
wants to merge 1 commit into from
Closed

Add recipe for OCW #1606

wants to merge 1 commit into from

Conversation

jarifibrahim
Copy link
Member

No description provided.

@conda-forge-linter
Copy link

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 (recipes/ocw) and found it was in an excellent condition.

@jarifibrahim
Copy link
Member Author

@agoodm Can you please help me fix the failing build?

@lewismc
Copy link
Member

lewismc commented Sep 16, 2016

Nice work @jarifibrahim

conda.resolve.NoPackagesFound: Packages/dependencies missing in current osx-64 channels: 

  - ocw 1.2.0 py27_0 -> esgf-pyclient >=0.1.6

  - ocw 1.2.0 py27_0 -> myproxyclient >=1.4.3

  - ocw 1.2.0 py27_0 -> podaacpy >=1.0.2

  - podaacpy >=1.0.2

  - myproxyclient >=1.4.3

  - esgf-pyclient >=0.1.6

@agoodm
Copy link
Member

agoodm commented Sep 16, 2016

@jarifibrahim Thank you for getting this done so soon!
The cause of these error messages is that some of the dependencies are not available on the main anaconda or conda-forge channels. This means that we will need to make PRs to upload recipes for esgf-pyclient, myproxyclient, and podaacpy. I think @lewismc might want to handle the latter, but I can go ahead and do the other two.

@jarifibrahim
Copy link
Member Author

jarifibrahim commented Sep 16, 2016

@agoodm I see these packages on anaconda
esgf-pyclient - https://anaconda.org/birdhouse/esgf-pyclient
myproxyclient - https://anaconda.org/birdhouse/myproxyclient
Both the packages are available only for python 2

The following are from the Travis build log.

File "/Users/travis/miniconda/lib/python3.5/site-packages/conda/resolve.py", line 454, in verify_specs
    raise NoPackagesFound(bad_deps)
conda.resolve.NoPackagesFound: Packages/dependencies missing in current osx-64 channels: 
  - ocw 1.2.0 py27_0 -> esgf-pyclient >=0.1.6

In the above snippet python 3 is used for building conda recipe.

Fetching package metadata .........
Resolving distributions from 1 recipes... 
Computed that there are 3 distributions from the 1 recipes:
Resolved dependencies, will be built in the following order: 
    ocw-1.2.0-py27_0 (will be built: True)
    ocw-1.2.0-py34_0 (will be built: True)
    ocw-1.2.0-py35_0 (will be built: True)

Is there any way to build ocw conda package only for python 2? The ocw is not compatible with python 3 at this moment.

@agoodm
Copy link
Member

agoodm commented Sep 16, 2016

@jarifibrahim I was referring to the main anaconda channel and the conda-forge channel. Those packages are available on my own channel as well, but I believe they need to at least be on the conda-forge channel in order to not cause a CI build failure. As for the python3 question I am not exactly sure at the moment myself. Someone in the conda-forge org might know.

@jarifibrahim
Copy link
Member Author

@agoodm Right. That means we'll have to add esgf-pyclient and myproxyclient to conda-forge as well. I'll push new PRs today. Thanks!

Copy link
Member

@agoodm agoodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this necessary? I don't recall seeing other recipe feedstocks containing standalone LICENSE files.

Copy link
Member

@agoodm agoodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarifibrahim Please read the attached review.

Thanks,m

# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarifibrahim You'll need to get rid of all comments in the final staged recipe, including the license headers. You'll need to do the same for the other PRs you have made if you haven't done so already.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.


source:
git_url: https://github.com/apache/climate.git

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be changed to point to PyPi, with md5 hash and all. Additionally leaving it like this will get the latest code from our master ocw branch rather than a stable release which is not what we want.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right.

# under the License.

{% set name = "ocw" %}
{% set version = "1.2.0" %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be version 1.1.0, as 1.2.0 is not released yet.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.


about:
home: http://climate.apache.org/
license: Apache License
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be "Apache License, Version 2.0"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@conda-forge-linter
Copy link

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 (recipes/ocw) and found some lint.

Here's what I've got...

For recipes/ocw:

  • Failed to even lint the recipe (might be a conda-smithy bug) 😢

@conda-forge-linter
Copy link

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 (recipes/ocw) and found it was in an excellent condition.


about:
home: http://climate.apache.org/
license: Apache License, Version 2.0
Copy link
Member

@jakirkham jakirkham Sep 17, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we at conda-forge prefer the shortened license form. So Apache 2.0 or similar.

Copy link
Member

@jakirkham jakirkham Sep 17, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please ask upstream to add the license file to MANIFEST.in. Also please add an xref in a comment in the recipe so we can track this and update accordingly once the license is packaged in the sdist. We are trying to ensure license files are included in the built packages.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also can optionally add license_family: Apache.


extra:
recipe-maintainers:
- agoodm
Copy link
Member

@jakirkham jakirkham Sep 17, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you ok with being a maintainer of climate at conda-forge, @agoodm?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jakirkham Yes I am.

build:
skip: True # [py3k]
number: 0
script: python setup.py install
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the arguments --single-version-externally-managed --record record.txt. These are required when using setuptools to make sure this gets packaged correctly.


about:
home: http://climate.apache.org/
license: Apache License, Version 2.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also can optionally add license_family: Apache.

Copy link
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together, @jarifibrahim.

A few comments to get this cleaned up. Noting some dependencies are not here yet, but I see they are being worked on other PRs. We can come back to this once they are packaged.

@jakirkham
Copy link
Member

Are you taking this over somewhere else @agoodm ? Should this stay open?

@agoodm
Copy link
Member

agoodm commented Oct 19, 2016

@jakirkham go ahead and close this. Since this PR is rather cluttered I think it would be best for me to start from a new one.

@agoodm agoodm mentioned this pull request Oct 19, 2016
@jakirkham
Copy link
Member

Continued in PR ( #1784 ).

@jakirkham jakirkham closed this Oct 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants