On Mon, Jan 28, 2019 at 12:05:42AM +0100, Chris Lamb wrote: > Thanks for the report. I'm afraid I'm finding it hard to parse in > the lofty abstract; can you perhaps share which package you are > refering to?
In my case, I've encountered this with various personal (local) packages. However, this also applies to any upstream that simply doesn't contain any copyright notices. Suppose you're packaging a piece of software for which `git grep -i copyright` returns absolutely nothing. In that case, requiring `debian/copyright` to contain something that looks like a copyright notice (e.g. "Copyright YYYY Some Person") seems wrong, and having to override that lintian warning seems similarly wrong.
