Niels Thykier ni...@thykier.net 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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
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
Package: lintian
Version: 2.3.4
Severity: wishlist
When working with packages not intended for upload to Debian but used
with internal repositories to create systems based on Debian, it is
still useful to run lintian over the results of dpkg-buildpackage.
Such configurations have non-standard
Neil Williams codeh...@debian.org writes:
When working with packages not intended for upload to Debian but used
with internal repositories to create systems based on Debian, it is
still useful to run lintian over the results of dpkg-buildpackage.
Such configurations have non-standard suites
On Thu, 25 Mar 2010 11:25:51 -0700
Russ Allbery r...@debian.org wrote:
There's really no way for Lintian to use information from the source
package to override tags for the *.changes file. Those are two entirely
separate objects to Lintian, and the *.changes file is parsed and tags
emitted
Neil Williams codeh...@debian.org writes:
Russ Allbery r...@debian.org wrote:
The supported way of handling unwanted tags from the *.changes file is to
suppress them from the command line:
lintian --suppress-tags bad-distribution-in-changes-file
Sounds like an alias is required . . .
6 matches
Mail list logo
