Package: libmcpp0 Version: 2.7.2-5 Severity: normal X-Debbugs-Cc: witold.bary...@gmail.com
I don't know what is the upstream status of mcpp, but supertuxkart has few important bug fixes: https://github.com/supertuxkart/stk-code/commit/21cf075e419737879f6868643c16de6b612ae223#diff-57e7858f5e2f96d62d31eda3f49c2fe8be77f37b4406c29b7fd5ecbee1084c9b https://github.com/supertuxkart/stk-code/commit/a79a2a7fabc181a4e0517d04d8cf9cd9300b4741#diff-57e7858f5e2f96d62d31eda3f49c2fe8be77f37b4406c29b7fd5ecbee1084c9b https://github.com/supertuxkart/stk-code/commit/d729c543f97de29f130daa7bac79481eb09acd90#diff-57e7858f5e2f96d62d31eda3f49c2fe8be77f37b4406c29b7fd5ecbee1084c9b https://github.com/supertuxkart/stk-code/commit/c8d036183710e2fd9ea2d819863e3400d04214fb#diff-57e7858f5e2f96d62d31eda3f49c2fe8be77f37b4406c29b7fd5ecbee1084c9b You can see the list here: https://github.com/supertuxkart/stk-code/commits/master/lib/mcpp Personally I would love to see the valgrind and memory leak fixes in Debian. PS. I didn't try to contact upstream, as the last commits are from 2008. There is also CVE-2019-14274, which is somehow addressed here: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14274 As well these proposed fix: https://sourceforge.net/p/mcpp/discussion/565342/thread/ef669864/?limit=25#7fb8 -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmcpp0 depends on: ii libc6 2.31-5 libmcpp0 recommends no packages. libmcpp0 suggests no packages. -- no debconf information
