[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#380927: marked as done (Python transition (#2): you are building a private python module !)

Your message dated Tue, 01 Aug 2006 15:37:02 -0700
with message-id <E1G82rG-00075P-Ha@spohr.debian.org>
and subject line Bug#380927: fixed in radiuscontext 1.88-2
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: radiuscontext
Version: 1.88-1
Severity: important

  Hi, your package has been detected as generating a (for most of that
mass bug fill: private) 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 (which should
happend on tomorrow - Wed 2nd of July). 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
      especially "Notes for packages with private modules/extensions"

Special Notes

  * embedded interpreters: You don't *need* to do anything for your
    package, though using XS/XB-Python-Version is much appreciated as it
    helps tracking your package for binNMUs when python2.4 will become

  * if you need help updating your package, you can either:
     - mail debian-python@lists.debian.org ,
     - tag your bug + help ,
     - come on #debian-python/OFTC.

--- End Message ---
--- Begin Message ---
Source: radiuscontext
Source-Version: 1.88-2

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

  to pool/main/r/radiuscontext/radiuscontext_1.88-2.diff.gz
  to pool/main/r/radiuscontext/radiuscontext_1.88-2.dsc
  to pool/main/r/radiuscontext/radiuscontext_1.88-2_all.deb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 380927@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Pierre Habouzit <madcoder@debian.org> (supplier of updated radiuscontext 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 ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Tue,  1 Aug 2006 22:14:02 +0200
Source: radiuscontext
Binary: radiuscontext
Architecture: source all
Version: 1.88-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Pierre Habouzit <madcoder@debian.org>
 radiuscontext - RADIUS log parser and report generator
Closes: 380927
 radiuscontext (1.88-2) unstable; urgency=low
   * QA Upload.
   * Update package to the last python policy (Closes: #380927).
   * Bump Standards-Version to 3.7.2.
   * Bump DH_COMPAT to 5.
 5e7dd1b248bdbf937ebd309cb580e924 632 admin optional radiuscontext_1.88-2.dsc
 10a0d6f8fdd3f5530306ae1596445e8c 3739 admin optional radiuscontext_1.88-2.diff.gz
 f08f7573a089b64d48ed1eaec7b7c22d 29018 admin optional radiuscontext_1.88-2_all.deb

Version: GnuPG v1.4.3 (GNU/Linux)


--- End Message ---

Reply to: