Thorsten Glaser <t...@mirbsd.de> writes: > The update-debian-copyright tag gives bad advice:
> N: The most recent copyright year mentioned for files in ./debian lags > N: behind the year in the timestamp for the most recent changelog > N: entry. > This is a fully normal thing to have. You only update the copyright year > for something when *you* do something relevant for copyright law (that > is passing the threshold of originality) in that year. > Having this tag is misleading because it’ll lead to people bumping the > year because they don’t know better and just to silence lintian. Yeah, and I'm also dubious that we should be telling people how to manage their copyright notices at all. Berne explicitly doesn't require copyright notices. Some licenses require them, but I'm not aware of a license where one is required to update them with new years. Some projects use the approach of only updating the years when the files are changed; others update all years on all files every year (the FSF does this, for instance, based on legal advice from their lawyers). This doesn't feel like something Lintian should have an opinion about. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
