Skip to content

Update imports to htslib/samtools/bcftools 1.11#962

Merged
jmarshall merged 5 commits intopysam-developers:masterfrom
jmarshall:import-1.11
Jan 12, 2021
Merged

Update imports to htslib/samtools/bcftools 1.11#962
jmarshall merged 5 commits intopysam-developers:masterfrom
jmarshall:import-1.11

Conversation

@jmarshall
Copy link
Copy Markdown
Member

@jmarshall jmarshall commented Oct 20, 2020

Import htslib, samtools, and bcftools 1.11:

jmarshall and others added 4 commits October 19, 2020 17:08
Avoid exercising samtools/htslib#1142 (present in the HTSlib-1.11 release),
which leads to test failures due to the way we test using iterators.
This is not what these pysam test cases are trying to test, so alter the
input data file to avoid the issue.
For each package:

rm -rf htslib;   python3 devtools/import.py htslib   .../htslib-1.11
rm -rf samtools; python3 devtools/import.py samtools .../samtools-1.11
rm -rf bcftools; python3 devtools/import.py bcftools .../bcftools-1.11

(Don't bother adding {sam,bcf}tools/htslib-1.11/{LICENSE,README}.)

Add new ampliconclip and ampliconstats commands to pysam/samtools.py.
Apply PR samtools/htslib#1150. The hfile irods plugin depends on
a constructed symbol name which was no longer being used.
Apply PR samtools/htslib#1184. On macOS, plugins pulling in libhts.dylib
conflicts with a statically linked libhts.a from the main executable.
@jmarshall
Copy link
Copy Markdown
Member Author

Season's greetings to all… @AndreasHeger @kevinjacobs-progenity @bioinformed — does anyone want to review this, or shall I just merge it? The update to 1.11 was straightforward (e.g., compared to the 1.10 one).

@kevinjacobs-progenity
Copy link
Copy Markdown
Member

Apologies for the delay. This looks sensible and uncontroversial. My quick tests passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants