Debian Patches
Status for mindthegap/2.3.0-6
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| use_debian_packaged_gatb-core.patch | Modify CMakeLists.txt ...to allow for CMake to use system-wide libraries instead of a localised binary within the same dir tree. | Shayan Doust <hello@shayandoust.me> | no | 2020-06-21 | ||
| remove_unnecessary_installs.patch | 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 | Shayan Doust <hello@shayandoust.me> | no | 2019-07-09 | ||
| modify_tests_for_autopkgtest.patch | 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 | Shayan Doust <hello@shayandoust.me> | no | 2020-06-21 | ||
| 2to3.patch | Automatic port to Python3 via 2to3 --write --nobackups *.py | Andreas Tille <tille@debian.org> | no | 2019-07-09 | ||
| fix-use-as-function.patch | 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. |
Étienne Mollier <emollier@debian.org> | yes | debian | 2024-09-06 | |
| fix-printf-argument-order.patch | Fix mismatched printf arguments in writeFilledBreakpoint The format string of the fprintf() call in Filler::writeFilledBreakpoint() expects a string, an integer, another integer, two doubles and a final string. The arguments were however supplied in the order string, integer, integer, string, double, double, so the first %.2f read the pointer to the "solution i/n" string as a double and the trailing %s dereferenced the bit pattern of a floating point value as a pointer. . This is undefined behaviour. It happened to work on most architectures, but makes the fill step crash with SIGBUS on loong64, which in turn makes the autopkgtest fail. . Fix the argument order to match the format string. |
Andreas Tille <tille@debian.org> | no | 2026-11-08 |