Your message dated Thu, 28 Jun 2007 21:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393375: fixed in imapsync 1.219-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: imapsync
Version: 1.182-1
Severity: serious

Hi!

This bug has been filed on multiple packages, and 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".

It seems this source package contains the following files from the
IETF under non-free license terms:

imapsync-1.182/rfc2342.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.

I went over many packages looking for names of likely non-free files,
and there may be false positives.  If this is the case for your
package, I'm sorry for the noise.  I'll modify the scripts to take
into account false positives when I learn of them, and publish the
list of exceptions under "Known exceptions" at
<http://wiki.debian.org/NonFreeIETFDocuments>.

Thanks,
Simon


--- End Message ---
--- Begin Message ---
Source: imapsync
Source-Version: 1.219-1

We believe that the bug you reported is fixed in the latest version of
imapsync, which is due to be installed in the Debian FTP archive:

imapsync_1.219-1.diff.gz
  to pool/main/i/imapsync/imapsync_1.219-1.diff.gz
imapsync_1.219-1.dsc
  to pool/main/i/imapsync/imapsync_1.219-1.dsc
imapsync_1.219-1_all.deb
  to pool/main/i/imapsync/imapsync_1.219-1_all.deb
imapsync_1.219.orig.tar.gz
  to pool/main/i/imapsync/imapsync_1.219.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.
RISKO Gergely <[EMAIL PROTECTED]> (supplier of updated imapsync 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, 28 Jun 2007 23:20:11 +0200
Source: imapsync
Binary: imapsync
Architecture: source all
Version: 1.219-1
Distribution: unstable
Urgency: low
Maintainer: RISKO Gergely <[EMAIL PROTECTED]>
Changed-By: RISKO Gergely <[EMAIL PROTECTED]>
Description: 
 imapsync   - IMAP synchronization, copy and migration tool
Closes: 391954 393375 410865 417997
Changes: 
 imapsync (1.219-1) unstable; urgency=low
 .
   * New upstream release (closes: #410865, #417997, #391954, #393375)
   * Removed patches/makefile.patch, because it is applied by upstream
   * Added patches/podfix.patch, because pod is wrong, as pointed out by
     podcheck and lintian
Files: 
 f9542ffe83d455f9eca547d366800330 678 net optional imapsync_1.219-1.dsc
 49e4a5b9f614d2ec1d836f628fc193ee 122080 net optional imapsync_1.219.orig.tar.gz
 d597b5b5c1ba81d85f284e7a9f2e68e6 1875 net optional imapsync_1.219-1.diff.gz
 7867561305041acf3c9f582980d04cac 57724 net optional imapsync_1.219-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGhCsFO0PrGO4KNccRAn9CAJwK8lp73gXDa0TV04XDw8FSeD3IAwCeLkkY
DPex2DbHYRBk+rVXnpSliA0=
=S0Kg
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to