[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#406528: marked as done (texlive-lang: woeful copyright file)

Your message dated Thu, 12 Jul 2012 22:04:01 +0200
with message-id <87sjcwwxu6.fsf@riesling.miltenberg.kuesterei.ch>
and subject line Closing this bug
has caused the Debian Bug report #406528,
regarding texlive-lang: woeful copyright file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

406528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406528
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tetex-base
Version: 2.0.2-5

| Some individual parts of this distribution may have their own
| copyright.  Please look into the respective files for their copyright.

The copyright file should list the license of all files, not tell you
to look at random other files.  [Yes, I know this is a pain for large
packages and lots of people don't do it, but...]

| Seminar and KOMA-Script have changed their licenses recently but
| there may still files that refer to their old copyrights.  Both are
| copyrighted under the LPPL (LaTeX Project Public License) now. You
| can find the text of the LPPL in the file
| /usr/share/doc/tetex-base/lppl.txt.gz.

The LPPL should be in the copyright file, not an external one.


--- End Message ---
--- Begin Message ---
Hi all,

I am closing these bugs now.  The license file of all affected packages
is generated from the license info in the Catalogue, and therefore is
complete. Infos for every single file are in the referenced file

This means that the woeful format of the copyright file is fixed.

All other issues in the bug report are also elsewhere. Converting the
copyright file to the new automatically parseable format is a different
issue, and if any detail is missing or wrong this is a separate bug,

Regards, Frank

--- End Message ---

Reply to: