Niels Thykier <[email protected]> writes: > With the upcoming changes to Lintian, we can process the changes file > together with the source. So we should be able to pull the overrides > for the changes from the source package.
> The question is how/where do we store them? Add a new file (e.g. > d/source/changes.lintian-overrides) or perhaps inside the source > overrides (probably requires modification to the override loading code > to work)? I think the best solution to this bug is to just allow overriding of specific tags on the command line (using the same syntax as an override file). That's how I was going to fix it. Using the source package to provide overrides for the *.changes file is an interesting idea, but it doesn't quite feel right to me. The *.changes file is *usually* generated from a source package, but it doesn't have to be and exists as its own separate, independent thing. Binary builds, for example, will have no source package but will still have a *.changes file on which it's reasonable to run Lintian. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
