Hi Hannes,
I'm writing you on behalf of the Debian Med team which tries to package
software which is relevant in medicine and biology for official Debian.
If you want to get an overview about the biological software we have
included into Debian you can get an overview here:
http://blends.debi
Hello,
I was wondering what one should do when upstream's source release tarball is
missing important components.
HTSeq's release tarballs after my initial release stopped including the .pyx
and .i source files and only included the C/CXX code generated by SWIG and
Cython.
I also discovered H
Hi Diane,
On Tue, Apr 08, 2014 at 11:22:56AM -0700, Diane Trout wrote:
> Hello,
>
> I was wondering what one should do when upstream's source release tarball is
> missing important components.
>
> HTSeq's release tarballs after my initial release stopped including the .pyx
> and .i source file
> Without beeing able to evaluate your chances to convince upstream (which
> would my *personal* prefered choice) I think you shoudl decide what from
> your point of view is the solution that might create the least trouble
> with an acceptable result for the user. We have some
> debian/get-orig-s
Hi Thorsten
No, libmatrixExp.so isn't used for anything here. Is there a way to
remove that in the debian package or do I need to do it in the original
phyutilty and push a new version?
Take care,
Stephen
On Tue, Apr 01, 2014 at 02:55:44PM +0200, Thorsten Alteholz wrote:
> Hi Stephen,
>
> lintian
Hi Stephen,
On Tue, Apr 08, 2014 at 10:19:07PM -0400, Stephen Smith wrote:
> Hi Thorsten
> No, libmatrixExp.so isn't used for anything here. Is there a way to
> remove that in the debian package or do I need to do it in the original
> phyutilty and push a new version?
There is the option to use "
6 matches
Mail list logo
