Bug#905206: Could you have a look at profnet test?

Hi Andreas, I'll try to take a look at the end of the week. Tanya. On Tue, Aug 27, 2019, 09:14 Andreas Tille wrote: > Hi Tatiana, > > since some time one of the profnet tests is failing with > >Program received signal SIGSEGV: Segmentation fault - invalid memory >reference. > > Do you

Bug#897605: How to deal with non-functional package in stretch? (Was: Bug#897605: profphd failure in stretch)

Hi All, This is fixed in version 1.0.42-2, and not present in version 1.0.42-1, which seems to be latest in stretch (both with tests). At patches dir: https://salsa.debian.org/med-team/profphd/blob/master/ debian/patches/2_remove_perlbrew_usage.patch - this disables perlbrew usage (this was

Bug#848903: metastudent: autopkgtests fail since 2016-12-05

Hi Andreas, I've managed to finish patch for metastudent (I've checked it several times and tried to make it to be compatible with old version of blast as well, although I didn't checked "studentC" part with legacy blast, only with latest version). Some details on how I checked: I've run

Bug#848903: Bug#848394: Bug#848903: metastudent: autopkgtests fail since 2016-12-05

Hi Andreas, This bug slightly differs from #848394.It relates to newer version of blast2 packages, for now it seems that it appeared because blast2 output has changed. For now it is clear that this error message in metastudent run log: Error: number of fastas and blasts dont match: 3 1 -

Bug#811876: disulfinder: FTBFS with GCC 6: no matching function for call to

Hi Gert, Thank you for notifying, I'll check. 2016-07-01 18:05 GMT+03:00 Gert Wollny : > Control: tags -1 pending > > Hi, > > I've added a patch in the svn to fix this bug and have also enabled > parallel builds. > > Tatiana, when you continue to work on the package please

Bug#827499: libtfbs-perl: Patches for misc packaging improvements

Hi Andreas, I've looked at `libtfbs-perl`, it seems that it already has testsuite similar to those produced by `autopkgtest-pkg-perl`. If you think it's better to use it instead of your testsuite in debian/tests/, I can change it (but for me it checks almost the same things - and if