#10 Licencing done incorrectly!!

closed-fixed
None
9
2008-10-31
2005-10-09
Paul Wise
No

I was thinking of packaging pylibpcap for Debian, but the licence is very vague. "under the terms of the BSD Licence" means nothing without including a specific reference to those terms or a copy of them. Please do the following:

* Move the contents of COPYING into the README file.
* Add a new file called COPYING or LICENCE containing the exact terms of the BSD licence that you refer to in the README
* Please do not use the old 4-clause BSD licence - it contains an obnoxious advertising clause

Discussion

  • Paul Wise
    Paul Wise
    2005-10-09

    • priority: 5 --> 9
     
  • David Margrave
    David Margrave
    2006-10-24

    Logged In: YES
    user_id=31040

    hi,

    sorry for taking a year to get back to you.

    i would love to have pylibpcap packaged for debian and am
    discussing the license issues with the other project admin.
    i personally have no philosophical issues with this or that
    license.

    dave

     
  • David Margrave
    David Margrave
    2006-10-24

    • assigned_to: nobody --> davidma
     
  • Wim Lewis
    Wim Lewis
    2007-02-14

    Logged In: YES
    user_id=110010
    Originator: NO

    OK, the COPYING file now contains explicit license text adapted from libpcap's BSD-style license, and the copyright notices on the individual files refer the reader to the COPYING file.

     
  • Wim Lewis
    Wim Lewis
    2007-02-14

    • status: open --> open-fixed
     
  • Paul Wise
    Paul Wise
    2007-07-23

    Logged In: YES
    user_id=35028
    Originator: YES

    I see that you have fixed this in CVS, but not in the latest release. Please release a new version that can be packaged.

    I personally don't have time to do the package, but there is someone else interested in it:

    http://bugs.debian.org/215367

     
  • Paul Wise
    Paul Wise
    2008-10-31

    • status: open-fixed --> closed-fixed
     
  • Paul Wise
    Paul Wise
    2008-10-31

    This bug appears to be fixed in the 0.6.2 release, closing it finally.