Alexis Sukrieh <[EMAIL PROTECTED]> writes: > Then, I don't understand why we have this discussion _after_ the policy > has been changed...
> I thought the policy was a trustable document, where developers could > find guidelines for their work, it seems that it's not always true. Sad. debian-policy, like every other package, will occasionally have bugs. Let's not exaggerate. > In the meantime, do you suggest to use lintian overrides for fixing this > in webapp packages or purely ignoring the lintian complaints? Given that I already modified lintian in Subversion for the Policy 3.7.2 release, I would vote that you just not worry about it. There will be a new upload of lintian shortly. The point of syncing lintian to Policy immediately is that I plan on *continuing* to sync lintian to Policy immediately. One of the advantages of doing this is that, since I'm adding new tests for the testable changes in Policy as we go, people actually *notice* Policy changes. :) lintian, like debian-policy and every other package, will also occasionally have bugs. This one in particular, in both cases, won't even have migrated to testing. It'll be fine, honest. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
