Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use lintian to validate deb package build process #1637

Closed
conorsch opened this issue Mar 30, 2017 · 2 comments
Closed

Use lintian to validate deb package build process #1637

conorsch opened this issue Mar 30, 2017 · 2 comments
Labels
help wanted Issues we would definitely appreciate volunteer help with ops/deployment
Milestone

Comments

@conorsch
Copy link
Contributor

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.

@redshiftzero redshiftzero added this to the 0.4.1 milestone Jun 6, 2017
@redshiftzero redshiftzero added the help wanted Issues we would definitely appreciate volunteer help with label Aug 19, 2017
@redshiftzero redshiftzero modified the milestones: 0.4.4, 0.4.3 Aug 31, 2017
@redshiftzero redshiftzero modified the milestones: 0.4.4, 0.4.5 Oct 5, 2017
@t2d
Copy link
Contributor

t2d commented Oct 8, 2017

I started to do a very basic implementation at t2d@1f543c2
But this actually makes the verifier fail. In what direction do you want this to progress?

@ghost
Copy link

ghost commented Oct 8, 2017

@t2d I'm sure @conorsch will be very happy to see progress in this direction :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues we would definitely appreciate volunteer help with ops/deployment
Projects
None yet
Development

No branches or pull requests

3 participants