Your message dated Wed, 05 Mar 2008 18:02:33 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468985: fixed in pyao 0.82-2
has caused the Debian Bug report #468985,
regarding pyao: may use different memory API for a given memory block
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
468985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468985
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pyao
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5
The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file. This may be a real problem, or a false
positive.
The most common error seen is of the form:
PyObject *
new_wadobject(WadFrame *f, int count) {
wadobject *self;
self = PyObject_NEW(wadobject, &WadObjectType);
[...]
}
static void
wadobject_dealloc(wadobject *self) {
PyMem_DEL(self);
}
This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.
For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html
Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive. Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz
--- End Message ---
--- Begin Message ---
Source: pyao
Source-Version: 0.82-2
We believe that the bug you reported is fixed in the latest version of
pyao, which is due to be installed in the Debian FTP archive:
pyao_0.82-2.diff.gz
to pool/main/p/pyao/pyao_0.82-2.diff.gz
pyao_0.82-2.dsc
to pool/main/p/pyao/pyao_0.82-2.dsc
python-pyao_0.82-2_i386.deb
to pool/main/p/pyao/python-pyao_0.82-2_i386.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.
Thomas Viehmann <[EMAIL PROTECTED]> (supplier of updated pyao 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: Tue, 04 Mar 2008 23:12:54 +0100
Source: pyao
Binary: python-pyao
Architecture: source i386
Version: 0.82-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Thomas Viehmann <[EMAIL PROTECTED]>
Description:
python-pyao - A Python interface to the Audio Output library
Closes: 468985
Changes:
pyao (0.82-2) unstable; urgency=high
.
* QA upload.
* Fix python memory handling. Closes: #468985.
* Set Maintainer to QA Group.
* Bump standards to 3.7.3 (No changes).
* Introduce debheler debian/compat
* Enhance debian/copyright.
Files:
53a529c67387316fb89f1a47353a69e7 661 python extra pyao_0.82-2.dsc
85a52daa94cdc160561c17e662553b62 2261 python extra pyao_0.82-2.diff.gz
05b0f64f184a32a7e89d20a61118eecf 11300 python extra python-pyao_0.82-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHzt6/riZpaaIa1PkRAuvwAJ9Sk/cyHUj2mZExPvmCzj//zV9pjgCfaAVg
s7WHoRV2RsU9LeqoYIJDHM4=
=KKJ7
-----END PGP SIGNATURE-----
--- End Message ---
