Your message dated Sun, 01 Oct 2006 15:47:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380960: fixed in spkproxy 1.4.8-4
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: spkproxy
Version: 1.4.8-3
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: spkproxy
Source-Version: 1.4.8-4
We believe that the bug you reported is fixed in the latest version of
spkproxy, which is due to be installed in the Debian FTP archive:
spikeproxy_1.4.8-4_all.deb
to pool/main/s/spkproxy/spikeproxy_1.4.8-4_all.deb
spkproxy_1.4.8-4.diff.gz
to pool/main/s/spkproxy/spkproxy_1.4.8-4.diff.gz
spkproxy_1.4.8-4.dsc
to pool/main/s/spkproxy/spkproxy_1.4.8-4.dsc
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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated
spkproxy 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: Sun, 1 Oct 2006 23:51:39 +0200
Source: spkproxy
Binary: spikeproxy
Architecture: source all
Version: 1.4.8-4
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description:
spikeproxy - Web application security testing proxy
Closes: 380960 385390
Changes:
spkproxy (1.4.8-4) unstable; urgency=low
.
* Acknowledge NMU, thanks Ana for the patch. (Closes: #380960)
* Package rebuild makes it depend on python version 2.4 (Closes: #385390)
* Add a new -c option to define the proxy's cache for users, this makes
it easier to define an alternate location for cachedir so that
administrators do not have to fiddle with the permissions of
/var/cache/spikeproxy
* Introduce all the options into the manpage, including the new -c option.
(it previously said there was only one option, which is no longer true)
* Introduce a new function in spikeProxyUI.py to setCache() that checks
if the cache directory exists and is writable. Previously it will only
check if it existed and would not complain about it not being writable
until you browsed through the proxy. This makes the error message
of the cachedir not being useful for the user appear as soon as the
program startups.
* Remove all compile Python files under ntlm/. This makes it possible
to rebuild the package after running spikeproxy locally (within
package sources)
Files:
909c1635a1898ca2173ff8532b4818f1 768 net optional spkproxy_1.4.8-4.dsc
a19bc5aa2f083c114534099aca37b6e8 10278 net optional spkproxy_1.4.8-4.diff.gz
d811acdb01695b9e19477411702f0bb9 678258 net optional spikeproxy_1.4.8-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iQCVAwUBRSBE0/tEPvakNq0lAQJWRAP/WZ08p5IbGvK/YYAAbAtjGweEdaCVc7QR
XerCkgVzIANk4CGkaTm0A286ZMRnpHaDiPniX+P9VhipizuQNn1lBgRV6q0c0uK+
MIDl4ANZZHd5qucS+Nol0Qv9v7RpBKo75C24tHv7gllPsFzo0HI9L6k3PQX4Bkso
bMbWnnNSA6g=
=imAM
-----END PGP SIGNATURE-----
--- End Message ---
