Santiago Vila <[email protected]> writes:

> reassign 517196 base-files
> thanks
>
> On Thu, 26 Feb 2009, Sven Joachim wrote:
>
>> Package: libidn11
>> Version: 1.12-1
>> Severity: serious
>> 
>> ,----[ /usr/share/doc/libidn11/copyright ]
>> | Files: doc/libidn.texi
>> | Copyright: Copyright 2002-2009 Simon Josefsson.
>> | License: GFDL-1.3+
>> |  This is the manual, licensed under GFDLv1.3+.  
>> | 
>> |   Copyright @copyright{} 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 
>> Simon Josefsson.
>> | 
>> |   Permission is granted to copy, distribute and/or modify this document
>> |   under the terms of the GNU Free Documentation License, Version 1.3 or
>> |   any later version published by the Free Software Foundation; with no
>> |   Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
>> |   copy of the license is included in the section entitled ``GNU Free
>> |   Documentation License''.
>> | 
>> |  On Debian systems, the complete text of the GNU Free Documentation
>> |  License Version 1.3 can be found in the file
>> |  `/usr/share/common-licenses/GFDL-1.3'.
>> `----
>> 
>> Unfortunately it cannot be found there, so until base-files includes
>> that file you have to full-quote the GFDL 1.3 in debian/copyright.
>> 
>> I think it would be good to actually ship the GFDL 1.3 in base-files,
>> since more packages are going to switch to it and it may still be a long
>> road to GFDL 2.0.  X-Debbugs-CC to the base-files maintainer for his
>> opinion.
>
> Hi. Thanks a lot for the CC.
>
> In fact, I almost included the latest GFDL in base-files before the
> release of lenny, but in the end it happened not to worth the effort
> *for lenny*.
>
> Now that lenny has been released, I agree that the best course of
> action here is to update the GFDL in base-files, hence the reassign.

Thanks.  If your upload is pending, I suppose I don't have to upload a
new libidn package with a complete copy of the GFDLv1.3?

/Simon



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to