lintian complaints after rerunning debuild --target=binary
Sam Varshavchik
mrsam at courier-mta.com
Sun Mar 27 19:26:15 UTC 2022
After I build my packages, then go back and make some tweaks to
debian/<package>.lintian-overrides, and then run
debuild --target=binary -us -uc
I get these kinds of complaints from lintian, due to these changes:
E: courier-authlib changes: checksum-mismatch-in-changes-file sha256 <package>.deb
E: <package> changes: file-size-mismatch-in-changes-file <package>_amd64.deb 24480 != 24692
So far I've been ignoring these, until I commit all my tweaks, then go back
and rebuild everything from scratch, which clears them out.
Rebuilding from step 0 take a long time. --target=binary is faster.
Running 'dpkg-source -b' results in complaints about all the unwanted
binaries in debian/tmp.
Is there a way to make these errors go away, or some kind of an alternative
approach that avoids having to rebuild everything just because I make an
override change, or make some kind of a change in the install/binary phase?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20220327/1ec4285d/attachment.sig>
More information about the ubuntu-users
mailing list