Re: DEP5 public-domain Question

2011-07-26 Thread Dominique Dumont
Since others have replied regarding the content of the DEP-5 file, I'll focus on DEP-5 parser On Wednesday 20 July 2011 15:39:09 Yaroslav Halchenko wrote: Also, the DEP5 checker has no clue about public-domain as a short license either: $ config-edit -application dpkg-copyright -ui none

Re: DEP5 public-domain Question

2011-07-26 Thread Jonathan Yu
Hi Dominique, To satisfy DEP5 model constraints, you need to spell out the terms of the licence you want to use. Etheir as a License: public-domain stand-alone section or as text in the File section (after the License: line in the file section). Does that mean that License: PD won't work

Re: DEP5 public-domain Question

2011-07-26 Thread Dominique Dumont
On Tuesday 26 July 2011 13:12:53 Jonathan Yu wrote: Does that mean that License: PD won't work with config-edit? No. Here's an example that works (PD license defined in Files section): ++ Files: * Copyright: 2009, foo bar License: PD Lots of explanations ++ This

Re: DEP5 public-domain Question

2011-07-21 Thread Yaroslav Halchenko
On Wed, 20 Jul 2011, Russ Allbery wrote: License: public-domain insert here the exact wording from upstream explaining why the work is in the public domain You do need some sort of statement about why the work is in the public domain, since that's a rather unusual status and requires some

Re: DEP5 public-domain Question

2011-07-21 Thread Russ Allbery
Yaroslav Halchenko deb...@onerussian.com writes: On Wed, 20 Jul 2011, Russ Allbery wrote: License: public-domain insert here the exact wording from upstream explaining why the work is in the public domain You do need some sort of statement about why the work is in the public domain,

Re: DEP5 public-domain Question

2011-07-21 Thread Stefano Zacchiroli
On Thu, Jul 21, 2011 at 09:57:15AM -0700, Russ Allbery wrote: License: public-domain insert here the exact wording from upstream explaining why the work is in the public domain You do need some sort of statement about why the work is in the public domain, since that's a rather

DEP5 public-domain Question

2011-07-20 Thread Yaroslav Halchenko
quick one -- where to place public domain -- into Copyright or License? http://dep.debian.net/deps/dep5/ kinda suggests to use short license name public-domain within License: field. But also it suggests that Copyright is the correct place for such information (which I agree with, since being

Re: DEP5 public-domain Question

2011-07-20 Thread Russ Allbery
Yaroslav Halchenko deb...@onerussian.com writes: quick one -- where to place public domain -- into Copyright or License? http://dep.debian.net/deps/dep5/ kinda suggests to use short license name public-domain within License: field. But also it suggests that Copyright is the correct place

Re: DEP5 public-domain Question

2011-07-20 Thread Jakub Wilk
* Russ Allbery r...@debian.org, 2011-07-20, 11:06: http://dep.debian.net/deps/dep5/ kinda suggests to use short license name public-domain within License: field. But also it suggests that Copyright is the correct place for such information (which I agree with, since being public domain is

Re: DEP5 public-domain Question

2011-07-20 Thread Russ Allbery
Jakub Wilk jw...@debian.org writes: * Russ Allbery r...@debian.org, 2011-07-20, 11:06: I think public domain in the Debian DEP-5 context is a license. While it's not legally a license, the public domain status serves the same purpose: telling people what rights they have to use the work. So

Re: DEP5 public-domain Question

2011-07-20 Thread Lars Wirzenius
On Wed, Jul 20, 2011 at 08:19:46PM +0200, Jakub Wilk wrote: So what to put in the Copyright field? It's a required one. I'd do something like this: Copyright: not applicable License: public-domain This work was created by the government of the United States of America without