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

samtools openssl>1.1 #13920

Closed
wants to merge 3 commits into from
Closed

samtools openssl>1.1 #13920

wants to merge 3 commits into from

Conversation

@pb-cdunn
Copy link
Contributor

@pb-cdunn pb-cdunn commented Mar 5, 2019

See #13909

ℹ️
Bioconda has finished the GCC7 migration. If you are dealing with C/C++ or Python package it can be that you need to rebuild other dependent packages. Bioconda utils - update-pinning will assist you with that. If you have any questions please use issue 13578.


  • I have read the guidelines for bioconda recipes.
  • This PR adds a new recipe.
  • AFAIK, this recipe is directly relevant to the biological sciences (otherwise, please submit to the more general purpose conda-forge channel).
  • This PR updates an existing recipe.
  • This PR does something else (explain below).
@unode
Copy link
Member

@unode unode commented Mar 6, 2019

So < is ok but > isn't. The fun never ends! :)
I see cases of >= out there so maybe that works.

@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

Nope.

  File "/home/circleci/project/miniconda/lib/python3.6/site-packages/conda_build/render.py", line 162, in get_pin_from_build
    pin = utils.apply_pin_expressions(version.split()[0], **pin_cfg)
  File "/home/circleci/project/miniconda/lib/python3.6/site-packages/conda_build/utils.py", line 1208, in apply_pin_expressions
    parsed_version = VersionOrder(version).version[1:]
  File "/home/circleci/project/miniconda/lib/python3.6/site-packages/conda/models/version.py", line 163, in __new__
    raise CondaValueError(message + "invalid character(s).")
conda.exceptions.CondaValueError: Malformed version string '>=1.1.1': invalid character(s).
Exited with code 1

@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

https://github.com/conda/conda/blob/master/conda/models/version.py#L46

I think it needs a space. (I don't know why < works without a space.)

@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

Error: bad character '>=' in package version dependency 'openssl'
Perhaps you meant 'openssl >=1.1.1'

Ugh! There seems to be inconsistency between conda and conda-build lint.

@unode
Copy link
Member

@unode unode commented Mar 6, 2019

@bioconda/core any suggestions how to proceed here?

@dpryan79
Copy link
Contributor

@dpryan79 dpryan79 commented Mar 6, 2019

I'm going to start migrating packages to the new OpenSSL pinning this week. Samtools and related packages will be the first to be migrated.

@dpryan79 dpryan79 closed this Mar 6, 2019
@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

What about the problem with >=? Build wants a space; lint does not. I think there is a bug in the spec parser.

@dpryan79
Copy link
Contributor

@dpryan79 dpryan79 commented Mar 6, 2019

I wonder if conda-build is throwing an error due to the mismatch in meta.yaml and conda_build_config.yaml. The pinning in the yaml file will get ignored, I think, since there's a conda_build_config.yaml. The >=1.1.1 syntax is actually correct and is used in many recipes (e.g., deepTools).

@pb-cdunn
Copy link
Contributor Author

@pb-cdunn pb-cdunn commented Mar 6, 2019

% ls recipes/samtools/
0.1.19  1.1  1.6  build.sh  meta.yaml

Hmmm. < worked fine. > and >= both failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants