Hello Andrius, Thank you for the upload! :-) Quick question. Would it be worth the effort backporting, or is that usually based on factors like demand and interest from users, developers, etc? Additionally, I've managed to fix one of the few tests which I was initially unable to include within the unit test. It takes a bit of effort to run valgrind and to try figure out where SIGSEGV was tripped. My aim is to have maximum functionality testing coverage with this very soon. This package was hugely beneficial in learning. I've been in touch with the upstream developer and have learned about their periodic releases, etc... which means that I can focus on keeping upstream happy by incorporating future releases within the package. > I am amazed by your speed and quality - two packages in twenty days! I > hope to see you becoming independent Debian developer soon. Sadly, I'm right before entering university so I'm still young and travelling for key signing / etc is not a viable option yet. I won't be surprised if I was the youngest in the team :-) Many thanks to you and Andreas for your efforts, Shayan Doust On 20/07/2019 23:02, Andrius Merkys wrote: > Hi Shayan, > > I have uploaded mmseqs2 as I deemed the packaging complete. Thanks a lot > for working on it. > > I am amazed by your speed and quality - two packages in twenty days! I > hope to see you becoming independent Debian developer soon. > > Best wishes, > Andrius > > On Sat, 20 Jul 2019, 21:32 Shayan Doust, <hello@shayandoust.me > <mailto:hello@shayandoust.me>> wrote: > > Hello Andreas, > > I just fixed the issues in copyright. Lintian no longer reports any of > those issues to me. > > Best Regards, > Shayan Doust > > On 20/07/2019 18:23, Andreas Tille wrote: > > Hello Shayan, > > > > On Sat, Jul 20, 2019 at 05:59:04PM +0100, Shayan Doust wrote: > >> Hello Andreas, > >> > >> Now with the newest version of Lintian which was pushed a week ago, I > >> still do not see any of the output you are getting. In fact, I am > seeing > >> this: > >> > >> > >> I: mmseqs2: spelling-error-in-binary usr/bin/mmseqs alteratives > alternatives > >> I: mmseqs2: spelling-error-in-binary usr/bin/mmseqs Dont Don't > >> I: mmseqs2: spelling-error-in-binary usr/bin/mmseqs seperated > separated > >> I: mmseqs2: spelling-error-in-binary ... use > --no-tag-display-limit to > >> see all (or pipe to a file/program) > >> I: mmseqs2: description-synopsis-might-not-be-phrased-properly "ultra > >> fast and sensitive protein search and clustering." > >> I: mmseqs2: possible-documentation-but-no-doc-base-registration > >> > >> This is what I have been working with the whole time, so my judgement > >> was that it was fairly complete. > >> > >> Right now I just ran lintian as is, as before I was specifying the > >> specific deb package using a manual invoke of the command, and > now I get > >> what you are getting. So I guess I was doing it wrong the whole > time :( > > > > I actually use it with the changes file. > > > >> Lesson learned, thanks! > > > > That's the whole point of the MoM project. ;-) > > > > Kind regards > > > > Andreas. > > >
Attachment:
signature.asc
Description: OpenPGP digital signature