Package: dhcp3
Version: 3.0.6-1
Severity: serious

Hi!

I have a distinct impression of reporting this bug before, for the dhcp3
package, but I cannot find the report at:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=both;dist=unstable;package=dhcp3;repeatmerged=1

Possibly the package has been renamed or the bug was reassigned or
something.  However, the problem still remains.

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

+  ./dhcp-3.0.6/doc/rfc1542.txt
+  ./dhcp-3.0.6/doc/rfc2132.txt
+  ./dhcp-3.0.6/doc/draft-ietf-dhc-dhcp-dns-12.txt
+  ./dhcp-3.0.6/doc/rfc2489.txt
+  ./dhcp-3.0.6/doc/rfc2131.txt
+  ./dhcp-3.0.6/doc/draft-ietf-dhc-authentication-14.txt
+  ./dhcp-3.0.6/doc/rfc2485.txt
+  ./dhcp-3.0.6/doc/rfc951.txt
+  ./dhcp-3.0.6/doc/draft-ietf-dhc-failover-07.txt
doc/ja_JP.eucJP

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 'dfsg' to the Debian package
   version name.

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


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

Reply via email to