Re: [Pysparse-developers] Bug from Debian user

[Daniel W. <dan...@gm...>]

Hi Adam, Hope all is well. Isn't it probably best to the deb release
from an official pysparse release? The latest release is 1.0.1, which
at this stage is a little old. So, maybe we should do a pysparse
release and then do the deb.

Dominque, Shall I go ahead and do that? The version number probably
needs bumping to 1.1 as there are a lot of extra features that you've
added, but a script that uses 1.0 will probably still work with 1.1.
Right?

On Tue, Aug 4, 2009 at 7:47 PM, Adam C Powell IV<haz...@de...> wrote:
> On Tue, 2009-08-04 at 19:14 -0400, Dominique Orban wrote:
>> 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.
>
> I'd be happy to package the SVN tree, I do that also for Elmer.  But an
> occasional release would be nice, whenever is convenient for you.
>
>>         > 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.
>
> Great, thanks.  My .deb has been in unstable for almost three years now,
> and released as part of Lenny (5.0).  I think it's also been in Ubuntu
> universe since Hardy Heron (8.04), maybe even Gutsy Gibbon (7.10).
>
> -Adam
> --
> GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6
>
> Engineering consulting with open source tools
> http://www.opennovation.com/
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Pysparse-developers mailing list
> Pys...@li...
> https://lists.sourceforge.net/lists/listinfo/pysparse-developers
>
>



-- 
Daniel Wheeler