Your message dated Fri, 07 Mar 2008 10:02:10 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#469007: fixed in thuban 1.2.0-2.1
has caused the Debian Bug report #469007,
regarding thuban: 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.)


-- 
469007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469007
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: thuban
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: thuban
Source-Version: 1.2.0-2.1

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

thuban_1.2.0-2.1.diff.gz
  to pool/main/t/thuban/thuban_1.2.0-2.1.diff.gz
thuban_1.2.0-2.1.dsc
  to pool/main/t/thuban/thuban_1.2.0-2.1.dsc
thuban_1.2.0-2.1_i386.deb
  to pool/main/t/thuban/thuban_1.2.0-2.1_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.
Barry deFreese <[EMAIL PROTECTED]> (supplier of updated thuban 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: Mon, 03 Mar 2008 15:28:25 -0500
Source: thuban
Binary: thuban
Architecture: source i386
Version: 1.2.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Changed-By: Barry deFreese <[EMAIL PROTECTED]>
Description: 
 thuban     - an interactive geographic data viewer
Closes: 469007
Changes: 
 thuban (1.2.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * pymem_del.dpatch. (Closes: #469007).
     + Use PyObject_Del instead of PyMem_DEL.
Files: 
 a353f33451c82b00b12d4e003c446a9b 860 graphics extra thuban_1.2.0-2.1.dsc
 4b6c087db2859482da807edbcf6cdba9 7749 graphics extra thuban_1.2.0-2.1.diff.gz
 da41b29efb4dd2d30fccbd637ec929e9 798284 graphics extra 
thuban_1.2.0-2.1_i386.deb

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

iD8DBQFH0Hj3riZpaaIa1PkRAv3KAJ0bH3qwN2G+0Vo48/uLlaUYCAZo5wCfV0wo
G0sOPNNaDeVq4Km20db1Nrg=
=0pAU
-----END PGP SIGNATURE-----



--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

Reply via email to