Re: how to mention GPL in the debian/copyright file
Hello Henning, thank you for your help. On Thu, Jan 13, 2005 at 10:25:58PM +, Henning Makholm wrote: What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. Does this mean we need all the notes from the source files with duplicates removed? Do you have any reference for this? Maybe debian-policy (this is where I looked) could be changed to include this information? I find for example the appended notices. Should I replace my text blurb by the concatenation of all these notices? Does different white space count as being different? Now confused, Jochen PS.: I looked at the vroot.h license (last one in my list) which I did not spot before. I think is is ok for our purposes. Do you agree? == * from the README: This is public release of ChBg distributed under GPL. [...] License : - Chbg is licensed under terms of GPL. See COPYING. * from src/absimg.c: /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999 - 2001 Ondrejicka Stefan*/ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ * from src/gdk_imlib1.c: (different copyright year) /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999,2000 Ondrejicka Stefan */ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ * from fnmatch.c: (different copyright holder) /* Copyright (C) 1991, 1992, 1993, 1996, 1997 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ * from gimpgradient.c: (even more different copyright holder) /* The GIMP -- an image manipulation program * Copyright (C) 1995 Spencer Kimball and Peter Mattis * * Gradient editor module copyight (C) 1996-1997 Federico Mena Quintero * [EMAIL PROTECTED] * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURIGHTE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ * from gtkgbpixmap.c: (gimp again, but different names) /* GTK - The GIMP Toolkit * Copyright (C) 1995-1997 Peter Mattis, Spencer Kimball and Josh MacDonald * GtkBgPixmap Copyright (C) 2000 Stefan Ondrejicka [EMAIL PROTECTED] * * Insensitive pixmap building code by Eckehard Berns from GNOME Stock * Copyright (C) 1997, 1998 Free Software Foundation * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Library General Public * License as published by the Free Software Foundation; either * version 2 of the License, or (at your option) any later version. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Library General Public License for more details. * * You should have received a copy of the GNU Library General Public * License along with this library; if not, write to the * Free
Re: how to mention GPL in the debian/copyright file
On Thu, 13 Jan 2005, Jochen Voss wrote: I have a question about how to write the debian/copyright file for packages which are distributed under the GPL. Currently the debian/copyright file of chbg contains the paragraph Chbg is copyrigthed by Ondrejicka Stefan ([EMAIL PROTECTED]). It is license under the GPL. On Debian systems, the complete text of the GNU General Public License can be found in the /usr/share/common-licenses/GPL file. Unfortunatly, this is incorrect. The code is licensed under GPL 2 or later. (See below where I discuss the issues with this.) [SNIP] My questions: 1) Is it required to include the above three paragraphs into the debian/copyright file? The debian/copyright file must include the upstream's copyright statement. This typically includes the three paragraphs listed above. In your case, it looks like the copyright statement is just the following: /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999,2000 Ondrejicka Stefan */ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ However, I strongly suggest that you talk to upstream, and have upstream use the form of copyright statement and licensing statement mentioned in the GNU GPL itself, namely: one line to give the program's name and a brief idea of what it does. Copyright (C) 19yy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; see the file COPYING. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. 2) In case it is not required, is it for some other reason preferable to include them? It is preferable to include them from the upstream maintainer's point of view, because it makes it explicit what license the work is released under. In the case of this work, it's very difficult to accertain what license the images are released under, as there is no LICENSE or similar file that contains a copyright statement and license statement covering the entire archive. While this may seem a bit overdone, it's really in the best interest of the upstream maintainer to follow the instructions of the GNU GPL when upstream places code under the GPL. Don Armstrong -- There are two types of people in this world, good and bad. The good sleep better, but the bad seem to enjoy the waking hours much more. -- Woody Allen http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to mention GPL in the debian/copyright file
On Thu, 13 Jan 2005, Henning Makholm wrote: Scripsit Jochen Voss [EMAIL PROTECTED] Recently Justin Pryzby filed bug #290087 against chbg, claiming that the debian/copyright file should instead contain the 3 paragraphs as found in /usr/share/debhelper/dh_make/native/copyright, which turn out to be [snip standard GPL blob] 1) Is it required to include the above three paragraphs into the debian/copyright file? What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. As far as I can see from a random sample (src/fnmatch.c) from the source package, this notice happens to be identical to the blurb you quoted from debhelper, but if it had been different, you should add the notice actually found in the upstream source. I actually missed this particular one... fnmatch.c is not copyrighted by Stefan Ondrejicka either. Nor is gtkclrbutton.c. The copyright file needs to include the copyright statements for the different works that have been included in chbg, since there are at least 5 copyright holders that I've identified so far. (FSF, Stefan, Peter, Spencer, and Josh.) [I'm ignoring the auto* stuff, but since that's owned by the FSF as well, you're probably ok.] Don Armstrong -- If it jams, force it. If it breaks, it needed replacing anyway. -- Lowery's Law http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to mention GPL in the debian/copyright file
Hello, I have a question about how to write the debian/copyright file for packages which are distributed under the GPL. Currently the debian/copyright file of chbg contains the paragraph Chbg is copyrigthed by Ondrejicka Stefan ([EMAIL PROTECTED]). It is license under the GPL. On Debian systems, the complete text of the GNU General Public License can be found in the /usr/share/common-licenses/GPL file. This is there to satisfy the requirement of policy section 12.5: Every package must be accompanied by a verbatim copy of its copyright and distribution license in the file /usr/share/doc/package/copyright. This file must neither be compressed nor be a symbolic link. [...] Packages distributed under the [...] GNU GPL [...], should refer to the files [...] /usr/share/common-licenses/GPL, [...] respectively, rather than quoting them in the copyright file. Recently Justin Pryzby filed bug #290087 against chbg, claiming that the debian/copyright file should instead contain the 3 paragraphs as found in /usr/share/debhelper/dh_make/native/copyright, which turn out to be This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this package; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. My questions: 1) Is it required to include the above three paragraphs into the debian/copyright file? 2) In case it is not required, is it for some other reason preferable to include them? Thank you very much in advance, Jochen PS.: I am not subscribed to debian-devel, so please Cc: me on replies. -- http://seehuhn.de/ signature.asc Description: Digital signature
Re: how to mention GPL in the debian/copyright file
Scripsit Jochen Voss [EMAIL PROTECTED] Recently Justin Pryzby filed bug #290087 against chbg, claiming that the debian/copyright file should instead contain the 3 paragraphs as found in /usr/share/debhelper/dh_make/native/copyright, which turn out to be [snip standard GPL blob] 1) Is it required to include the above three paragraphs into the debian/copyright file? What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. As far as I can see from a random sample (src/fnmatch.c) from the source package, this notice happens to be identical to the blurb you quoted from debhelper, but if it had been different, you should add the notice actually found in the upstream source. -- Henning MakholmWe can hope that this serious deficiency will be remedied in the final version of BibTeX, 1.0, which is expected to appear when the LaTeX 3.0 development is completed.
Re: how to mention GPL in the debian/copyright file
Hello Henning, thank you for your help. On Thu, Jan 13, 2005 at 10:25:58PM +, Henning Makholm wrote: What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. Does this mean we need all the notes from the source files with duplicates removed? Do you have any reference for this? Maybe debian-policy (this is where I looked) could be changed to include this information? I find for example the appended notices. Should I replace my text blurb by the concatenation of all these notices? Does different white space count as being different? Now confused, Jochen PS.: I looked at the vroot.h license (last one in my list) which I did not spot before. I think is is ok for our purposes. Do you agree? == * from the README: This is public release of ChBg distributed under GPL. [...] License : - Chbg is licensed under terms of GPL. See COPYING. * from src/absimg.c: /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999 - 2001 Ondrejicka Stefan*/ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ * from src/gdk_imlib1.c: (different copyright year) /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999,2000 Ondrejicka Stefan */ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ * from fnmatch.c: (different copyright holder) /* Copyright (C) 1991, 1992, 1993, 1996, 1997 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ * from gimpgradient.c: (even more different copyright holder) /* The GIMP -- an image manipulation program * Copyright (C) 1995 Spencer Kimball and Peter Mattis * * Gradient editor module copyight (C) 1996-1997 Federico Mena Quintero * [EMAIL PROTECTED] * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURIGHTE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ * from gtkgbpixmap.c: (gimp again, but different names) /* GTK - The GIMP Toolkit * Copyright (C) 1995-1997 Peter Mattis, Spencer Kimball and Josh MacDonald * GtkBgPixmap Copyright (C) 2000 Stefan Ondrejicka [EMAIL PROTECTED] * * Insensitive pixmap building code by Eckehard Berns from GNOME Stock * Copyright (C) 1997, 1998 Free Software Foundation * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Library General Public * License as published by the Free Software Foundation; either * version 2 of the License, or (at your option) any later version. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Library General Public License for more details. * * You should have received a copy of the GNU Library General Public * License along with this library; if not, write to the * Free
Re: how to mention GPL in the debian/copyright file
On Thu, 13 Jan 2005, Jochen Voss wrote: I have a question about how to write the debian/copyright file for packages which are distributed under the GPL. Currently the debian/copyright file of chbg contains the paragraph Chbg is copyrigthed by Ondrejicka Stefan ([EMAIL PROTECTED]). It is license under the GPL. On Debian systems, the complete text of the GNU General Public License can be found in the /usr/share/common-licenses/GPL file. Unfortunatly, this is incorrect. The code is licensed under GPL 2 or later. (See below where I discuss the issues with this.) [SNIP] My questions: 1) Is it required to include the above three paragraphs into the debian/copyright file? The debian/copyright file must include the upstream's copyright statement. This typically includes the three paragraphs listed above. In your case, it looks like the copyright statement is just the following: /***/ /* This code is part of Desktop Background changer*/ /* called ChBg*/ /* Copyright (c) 1999,2000 Ondrejicka Stefan */ /* ([EMAIL PROTECTED]) */ /* Distributed under GPL 2 or later */ /***/ However, I strongly suggest that you talk to upstream, and have upstream use the form of copyright statement and licensing statement mentioned in the GNU GPL itself, namely: one line to give the program's name and a brief idea of what it does. Copyright (C) 19yy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; see the file COPYING. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. 2) In case it is not required, is it for some other reason preferable to include them? It is preferable to include them from the upstream maintainer's point of view, because it makes it explicit what license the work is released under. In the case of this work, it's very difficult to accertain what license the images are released under, as there is no LICENSE or similar file that contains a copyright statement and license statement covering the entire archive. While this may seem a bit overdone, it's really in the best interest of the upstream maintainer to follow the instructions of the GNU GPL when upstream places code under the GPL. Don Armstrong -- There are two types of people in this world, good and bad. The good sleep better, but the bad seem to enjoy the waking hours much more. -- Woody Allen http://www.donarmstrong.com http://rzlab.ucr.edu
Re: how to mention GPL in the debian/copyright file
On Thu, 13 Jan 2005, Henning Makholm wrote: Scripsit Jochen Voss [EMAIL PROTECTED] Recently Justin Pryzby filed bug #290087 against chbg, claiming that the debian/copyright file should instead contain the 3 paragraphs as found in /usr/share/debhelper/dh_make/native/copyright, which turn out to be [snip standard GPL blob] 1) Is it required to include the above three paragraphs into the debian/copyright file? What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. As far as I can see from a random sample (src/fnmatch.c) from the source package, this notice happens to be identical to the blurb you quoted from debhelper, but if it had been different, you should add the notice actually found in the upstream source. I actually missed this particular one... fnmatch.c is not copyrighted by Stefan Ondrejicka either. Nor is gtkclrbutton.c. The copyright file needs to include the copyright statements for the different works that have been included in chbg, since there are at least 5 copyright holders that I've identified so far. (FSF, Stefan, Peter, Spencer, and Josh.) [I'm ignoring the auto* stuff, but since that's owned by the FSF as well, you're probably ok.] Don Armstrong -- If it jams, force it. If it breaks, it needed replacing anyway. -- Lowery's Law http://www.donarmstrong.com http://rzlab.ucr.edu
Re: how to mention GPL in the debian/copyright file
Henning Makholm wrote: found in /usr/share/debhelper/dh_make/native/copyright, which turn out What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. As far as I can see from a random sample (src/fnmatch.c) from the source package, this notice happens to be identical to the blurb you quoted from debhelper Debhelper does not contain such a GPL copyright blurb. -- see shy jo, who will keep correcting people who confuse dh-make and debhelper forever, I suppose signature.asc Description: Digital signature
Re: how to mention GPL in the debian/copyright file
Scripsit Jochen Voss [EMAIL PROTECTED] On Thu, Jan 13, 2005 at 10:25:58PM +, Henning Makholm wrote: What you should include is the exact notice found in the upstream source which says that the program is covered by the GPL. Does this mean we need all the notes from the source files with duplicates removed? Yes. All authors who claim copyright in a source file should be credited in the Debian copyright file, together with the exact statement of license they issued. For many free licences this is a legal requirement, because the notices in the source are not shipped in the .deb otherwise, and even when it isn't it would be discourteous in extreme not to quote it anyway. This is what /usr/share/doc/*/copyright is _for_. Does different white space count as being different? Current best practice is, as far as I'm aware, something like: 1. Minor formatting differences, including different styles of comment markup, line wrapping and other whitespace, can be compressed away in the copyright file. 2. Similarly, two authors who assert copyright but give identical license notices can be compressed into just giving both copyright assertions in the copyright file, followed by the common license notice. 3. Actual differences in wording should be preserved, even if they may seem insignificant to the packager, except perhaps where the difference is beyond any conceivable doubt due to a mere typo. Do you have any reference for this? Policy section 12.5. A verbatim copy of its copyright and distribution license means just what it says. Policy perhaps neglects to explicitly point out that this applies simultaneously to every copyright [notice] and every distribution licence that covers the package, but I still think this can safely be left to the reader's imagination. I find for example the appended notices. Should I replace my text blurb by the concatenation of all these notices? Yes. See e.g. /usr/share/doc/xlibs/copyright for an example of how large this can be in complex cases, but it all has to be there. PS.: I looked at the vroot.h license (last one in my list) which I did not spot before. I think is is ok for our purposes. Do you agree? Yes, it looks like a minor rewording of the common 3-clause BSD license: Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permis- sion notice appear in supporting documentation, and that the name of Solbourne not be used in advertising in publicity pertaining to distribution of the software without specific, written prior permission. ANDREAS STOLCKE AND SOLBOURNE COMPUTER INC. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL ANDREAS STOLCKE OR SOLBOURNE BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. -- Henning MakholmI ... I have to return some videos.
Re: how to mention GPL in the debian/copyright file
Scripsit Joey Hess [EMAIL PROTECTED] Henning Makholm wrote: found in /usr/share/debhelper/dh_make/native/copyright, which turn out this notice happens to be identical to the blurb you quoted from debhelper Debhelper does not contain such a GPL copyright blurb. Sorry. Damn dh-make's creative installation directory choices. -- Henning Makholm Der er ingen der sigter på slottet. D'herrer konger agter at triumfere fra balkonen når de har slået hinanden ihjel.