bbqsql_1.1-2_amd64.changes REJECTED

Scott Kitterman debian at kitterman.com
Wed Nov 9 20:11:42 UTC 2016


It depends on the license.

If the license requires the copyright statement be shipped with the code then it needs to be in debian/copyright.  BSD licenses include:

"Redistributions of source code must retain the above copyright notice", so we have to do that.

Scott K

On November 9, 2016 3:01:11 PM EST, Raphael Hertzog <hertzog at debian.org> wrote:
>Hi Chris,
>
>On Wed, 09 Nov 2016, Chris Lamb wrote:
>> Looks like d/copyright isn't completely up to date, eg.:
>
>I understand a reject when we miss a license or misclassify files
>according to their license... but AFAIK we do not require to capture
>all copyright holders in debian/copyright.
>
>Am I wrong?
>
>Even upstream stopped doing it, replacing the copyright
>notice by a generic one: "Copyright 2012, BBQSQL All rights reserved."
>(followed by BSD-3-Clause).
>
>Anyway, Marcos, can you review the copyright file to include all the
>copyright notices in the generic "Files: *" entry? (No need to create
>sub-set like "bbqsql/menu/*" since all files have the same license)
>
>Thank you!
>
>> bbqsql/__init__.py
>> __copyright__ = 'Copyright 2012 Ben Toews (mastahyeti)'
>> 
>> bbqsql/menu/LICENSE.md
>> Copyright 2011, The Social-Engineer Toolkit (SET)
>> 
>> (Stopped looking at this point; there might be others)
>> 
>>  -- Chris Lamb <lamby at debian.org>  Wed, 09 Nov 2016 17:51:09 +0000
>> 
>> 
>> 
>> ===
>> 
>> Please feel free to respond to this email if you don't understand why
>> your files were rejected, or if you upload new files which address
>our
>> concerns.
>> 
>> 
>> 




More information about the Pkg-security-team mailing list