Add pyvcf to conda-forge#6303
Conversation
|
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 ( Here's what I've got... For recipes/pyvcf:
|
|
@conda-forge/bioconda-recipes, please advise how to proceed with pyvcf package. The bioconda community prefers for the package to stay in bioconda, and I need to package |
As agreed to in the bioconda/bioconda-recipes#9979 PR I added everyone in that thread as a `recipe-maintainer`. The order is alphabetical.
|
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 ( |
|
@bgruening, this is ready to merge. |
| FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR | ||
| COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER | ||
| IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN | ||
| CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
There was a problem hiding this comment.
Please, remove this file. This is not necessary since the LICENSE file is already in the repository and being package
There was a problem hiding this comment.
It is not. Please see my initial post with a reference to the PR for changing the MANIFEST.in file.
Until then the license file should stay here.
|
Thanks! |
4 participants
License file was added to the feedstock and an upstream PR was created to fix this issue.
cf: jamescasbon/PyVCF#295