Description of problem: Checking any c++ files (even a trivial 'Hello World' application), vim syntastic plugin fails showing the following warnings and errors: Error detected while processing function 82: line 9: E605: Exception not caught: Syntastic: Checker c/avrgcc redirects to unregistered checker c/avrgcc E605: Exception not caught: Syntastic: Checker c/clang_check redirects to unregistered checker c/clang_check E605: Exception not caught: Syntastic: Checker c/clang_tidy redirects to unregistered checker c/clang_tidy E605: Exception not caught: Syntastic: Checker c/cppcheck redirects to unregistered checker c/cppcheck E605: Exception not caught: Syntastic: Checker c/cppclean redirects to unregistered checker c/cppclean E605: Exception not caught: Syntastic: Checker c/flawfinder redirects to unregistered checker c/flawfinder E605: Exception not caught: Syntastic: Checker c/oclint redirects to unregistered checker c/oclint E605: Exception not caught: Syntastic: Checker c/pc_lint redirects to unregistered checker c/pc_lint Error detected while processing function <SNR>26_BufWritePostHook[4]..<SNR>26_UpdateErrors[15]..<SNR>26_CacheErrors[39]..18[1]..17[24]..SyntaxCheckers_cpp_gcc_GetLocList: line 1: E117: Unknown function: syntastic#c#GetLocList Error detected while processing function <SNR>26_BufWritePostHook[4]..<SNR>26_UpdateErrors[15]..<SNR>26_CacheErrors[39]..18[1]..40: line 3: E712: Argument of filter() must be a List or Dictionary Apparently the issue lies in package vim-syntastic-c not being a dependency for vim-syntastic-cpp although both are needed (at least when using gcc or cppcheck as external checkers for c-like languages). Version-Release number of selected component (if applicable): vim-syntastic 3.10.0-4 vim-minimal, vim-common and vim-enhanced 2:8.2.587-1 How reproducible: Open any c++ files, try to save with :w Steps to Reproduce: 1. Install any flavour of vim then vim-syntastic and vim-syntastic-cpp 2. Create a minimal c++ skeleton app (with or without syntax error, it does not matter) 3. activate the control over the syntax by trying to save the file as foo.cpp with command :w Actual results: The list of warnings/errors reported above Expected results: Syntax checking is performed and syntax errors are highlighted in the source code Additional info:
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Please re-open this bug. The problem still exists in 2025 !!! And it is a simple dependency to add on the spec file. Without vim-syntastic-c I get exactly the same errors mentioned above. They disappear when this package is installed... I'm on a fedora 42, x86_64 machine.
Added the (seemingly) current maintainer of these packages in CC. Sorry mhjacks if I'm wrong.
I'm the right maintainer. I think I took vim-syntastic after Fedora 32 so I never saw this, sorry. It's a little trickier to add this dependency because all of the subpackages are generated via macro, but I'll look at a way to do it without breaking everything.
FEDORA-2025-6e06a5e0af (vim-syntastic-3.10.0-28.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6e06a5e0af
FEDORA-2025-9a3de6f432 (vim-syntastic-3.10.0-28.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-9a3de6f432
FEDORA-2025-9a3de6f432 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9a3de6f432` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9a3de6f432 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-6e06a5e0af has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6e06a5e0af` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6e06a5e0af See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-9a3de6f432 (vim-syntastic-3.10.0-28.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-6e06a5e0af (vim-syntastic-3.10.0-28.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.