Your message dated Thu, 10 Aug 2006 16:18:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380936: fixed in routeplanner 0.19
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: routeplanner
Version: 0.18
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 [email protected] ,
     - tag your bug + help ,
     - come on #debian-python/OFTC.



--- End Message ---
--- Begin Message ---
Source: routeplanner
Source-Version: 0.19

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

routeplanner-gnome_0.19_all.deb
  to pool/main/r/routeplanner/routeplanner-gnome_0.19_all.deb
routeplanner_0.19.dsc
  to pool/main/r/routeplanner/routeplanner_0.19.dsc
routeplanner_0.19.tar.gz
  to pool/main/r/routeplanner/routeplanner_0.19.tar.gz
routeplanner_0.19_all.deb
  to pool/main/r/routeplanner/routeplanner_0.19_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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lawrence <[EMAIL PROTECTED]> (supplier of updated routeplanner 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, 10 Aug 2006 17:54:22 -0500
Source: routeplanner
Binary: routeplanner-gnome routeplanner
Architecture: source all
Version: 0.19
Distribution: unstable
Urgency: low
Maintainer: Chris Lawrence <[EMAIL PROTECTED]>
Changed-By: Chris Lawrence <[EMAIL PROTECTED]>
Description: 
 routeplanner - A highway trip planner
 routeplanner-gnome - A highway trip planner (GNOME interface)
Closes: 380936
Changes: 
 routeplanner (0.19) unstable; urgency=low
 .
   * Update for Python transition.  (Closes: #380936)
   * Apply diffs from Shawn Quinn.
Files: 
 3da97042e969ae5472f5b1dfd51c3d6f 627 misc optional routeplanner_0.19.dsc
 ca9b9acc6984a1b90676915a453caebf 361617 misc optional routeplanner_0.19.tar.gz
 4ecd307a10384858e59708801e1953d9 292106 misc optional routeplanner_0.19_all.deb
 5aa36647452f784bb953261cb4a8fbe0 36906 gnome optional 
routeplanner-gnome_0.19_all.deb

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

iD8DBQFE27o62wQKE6PXubwRArrvAKCJwTN/LrlkfhiQJpHznE2btUPuEQCdGXk2
0d8sU791KT7fIqKOvKNm1Qs=
=Tzuo
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to