On Wed, 2009-08-05 at 19:50 +0100, Chris Lamb wrote:
Adam C Powell IV wrote:
Why don't I upload with your patch, and wait for Dan Wheeler to make a
new release rather than packaging a snapshot?
Up to you of course, but I'd actually forget my patch and upload a snapshot
right now and
Adam C Powell IV wrote:
Okay, and with the squeeze freeze on the way, I'll try to get to this
sooner rather than later.
Or, since I'm no longer a user of this package, feel free to change the
Maintainer to pkg-scicomp or something similar, with me and you as
Uploaders, and upload
On Wed, 2009-08-05 at 14:29 +0100, Chris Lamb wrote:
Adam C Powell IV wrote:
Okay, and with the squeeze freeze on the way, I'll try to get to this
sooner rather than later.
Or, since I'm no longer a user of this package, feel free to change the
Maintainer to pkg-scicomp or something
Adam C Powell IV wrote:
Why don't I upload with your patch, and wait for Dan Wheeler to make a
new release rather than packaging a snapshot?
Up to you of course, but I'd actually forget my patch and upload a snapshot
right now and then upload the new tarball when it appears. It's not as if
severity 535318 important
forwarded 535318 http://sourceforge.net/mailarchive/forum.php?forum_id=28092
thanks
This is important, but not grave -- the package has other users who
haven't run into this problem, and data loss generally refers to
corrupting or erasing on-disk data.
Thanks for the
Adam C Powell IV wrote:
Thanks for the report, forwarded it upstream.
Hm, I don't see it on the link you've specified.
Can you even reproduce it? Running through my schroots, I spot a pattern:
sid-amd64 pass
sid-i386 fail
squeeze-amd64 pass
squeeze-i386 fail
lenny-amd64
tags 535318 + patch
thanks
Chris Lamb wrote:
Can you even reproduce it?
Traceback (and patch) attached, but that's only because I'm stubborn. The
real solution is to package an upstream snapshot.
Upstream is not dead, they just haven't made a release in a while. Plus (as
Oz is finding out)
Hi Chris,
On Tue, 2009-08-04 at 20:55 +0100, Chris Lamb wrote:
Adam C Powell IV wrote:
Thanks for the report, forwarded it upstream.
Hm, I don't see it on the link you've specified.
Yeah, SF seems to be having email trouble. It's that (1) link in August
-- but it's currently broken. I
Package: python-sparse
Version: 1.0.1-5+b1
Severity: grave
Justification: renders package unusable
I installed python-and often when I ran code involvind it, it causes
segmentation faults.
I hope this helps,
Thanks, Oz.
here's an example which causes that:
from numpy import *
from pysparse
9 matches
Mail list logo