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

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



Your message dated Fri, 18 Aug 2006 08:02:11 -0700
with message-id <E1GE5rP-0004Dq-HE@spohr.debian.org>
and subject line Bug#380955: fixed in qtorrent 2.9.1-6
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: qtorrent
Version: 2.9.1-5
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
    default.

  * 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: qtorrent
Source-Version: 2.9.1-6

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

qtorrent_2.9.1-6.diff.gz
  to pool/main/q/qtorrent/qtorrent_2.9.1-6.diff.gz
qtorrent_2.9.1-6.dsc
  to pool/main/q/qtorrent/qtorrent_2.9.1-6.dsc
qtorrent_2.9.1-6_all.deb
  to pool/main/q/qtorrent/qtorrent_2.9.1-6_all.deb



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 380955@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matej Vela <vela@debian.org> (supplier of updated qtorrent 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)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 18 Aug 2006 16:48:40 +0200
Source: qtorrent
Binary: qtorrent
Architecture: source all
Version: 2.9.1-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Matej Vela <vela@debian.org>
Description: 
 qtorrent   - graphical BitTorrent client using Qt 3.x
Closes: 380955
Changes: 
 qtorrent (2.9.1-6) unstable; urgency=low
 .
   * QA upload.
   * Switch to new Python policy.  Closes: #380955.
   * Switch to debhelper 5.
   * Conforms to Standards version 3.7.2.
Files: 
 79b14db8f915ed08ba50f00b9e2910f8 675 net optional qtorrent_2.9.1-6.dsc
 3196cff4b1f09838b9a2d3b8ff38b9b7 3547 net optional qtorrent_2.9.1-6.diff.gz
 45232143eb0c13342b328949b1d4768e 81916 net optional qtorrent_2.9.1-6_all.deb

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

iD8DBQFE5dNUxBYivKllgY8RAr+gAKCOewBAxK0gzpXtIyIwEUqme5zSQwCfXF9f
GTpSpX8k1gWO5M2lXUqBhhI=
=hiPA
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: