From: Dominique O. <dom...@gm...> - 2009-08-04 23:14:47
|
On Tue, Aug 4, 2009 at 6:44 PM, Adam C Powell IV <haz...@de...>wrote: > On Tue, 2009-08-04 at 12:12 -0400, Dominique Orban wrote: > > On Tue, Aug 4, 2009 at 9:37 AM, Adam C Powell IV <haz...@de...> > > wrote: > > Hi, > > > > The following segfault-inducing code came in from a user > > (details at > > http://bugs.debian.org/535318 ): > > > > from numpy import * > > from pysparse import * > [snip] > > Segmentation fault > > > > Any ideas? Bug in user's code, pysparse, or Debian packaging? > > Hi, > > > > > > Thanks for the report. Lots of bugs in user's code. Still Pysparse > > should not have crashed with a segfault. I have now added appropriate > > argument checking. > > Thank you. Any idea when a new release might happen? I updated the Pysparse svn repository earlier today (revision 124). Oz's code now terminates with appropriate error messages. What is best for you? Are you able to grab the svn tree to package the source into a deb or would you rather a tar.gz of the source tree? I admit I've been relying on svn so far and haven't released the source tree much. > > The user who reported the bug is also the author of the Deb package. > > He says he will fix the package soon. > > Sorry I wasn't clear: the package author is me, the user who reported > this is Oz Nahum (or Nahum Oz?). Ah I misunderstood that. Oz was trying to package Pysparse into a deb at some point, which is why I thought he was still the package author. Thank you for your help. I'll mention on the website that a deb is now available. -- Dominique |