Package: lintian
Version: 2.5.10.1
Severity: minor
Hi,
On running lintian, I get
W: ccl source: comma-separated-files-in-dep5-copyright paragraph at line 100
The copyright file which the error was reported against is below. This
is an impressive level of checking, and the check is correct. The only
problem is that the line number is wrong. The line in question is
Files: ffigen4/gcc-core-4.0.0.tar.bz2, ffigen4/gcc-objc-4.0.0.tar.bz2
which is line 17 of the file.
Additionally, another small comment. Previously, when I had I wrapped the
Source: line
around (this refers to the 4th line) so that there was no space after
the second line, like this
Source: The main download url is
http://ccl.clozure.com/download.html. The source code was downloaded
from svn.clozure.com. See README.source for further information.
it gave the error
W: ccl source: syntax-error-in-dep5-copyright line 5: Cannot parse line
However at that time, it did not report the
comma-separated-files-in-dep5-copyright error.
Regards, Faheem
#
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Clozure Common Lisp
Upstream-Contact: http://ccl.clozure.com
Source: The main download url is http://ccl.clozure.com/download.html. The
source code
was downloaded from svn.clozure.com. See README.source for further information.
License: LLGPL
Files: *
Copyright: 1994-2012 by Clozure Associates and contributors
License: LLGPL
Files: ffigen4/source/*
Copyright: 2001, 2005 Clozure Associates.
2004, Helmut Eller
License: GPL-2+
Files: ffigen4/gcc-core-4.0.0.tar.bz2, ffigen4/gcc-objc-4.0.0.tar.bz2
Copyright: Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998,
1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
License: GPL-2+
Files: debian/*
Copyright: 2012 Faheem Mitha
License: LLGPL
License: LLGPL
CCL is licensed under the terms of the Lisp Lesser GNU Public License
(LLGPL). The LLGPL consists of a preamble (see below) and the Lessor
GNU Public License 2.1 (LGPL-2.1). Where these conflict, the preamble
takes precedence. CCL is referenced in the preamble as the LIBRARY.
On Debian systems the complete text of the LGPL 2.1 is in the file
/usr/share/common-licenses/LGPL-2.1. The preamble is located in the
file doc/LICENSE, in the CCL sources, and it is reproduced verbatim
below.
.
Preamble to the Gnu Lesser General Public License
=
.
Copyright (c) 2000 Franz Incorporated, Berkeley, CA 94704
.
The concept of the GNU Lesser General Public License version 2.1
(LGPL) has been adopted to govern the use and distribution of
above-mentioned application. However, the LGPL uses terminology that
is more appropriate for a program written in C than one written in
Lisp. Nevertheless, the LGPL can still be applied to a Lisp program if
certain clarifications are made. This document details those
clarifications. Accordingly, the license for the open-source Lisp
applications consists of this document plus the LGPL. Wherever there
is a conflict between this document and the LGPL, this document takes
precedence over the LGPL.
.
A Library in Lisp is a collection of Lisp functions, data and
foreign modules. The form of the Library can be Lisp source code (for
processing by an interpreter) or object code (usually the result of
compilation of source code or built with some other
mechanisms). Foreign modules are object code in a form that can be
linked into a Lisp executable. When we speak of functions we do so in
the most general way to include, in addition, methods and unnamed
functions. Lisp data is also a general term that includes the data
structures resulting from defining Lisp classes. A Lisp application
may include the same set of Lisp objects as does a Library, but this
does not mean that the application is necessarily a work based on the
Library it contains.
.
The Library consists of everything in the distribution file set before
any modifications are made to the files. If any of the functions or
classes in the Library are redefined in other files, then those
redefinitions ARE considered a work based on the Library. If
additional methods are added to generic functions in the Library,
those additional methods are NOT considered a work based on the
Library. If Library classes are subclassed, these subclasses are NOT
considered a work based on the Library. If the Library is modified to
explicitly call other functions that are neither part of Lisp itself
nor an available add-on module to Lisp, then the functions called by
the modified Library ARE considered a work based on the Library. The
goal is to ensure that the Library will compile and run without
getting undefined function errors.
.
It is permitted to add proprietary source code to the Library, but it
must be
