Hello, On Sun 15 Dec 2024 at 01:19am -08, Xiyue Deng wrote:
>> I think Lintian is correct, tbh. > > Can you expand a little on this? The lintian warning text does say: > ,---- > | (Symlinks to another file in /usr/share/doc/pkg or a subdirectory > | thereof are fine and should not trigger this warning.) > `---- > which I believe CHANGELOG.org satisfies. I should have been more explicit. I think that Lintian is right that this file should not be a symlink; I did not mean to comment on whether or not there is a bug in the check. When Policy calls for a file to be installed at /a/b/c and upstream ship that file under the name foo-1.0/d/e.f, we install it directly as /a/b/c. Doing anything else would need a good justification -- for example, that overall the d/rules is simpler. (Suppose upstream's build system already installed the changelog under /usr/share/doc, well, then we might make our changelog file a symlink to it.) This is not the case here, so far as I can see. It's important to remember that upstream's context is different to ours. This is Free Software; we should patch things and move them around as appropriate to our context. > As Soren explained in details, I think a single "Files: *" stanza > should be OK, right? I haven't read Soren's mail. If you mean that a single "Files: *" for all the GPL-3+ licensed files, then yes, that should be fine. I saw that you reformatted copyright claims to drop the (C) and to add commas. Generally licenses require us to reproduce copyright notices verbatim. IANAL, but reformatting is probably not justified. You'll need a copy of the entire EPL-2.0, per Policy 12.5. -- Sean Whitton
