On 08/ 3/10 08:39 AM, Simon King wrote:
Hi David,
On 3 Aug., 06:24, "Dr. David Kirkby"<[email protected]> wrote:
But given it was unmerged, should this not be be set to "needs work", rather
than fixed?
Indeed, there never was an "officially" published version of Sage that
contained the patch. So, I think it indeed does not qualify as
"fixed", and also I don't see the point of declaring it "fixed" and
then opening another ticket for re-merging it.
I think normally I would be tempted to reverse this (I have admin rights on
trac), but since it's the release manager that changed it, I am not going to
touch it. I left a note on the ticket though.
But I can't understand how it can be "fixed" if it was not merged.
By the way, the problem with that patch (segfault on t2 but apparently
nowhere else) might be solved with the new singular-3-1-1-4.spkg -- I
am testing this now on t2.
IIRC, it was not only t2 which had that problem. There were later reports of it
on other non-Solaris machines.
But the new Singular update seems to have "stalled". There are reports of
problems and nobody other than me has written anything in the last 8 days on
that ticket.
In fact, I've put back #9397 for review, as that is a much simpler change to the
current version of Singular - just a few lines to permit 64-bit builds on
Solaris/OpenSolaris and does not update the Singular version. The necessary
fixes are in the new Singular update, but that ticket has been open 6 months
now, and is still not concluded. So if Singular does not get updated, I'd like
to get #8059 merged, which I've tested on Linux, OS X, Solaris and OpenSolaris.
I've attached build logs on all systems to the trac ticket.
0.02€,
Simon
Dave
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
