Your message dated Thu, 22 Jun 2006 10:32:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#199810: fixed in libnss-ldap 251-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: doc-rfc Version: 2000.08-1 Severity: serious The license on this package is pretty clearly non-free. The doc-rfc package is a great resource, but its license makes it unsuitable for main. The older RFC's appear to me to be DFSG-free, since the most onerous restrictions are described as a "courtesy": 3. Favor or indulgence, as distinguished from right; as, a title given one by courtesy. The newer ones, however, are not: However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The phrase "in any way," fails DFSG 3, and "for the purposes..." and the subsequent language fails DFSG 6. There are no other problems with the "new" license that I can see. Perhaps only the DFSG-free RFC's could be split into a doc-rfc-nonfree package? Copyright: (this is rfc-copyright-story in the rfc-editor subdirectory.) "Hi. The Request For Comments (RFC) documents are intended to have wide distribution. 1. Copying and distributing the whole RFC without any changes: 1a. The copying and free redistribution are generally encouraged. 1b. The inclusion of RFCs in other documents and collections that are distributed for a fee is also encouraged, though in this case it is a courtesy (i) to ask the RFC author and (ii) provide the RFC author with a copy of the final document or collection. Anyone can takes some RFCs, put them in a book, copyright the book, and sell it. This in no way inhibits anyone else from doing the same thing, or inhibits any other distribution of the RFCs. 2. Copying and distributing the whole RFC with changes in format, font, etcetera: 2a. The same as case 1 with the addition that a note should be made of the reformatting. 3. Copying and distributing portions of an RFC: 3a. As with any material excerpted from another source, proper credit and citations must be provided. 4. Translating RFCs into other languages: 4a. Since wide distribution of RFCs is very desirable, translation into other languages is also desirable. The same requirements and courtesies should be followed in distributing RFCs in translation as would be followed when distributing RFCs in the original language. --jon." Newer RFCs are under the following copyright: "Full Copyright Statement Copyright (C) The Internet Society (1998). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux apocalypse 2.4.3 #1 Mon Apr 2 04:43:41 UTC 2001 i586
--- End Message ---
--- Begin Message ---Source: libnss-ldap Source-Version: 251-1 We believe that the bug you reported is fixed in the latest version of libnss-ldap, which is due to be installed in the Debian FTP archive: libnss-ldap_251-1.diff.gz to pool/main/libn/libnss-ldap/libnss-ldap_251-1.diff.gz libnss-ldap_251-1.dsc to pool/main/libn/libnss-ldap/libnss-ldap_251-1.dsc libnss-ldap_251-1_amd64.deb to pool/main/libn/libnss-ldap/libnss-ldap_251-1_amd64.deb libnss-ldap_251.orig.tar.gz to pool/main/libn/libnss-ldap/libnss-ldap_251.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Frost <[EMAIL PROTECTED]> (supplier of updated libnss-ldap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 22 Jun 2006 10:01:07 -0400 Source: libnss-ldap Binary: libnss-ldap Architecture: source amd64 Version: 251-1 Distribution: unstable Urgency: low Maintainer: Stephen Frost <[EMAIL PROTECTED]> Changed-By: Stephen Frost <[EMAIL PROTECTED]> Description: libnss-ldap - NSS module for using LDAP as a naming service Closes: 199810 302391 302396 302541 302562 308490 310421 312284 312435 314461 316973 317672 323580 330911 332001 332600 335133 340633 341539 347477 352032 354093 359341 364051 366540 367766 368191 369192 Changes: libnss-ldap (251-1) unstable; urgency=low . * New upstream version, Closes: #332600 * Upstream fixes, Closes: #323580, #302391, #308490 * Maintainer upload, Closes: #316973, #335133 * Changed debconf 'host' question to 'uri', Closes: #312284, #359341 * Added additional commentary to the ldap.conf, Closes: #368191, #369192 * Enabled configurable krb5 CCNAME, Closes: #352032 * Included Swedish, Vietnamese and Czech translations, Closes: #317672, #312435, #340633 * Modified syslog() calls to use LOG_AUTHPRIV facility, Closes: #310421 * Removed build-depend on libdb4.2-dev, Closes: #302541 * Changed nscd restart to use invoke-rc.d, Closes: #367766 * Changed depends to allow debconf-2.0, Closes: #332001 * Ensure that libnss-ldap is compiled with libpthread, Closes: #314461, #330911, #366540, #347477 * Changed to using upstream manpage, Closes: #302396 * Added escaping to password handling, Closes: #341539 * Moved ldap.secret to libnss-ldap.secret, Closes: #302562 * Upstream removed RFC from tarball, Closes: #199810 * Cleaned up copyright file, Closes: #364051 * Fixed possible overflow in uid/gid handling, Closes: #354093 Files: 4a867275f6d8b2e6bfd9aee03693f5ab 669 net extra libnss-ldap_251-1.dsc a80718b3f7cf46f2579a26f9d6fbcd46 228931 net extra libnss-ldap_251.orig.tar.gz bc8ffc5af50888ba802e6ac4472d9db3 116590 net extra libnss-ldap_251-1.diff.gz d124c0982d5cdcbf8112ff5e90c8bfa7 97460 net extra libnss-ldap_251-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEmtJyrzgMPqB3kigRAoy7AJ9bOqoVL3NDNS8LLVwKf9BaXztvmwCfbMHr OZWrNrztt39AWdEqckl1Ksk= =Tbl5 -----END PGP SIGNATURE-----
--- End Message ---
