[SCM] supercollider/master: Update changelog and copyright hints

[Jonas Smedegaard]

Hi Dan (and others),

On 12-02-08 at 10:00am, Dan S wrote:
> Thanks for all these tweaks. A question about "copyright_hints": there 
> are quite a few entries in there saying "License: UNKNOWN, FIXME" -- 
> many image files, which have always been part of the SC distribution 
> and were generated within the SC project and are under the same 
> license as the source code. Can I simply delete their entries in 
> copyright_hints, or change "UNKNOWN" to "GPL-2+"?

copyright_hints is not to be edited by hand.  Its purpose is for 
comparison with later automated scans of the source package to help 
discover changes needed to be documented in debian/copyright.


> What about the junk that some automated process has (presumably) 
> dropped into the "Copyright" field for those images?

It is possible to suppress scanning of some files if known to not need 
checking (i.e. if carefully handled by hand in case it *ever* changes) 
by changing DEB_COPYRIGHT_CHECK_IGNORE_REGEX (see the source of 
/usr/share/cdbs/1/rules/utils.mk for its syntax and default value).

Alternatively, to avoid dpkg choking on its binary content, the hints 
file can be listed in debian/source/include-binaries .


> Secondly, I used the word "copyright" in the changelog (after removing 
> the misplaced keyword "copyright" from a helpfile) so now there's a 
> hint like this:
> 
> Files: common/build/ChangeLog
> Copyright: in MoogFF (and don't use keyword '' in files where he doesn't have )
> License: UNKNOWN
>  FIXME
> 
> Argh! That just needs to go, it's a false positive caused by my fixing 
> a false positive :(

Again, you need not care about the hints file unless it tells you to, or 
(as mentioned above) dpkg gets upset about binary content.


> Is there a guide to editing this copyright_hints file? I can't see one 
> online.

CDBS is lacking documentation currently.  README.source has a tiny clue, 
but really you need not mess with it directly unless it tells you to do 
so during build.

Here's what I do to provoke a copyright check as narrowly as possible:

  DEB_MAINTAINER_MODE=1 debian/rules pre-build

If that fails, I do this:

  DEB_MAINTAINER_MODE=1 fakeroot debian/rules clean

...and then follow the instructions and commit the results to git.



BTW, I noticed that you originally added the long list of copyright 
holder for the main Files section.  Are you certain that they are all 
officially declared copyright holders, not authors/contributors?  There 
is a distinction there, and it seems that you simply added the contents
of the AUTHORS file.



NB! Please don't cc me - I am subscribed to the list.

More on that here: http://www.debian.org/MailingLists/#codeofconduct




Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20120208/a1543652/attachment.pgp>