Thomas Viehmann
2008-Mar-07 01:58 UTC
[Pkg-xen-devel] Bug#469013: bug lies in (presently) unused code path
user debian-release at lists.debian.org usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/ext2/ext2module.c) is not actually compiled and the results shipped[1]. As such, while a fix still seems to be worthwile it does not affect the python2.5 release goal. I am thus removing the usertag. Just be that it does not get activated its present buggy form. (CCing debian-python because the bugs will disappear from the release-goal list.) Kind regards T. 1. It should compile a module _ext2, I did not find any indication that it is contained in the binary packages.
Debian Bug Tracking System
2008-Mar-07 02:00 UTC
[Pkg-xen-devel] Processed: bug lies in (presently) unused code path
Processing commands for control at bugs.debian.org:> user debian-release at lists.debian.orgSetting user to debian-release at lists.debian.org (was tv at beamnet.de).> usertag 469013 -goal-python2.5Bug#469013: xen-unstable: may use different memory API for a given memory block Usertags were: goal-python2.5. Usertags are now: .> retitle 469013 Python API memory handling bug in unused code pathBug#469013: xen-unstable: may use different memory API for a given memory block Changed Bug title to `Python API memory handling bug in unused code path' from `xen-unstable: may use different memory API for a given memory block'.> found 469013 3.0-unstable+hg11561-1Bug#469013: Python API memory handling bug in unused code path Bug marked as found in version 3.0-unstable+hg11561-1.> thanksStopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)