Bug#881170: Private HTSlib internals packaged in libhts-dev

2017-11-10 Thread Mattia Rizzolo
Control: clone -1 -2 -3 Control: retitle -1 htslib: please do not package cram/*.h headers Control: severity -1 important Control: summary -1 cram headers are considered private and other projects shouldn't be interested in them Control: retitle -2 htslib: please revert pkg-config change in fix_p

Bug#881170: Private HTSlib internals packaged in libhts-dev

2017-11-09 Thread John Marshall
If you want to demonstrate your acknowledgement of this bug report, you (Debian maintainers) might consider setting its severity to an appropriate level. Judging by #879886, that level would be SERIOUS.

Bug#881170: Private HTSlib internals packaged in libhts-dev

2017-11-08 Thread Trout, Diane E.
Hi, I wanted to acknowledge that all your issues need to be addressed and resolved. I filed an issue with SeqLib & htslib to ask to work out a public cram api. Personally I think option C would be best for a short term fix and option B for the long term fix. SeqLib issue: https://github.com/wal

Bug#881170: Private HTSlib internals packaged in libhts-dev

2017-11-08 Thread John Marshall
> 3. The htslib*.mk makefile fragments should not be packaged Looking at debian/libhts-dev.links which also appears to have been introduced for bcftools's benefit, it is clear that the whole /usr/lib/htslib directory is for bcftools's benefit and should not be packaged. If that directory layout