Your message dated Tue, 3 Jul 2007 16:25:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 ---
Severity: serious
Package: cyrus-sasl2-mit
Version: 2.1.19.dfsg1-1
User: [EMAIL PROTECTED]
Usertags: nonfree-doc rfc

Hi!

Based on the package names, I suspect cyrus-sasl2-mit share the same
source package as the cyrus-sasl2 package, and that the problem below
might get fixed automatically when cyrus-sasl2-mit is updated to use
the latest cyrus-sasl2 sources (see #365183), but as far as I can
tell, it isn't guaranteed that this will happen automatically, hence
this report.

This source package contains the following files from the
IETF under non-free license terms:

cyrus-sasl-2.1.19.dfsg1/java/doc/draft-weltman-java-sasl-02.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-rfc2831bis-02.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2195.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc3174.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-newman-sasl-c-api-01.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-saslprep-04.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc1939.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-rfc2222bis-03.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-crammd5-01.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2243.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2444.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2831.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2222.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2289.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-plain-03.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2595.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2945.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc1321.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-anon-02.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2104.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-burdis-cat-srp-sasl-08.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-ietf-sasl-gssapi-00.txt
cyrus-sasl-2.1.19.dfsg1/doc/draft-murchison-sasl-login-00.txt
cyrus-sasl-2.1.19.dfsg1/doc/rfc2245.txt

The license on RFC/I-Ds is not DFSG-free, see:
 * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199810
 * http://release.debian.org/removing-non-free-documentation
 * http://wiki.debian.org/NonFreeIETFDocuments

The etch release policy says binary and source packages must each be free:
 * http://release.debian.org/etch_rc_policy.txt

The severity is serious, because this violates the Debian policy:
 * http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg

There are (at least) three ways to fix this problem.  In order of
preference:

1. Ask the author of the RFC to re-license the RFC under a free
   license.  A template for this e-mail request can be found at
   http://wiki.debian.org/NonFreeIETFDocuments

2. Remove the non-free material from the source, e.g., by re-packaging
   the upstream archive and adding a 'dfsg' version name to it.

3. Move the package to non-free.

General discussions are kindly requested to take place on debian-legal
or debian-devel in the thread with Subject: "Non-free IETF RFC/I-Ds in
source packages".

Thanks,
Simon


--- End Message ---
--- Begin Message ---
This package has been removed from Debian unstable.  I'm therefore
closing this bug report.  The package has been removed because it
is obsolete; superseded by cyrus-sasl2.

-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---

Reply via email to