Package: mindthegap / 2.3.0-5

Metadata

Package Version Patches format
mindthegap 2.3.0-5 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
use_debian_packaged_gatb core.patch | (download)

CMakeLists.txt | 14 8 + 6 - 0 !
1 file changed, 8 insertions(+), 6 deletions(-)

 modify cmakelists.txt
 ...to allow for CMake to use system-wide libraries instead of a localised binary within the same dir tree.
remove_unnecessary_installs.patch | (download)

CMakeLists.txt | 10 5 + 5 - 0 !
1 file changed, 5 insertions(+), 5 deletions(-)

 prevent cmake from installing some static files
 These static files can easily be retrieved from the upstream root directory. Having CMake attempt to install repetitive files would cause lintian to complain and an overall bad package
modify_tests_for_autopkgtest.patch | (download)

test/simple_full_test.sh | 21 4 + 17 - 0 !
test/simple_test.sh | 19 3 + 16 - 0 !
2 files changed, 7 insertions(+), 33 deletions(-)

 fix upstream pre-existing test scripts
 This will ensure that autopkgtest can invoke these scripts. They need to be modified to remove any mindthegap binary checks that the upstream author has put in place as well as ensuring the script invokes the global MindTheGap command
2to3.patch | (download)

test/scripts/generate_read.py | 34 17 + 17 - 0 !
test/scripts/make_deletions.py | 42 21 + 21 - 0 !
test/scripts/make_snp_deletions.py | 4 2 + 2 - 0 !
test/vde.py | 10 5 + 5 - 0 !
4 files changed, 45 insertions(+), 45 deletions(-)

 automatic port to python3 via
   2to3 --write --nobackups *.py


fix use as function.patch | (download)

src/FindBreakpoints.hpp | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix expression that cannot be used as a function
 Starting with g++ 14, the build fails with:
 .
    /<<PKGBUILDDIR>>/src/FindBreakpoints.hpp:786:38: error: expression cannot be used as a function
      786 |     return this->m_solid_stretch_size();
          |            ~~~~~~~~~~~~~~~~~~~~~~~~~~^~
 .
 Looking at other instances of the m_solid_stretch_size attribute, the
 use of the expression as a function seems to be erroneous and the
 intent seems to have been to return the plain integer number instead.