Proposed solution: Add --errors-only mode to run-linters to only run pylint in --errors-only mode and mypy: https://github.com/canonical/apport/pull/215
Those two can find relevant errors. The linters like black will be skipped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2028881 Title: apport FTBFS Status in apport package in Ubuntu: Triaged Bug description: Rebuilding apport in mantic today FTBFS because of a pylint complaint. We discussed this in #ubuntu-devel today. I don't think that failing the build on a lint failure is appropriate in distribution packaging in a production build since otherwise the build regresses for no good reason. Linting should be done during development but not enabled in production archive builds. This can be fixed by dropping the lint tests from override_dh_auto_test in debian/rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
