Your message dated Sun, 16 Mar 2008 13:47:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#468989: fixed in pymol 1.1~beta3-2 has caused the Debian Bug report #468989, regarding pymol: 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.) -- 468989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468989 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: pymol 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: pymol Source-Version: 1.1~beta3-2 We believe that the bug you reported is fixed in the latest version of pymol, which is due to be installed in the Debian FTP archive: pymol_1.1~beta3-2.diff.gz to pool/main/p/pymol/pymol_1.1~beta3-2.diff.gz pymol_1.1~beta3-2.dsc to pool/main/p/pymol/pymol_1.1~beta3-2.dsc pymol_1.1~beta3-2_i386.deb to pool/main/p/pymol/pymol_1.1~beta3-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. Michael Banck <[EMAIL PROTECTED]> (supplier of updated pymol 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, 16 Mar 2008 14:26:06 +0100 Source: pymol Binary: pymol Architecture: source i386 Version: 1.1~beta3-2 Distribution: unstable Urgency: low Maintainer: Debichem Team <[EMAIL PROTECTED]> Changed-By: Michael Banck <[EMAIL PROTECTED]> Description: pymol - An OpenGL Molecular Graphics System written in Python Closes: 468989 Changes: pymol (1.1~beta3-2) unstable; urgency=low . * debian/patches/16_pymem_del.dpatch: Fix usage of different memory APIs; by Barry deFreese; closes: #468989. Files: 084c9f16c63d357cb1df69294ff8a310 933 science optional pymol_1.1~beta3-2.dsc c0a4aeeb876e2afc9d10a1ebc46d746f 20473 science optional pymol_1.1~beta3-2.diff.gz 954cf44e1c82da445f2ab73341cc8ef7 6116324 science optional pymol_1.1~beta3-2_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFH3SKsmHaJYZ7RAb8RAmzsAKDN0WNLpjb/sQ3Ar8QeLpvO1ScCVgCfU7Rx 5j4LP2+1k74aLF8f/2VCNs0= =qwm+ -----END PGP SIGNATURE-----
--- End Message ---
