Bug#920575: copyright-without-copyright-notice assumes upstream has copyright notices
On Mon, Jan 28, 2019 at 05:07:54PM +0100, Chris Lamb wrote:
> > However, this also applies to any upstream that simply doesn't
> > contain any copyright notices.
>
> Mm, do you have any examples, out of interest?
Many Rust projects, which just provide a license identifier in
Cargo.toml and no copyright notices or license notices in source files.
> > 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
>
> I would agree it would be wrong in those but I'm thinking that
> statistically-speaking this is surely uncommon enough that making
> Lintian drop this check (which is what you are asking for, right?)
> a net negative.
No, I'm not suggesting dropping the check entirely. Would it be possible
to only run the check if the package source contains at least one
copyright notice?
Reply to: