[sage-devel] Re: please schedule a rebuild for sagemath on alpha architecture

2010-08-07 Thread tabbott
On Fri, 6 Aug 2010, kamaraju kusumanchi wrote: > > Kamaraju, > > > > Overall I like your plan.  And I'd like to help. > > > > I do not like starting with version 3.0.6.  I think such an old version > > is unlikely to attract many users and hence testing will be suboptimal. > > In addition, upstrea

[sage-devel] Re: please schedule a rebuild for sagemath on alpha architecture

2010-08-07 Thread tabbott
On Fri, 6 Aug 2010, kamaraju kusumanchi wrote: > > Removing the package from unstable doesn't prevent you from working on > > the package. It's just a way to clean up Debian. It will be very easy to > > re-upload when you will have something that builds in i386 and amd64 > > (though it might be be

[sage-devel] Re: Questions about various spkgs

2008-05-10 Thread tabbott
Okay, I will not bother submitting the flintqs package to Debian, since it sounds like things may move to flint entirely before the SAGE package makes it into Debian upstream anyway. -Tim Abbott On May 8, 10:02 am, Bill Hart <[EMAIL PROTECTED]> wrote: > The new quadratic sieve included

[sage-devel] Re: Questions about various spkgs

2008-05-10 Thread tabbott
On May 8, 5:46 am, Clement Pernet <[EMAIL PROTECTED]> wrote: > Rumors are always true! > I meant to merge linbox_wrap in linbox/interfaces for the 2.0 linbox > release. Depending on how urgent is your need for this to happen, I may > consider doing it in a 1.1.6 release instead. What's the times

[sage-devel] Re: SAGE 3.0alpha6 Debian package issues

2008-05-03 Thread tabbott
It turns out the singular problem was that /usr/lib/libsingular.so has to be marked as executable for Singular to load it. The LinBox problem went away when I upgraded to 3.0.1alpha1. -Tim Abbott On Apr 26, 9:28 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 27, 2:57 am, T

[sage-devel] Re: Debian package build failure for gfan with 3.0.1alpha1

2008-05-02 Thread tabbott
On May 2, 7:31 pm, Francois <[EMAIL PROTECTED]> wrote: > I got it! -IGMPRATIONAL should be -DGMPRATIONAL > Do not know where that came from in your package. > > Francois Indeed; that was a typo in my package introduced when I fixed a different bug. It would have probably taken me a long time to