Your message dated Sat, 9 Jun 2007 19:24:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
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: python-xlib
Version: 0.12-5
Severity: important


  Hi, your package has been detected as generating a python
module/extension that may need an upgrade to the new Python Policy[1].

  A wiki page [2] explains what has to be done to upgrade your packages
to the new Policy. This bug may be a false positive, in that case,
please just close the bug.

  This bug is part of a mass bug filling, and its severity will be
raised to serious when python will default to python2.4. Please note
that this bug (even not being RC) falls under the 0-day NMU policy.


  [1] http://lists.debian.org/debian-devel-announce/2006/06/msg00009.html
  [2] http://wiki.debian.org/DebianPython/NewPolicy




--- End Message ---
--- Begin Message ---
Version: 0.12-5.1

acknowleging the fixed in nmu bug.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to