Ticket #957 (closed task: fixed)

Opened 13 years ago

Last modified 11 years ago

Review Lintian VendorCustomization spec and use it

Reported by: geofft Owned by:
Priority: high Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version: debathena-lintian-config 1.0, debathena-debian-dev 0.3
Upstream bug:


 pabs mentioned to us on debian-derivatives that the  Lintian VendorCustomization spec probably does most of what we want in terms of squelching spurious Lintian errors and adding new ones. This has been merged into Lintian master. We should create a Debathena profile and make sure the spec is sufficient for our needs.

Change History

comment:1 Changed 13 years ago by geofft

Hm,  this thread link is probably a bit more useful. In particular, note the reply from the Lintian team

The implementation has been merged into the master branch already, but
we have not released yet so we can still take suggestions without
breaking any "official stable" API. :)

Anyhow, basically Lintian will do the right thing if the debathena has /
provides two things: A dpkg origin file and a Lintian vendor profile.
  In the absence of a dpkg-origin file, you can use LINTIAN_PROFILE in
the config file (which works as long as the user does not have their own
and forget to copy that part).

comment:2 Changed 11 years ago by jdreed

r25857 creates debathena-lintian-config. I think playing with dpkg origin files is more trouble than it's worth, and I'm not sure how to manage the /etc/dpkg/origins/default symlink (manually seems wrong, c-p-d seems like a large hammer). We should just put DEBUILD_LINTIAN_OPTS="--profile debathena" in .devscripts and move on.

comment:3 Changed 11 years ago by jdreed

  • Status changed from new to committed

comment:4 Changed 11 years ago by jdreed

  • Fixed in version set to debathena-lintian-config 1.0, debathena-debian-dev 0.3

comment:5 Changed 11 years ago by jdreed

  • Status changed from committed to development

comment:6 Changed 11 years ago by jdreed

  • Status changed from development to proposed

comment:7 Changed 11 years ago by jdreed

  • Status changed from proposed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.