Re: [MoM] kmer-tools status update
Hi, Andreas,
On الإثنين 25 أيار 2015 00:13, Andreas Tille wrote:
Hi Afif,
On Sun, May 24, 2015 at 11:12:00PM -0700, Afif Elghraoui wrote:
Hi, Andreas,
I tried to go ahead with packaging shared libraries, but it looks like I
have to read three to five more manuals before I can proceed and know what
I'm doing.
Hmmm, I can not parse this as a specific question to me - just ask if I
can help somehow. Regarding packaging shared libraries I personally
recommend using d-shlibs. There are some examples in our repositories
for instance bambamc, bamtools or snp-sites (just a random pick from my
poor mind with no specific order or preference)
Thanks. These are good enough pointers for me to start trying something.
I was mostly confused by having to mind the symbols and sonames. It
looks like I should just build the .so files and take care of their
placement in multiarch folders...at least, as a first step.
[...]
Moreover, the spacing is
the same for the other two generated packages and I don't get this warning
for them. Otherwise, the package is lintian clean.
See my latest push. :-)
Oh... I see. :facepalm:
On the other hand when I'm using the latest lintian (from unstable) I get
some more things as info, which might be worth fixing
Ok, I just discovered the -I flag for lintian and see what you saw.
I: kmer-tools source: duplicate-short-description meryl libmeryl-dev
Done.
I: kmer-tools source: quilt-patch-missing-description kazlib.patch
I: kmer-tools source: quilt-patch-missing-description remove-kazlib.patch
Done.
You might like to override
I: kmer-tools source: debian-watch-file-is-missing
with a comment to express the fact that there is no chance to write such
a file.
Lintian info recommended creating a dummy watch file with comments
explaining the situation. I did that and hope it's ok with you (more
details in my commit message).
I decide from time to time whether I fix things like
I: meryl: spelling-error-in-binary usr/bin/existDB endianess endianness
If there is a responsive upstream I send a patch.
Fixing this involves renaming two of the source files. Is there an way
to do that with quilt without essentially deleting it and creating it
with a different name? I feel like upstream will laugh at me if I send
in a patch to correct such a minor thing.
For things like
I: meryl: hardening-no-fortify-functions usr/bin/existDB
I never found a solution myself and consider this false positives. Feel
free to leave these untouched.
I was able to resolve this. The dh_make debian/rules template had some
extremely useful information in this regard.
Please add the DEP3 headers to the patches since this is helpful for
other team members.
Done (and sorry about that; I totally forgot about the quilt header thing).
Thanks and regards
Afif
--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name
Reply to: