tag 411078 + patch
thanks

On Fri, Feb 23, 2007, Mohammed Adnène Trojette wrote:
> Is it necessary to create a license.terms file here and put it in
> /usr/share/doc/amsn for instance?
> Isn't is sufficient to ask upstream to correct this in a later release?
> Is it worth mentioning in README.Debian?

Here is a patch mentioning the Tcl-license terms in debian/copyright.

-- 
Mohammed Adnène Trojette
diff -u amsn-0.95+dfsg2/debian/changelog amsn-0.95+dfsg2/debian/changelog
--- amsn-0.95+dfsg2/debian/changelog
+++ amsn-0.95+dfsg2/debian/changelog
@@ -1,3 +1,12 @@
+amsn (0.95+dfsg2-0.3) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * High urgency for an RC bug fix.
+  * Include the terms of the Tcl-license in debian/copyright.
+    (Closes: #411078)
+
+ -- Mohammed Adnène Trojette <[EMAIL PROTECTED]>  Sat, 24 Feb 2007 11:04:56 +0100
+
 amsn (0.95+dfsg2-0.2) unstable; urgency=high
 
   * Non-maintainer upload
diff -u amsn-0.95+dfsg2/debian/copyright amsn-0.95+dfsg2/debian/copyright
--- amsn-0.95+dfsg2/debian/copyright
+++ amsn-0.95+dfsg2/debian/copyright
@@ -10,4 +10,47 @@
-Copyright:
+License:
 
 This program is released under the GPL version 2, available as
 /usr/share/common-licenses/GPL-2 on your Debian system.
+
+The following files and directories are released under the Tcl-license
+terms (see below):
+utils/base64/base64.tcl
+utils/base64/uuencode.tcl
+utils/macosx/QuickTimeTcl3.1/movie.tcl
+utils/BWidget-1.7.0/
+utils/http2.4/http.tcl
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.  THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal 
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2).  If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs.  Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license. 

Reply via email to