Bill Allombert [29/Oct  9:06am GMT] wrote:
> This are only blockers in the mind of the LLM, Debian policy does not
> require to list all copyright holders, instead it says:
>
>   2.3. Copyright considerations
>   =============================
>   
>   Every package must be accompanied by a verbatim copy of its
>   distribution license(s) in the file
>   "/usr/share/doc/PACKAGE/copyright".
>   
>   The copyright information for files in a package must be copied
>   verbatim into "/usr/share/doc/PACKAGE/copyright", when all of the
>   following hold:
>   
>   1. the distribution license for those files requires that copyright
>      information be included in all copies and/or binary distributions;
>   
>   2. the files are shipped in the binary package, either in source or
>      compiled form; and
>   
>   3. the form in which the files are present in the binary package does
>      not include a plain text version of their copyright notices.
>   
>   Thus, the copyright information for files in the source package which
>   are only part of its build process, such as autotools files, need not
>   be included in "/usr/share/doc/PACKAGE/copyright", because those files
>   do not get installed into the binary package.  Similarly, plain text
>   files which include their own copyright information and are installed
>   into the binary package unmodified need not have that copyright
>   information copied into "/usr/share/doc/PACKAGE/copyright"

Yes.  The Policy text you quote should be part of the LLM's prompt.
I was a NEW queue processor myself when I wrote it and it was signed off
on by other FTP team members.  It's accurate and important.

> So at least
>
>> - **Kitware, Inc.** (CMake files)
>> - **Nokia** (1 test file)
>> - **SUSE LLC** (RPM spec)
>
> are not blocker at all.
>
> This LLM fundamentally misunderstand the purpose of debian/copyright.
> There is no way it can give useful report about it.

Improving its prompt would probably go a long way.

The new DFSG team don't tend to engage with threads like this about
their work, which I find very concerning.  I hope they'll respond here;
CCing them.

-- 
Sean Whitton

Reply via email to