On Mon, Nov 15, 2010 at 10:41 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2010-11-15 17:23, Dr. David Kirkby wrote: >> But surely if a bug is found, it should be on trac. > > Should a PARI bug be on the Sage Trac? What's the point if it already > was reported to PARI?
I think the point is that another Sage user might come up against the bug without knowing that it was caused by an upstream bug. > > Anyway, if you want you can go ahead and make the ticket but there is > not much we can do anyway besides waiting for PARI to fix the problem... > When the bug is fixed upstream, Sage will have to change -- by upgrading its PARI spkg. And that needs a ticket! John > > Jeroen. > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
