You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beyond simply ensuring that the debs don't have unwanted files (#1507), we should be use lintian to inspect the built deb packages in the config test suite and fail out if checks aren't satisfied.
By default lintian performs comprehensive validation, and we likely won't agree with every recommendation. Still, we can selectively opt in to certain checks via the --tags option. Good candidates for inclusion in the config test suite are:
wrong-file-owner-uid-or-gid
package-contains-vcs-control-file
package-installs-python-bytecode
non-standard-file-perm
A parametrized config test that runs all of the above would be grand. In the context of config tests that inspect warnings, the --fail-on-warnings flag should be used. See lintian-info --tags <tag> for an explanation of what a tag check entails.
The text was updated successfully, but these errors were encountered:
Beyond simply ensuring that the debs don't have unwanted files (#1507), we should be use
lintian
to inspect the built deb packages in the config test suite and fail out if checks aren't satisfied.By default lintian performs comprehensive validation, and we likely won't agree with every recommendation. Still, we can selectively opt in to certain checks via the
--tags
option. Good candidates for inclusion in the config test suite are:A parametrized config test that runs all of the above would be grand. In the context of config tests that inspect warnings, the
--fail-on-warnings
flag should be used. Seelintian-info --tags <tag>
for an explanation of what a tag check entails.The text was updated successfully, but these errors were encountered: