On Fri, 26 Jul 2024, 10:10 Chris Hofstaedtler, <z...@debian.org> wrote:
> On Fri, Jul 26, 2024 at 06:42:11AM +0100, Arif Ali wrote: > > > (It seems that part of the discussions are not on the bug (at least I > > > do not see a Chris participating here)) > > > > > > d/copyright needs to reflect the code "verbatim" -- see Policy > > > > > > Checking a random file, (sos/report/archive.py) the file is licenses > > > GPL2 *only*, while d/copyright says GPL2 *or later*. > > > > > > (An inaccurate d/copyright is a RC bug and a blocker for this RFS) > > > > Ah, apologies for not being clear > > > > The plan was to overhaul the d/copyright file, but there was an issue and > > Chris in Upload #3 put a comment to say it didn't fly [0]. > > I'll note that I've objected to this change: > > d/changelog: +Copyright: 2007-2024 Upstream > > Not listing the authors and just putting "Upstream" there is > _obviously_ wrong for d/copyright. > > > Created a new discussion [1] and PR [2] upstream to discuss the issues > > around this. > > [1] https://github.com/orgs/sosreport/discussions/3705 > > [2] https://github.com/sosreport/sos/pull/3712 > > What happens upstream is a related, but different topic. > > Chris > Thanks for the input. With being 2 topics, if I was to handle the copyright with this commit https://salsa.debian.org/arif-ali/sosreport/-/commit/868b6eff7e3a3b9853e01a518b2762602b95fe26 And the more specifics around the lrc checks later based on upstream conversation, would that suffice? >
