Hi David, On Thu, Jan 28, 2010 at 10:05 PM, Dr. David Kirkby <[email protected]> wrote:
<SNIP> > That will not work. I tried to build Sage 4.3.1.alpha1 and it failed on my > home machine. I think sage 4.3 with > > http://trac.sagemath.org/sage_trac/ticket/8088 Do you mean ticket #6595? http://trac.sagemath.org/sage_trac/ticket/6595 > added is the safest option. 4.3 should hopefully be a 'stable' release, > whereas the alphas are less so. > > Hence I think whatever changes took place that broke the Solaris 10 build, > occurred between 4.3 and 4.3.1.alpha1. As far as I know, alpha0 and alpha1 > were the same, except one package was duplicated. Here's another version: http://sage.math.washington.edu/home/mvngu/sage-src/sage-4.3.0.1.tar It's based on Sage 4.3 with the patch at #6595. To help narrow down where a build on t2.math would fail, I'm dividing various tickets closed in Sage 4.3.1.alpha1 into 9 batches: * sage-4.3.0.1.alpha0: #6425, #6772, #7799, #7775, #7772 * sage-4.3.0.1.alpha1: #7770, #7692, #7749, #7768, #7728 * sage-4.3.0.1.alpha2: #7704, #7548, #7616, #7754, #7620 * sage-4.3.0.1.alpha3: #5174, #1321, #6595, #6820, #6965 * sage-4.3.0.1.alpha4: #7482, #7724, #7678, #7388, #7483 * sage-4.3.0.1.alpha5: #7514, #7097, #7279, #7834, #7745 * sage-4.3.0.1.alpha6: #6423, #4142, #7271, #6583, #6887 * sage-4.3.0.1.alpha7: #7505, #7769, #7779, #7783 * spkg updates: #7138, #7162, #7696, #7697, #7699, #7732, #7796, #7817, #7825, #7840 The order of the tickets is the order in which I think their corresponding patches were merged in Sage 4.3.1.alpha1, except for the tickets with spkg updates/upgrades. I can't work out precisely when those tickets with spkg updates/upgrades were merged. For example, if ticket T1 only has patch(es) for the Sage library and ticket T2 has an updated spkg, was the patches in T1 merged before or after the spkg in T2? Now back to the 9 batches of tickets above. Starting from Sage 4.3, one could produce, say, 9 releases with patches on top of it. For example, Sage 4.3.0.1.alpha0 would contain patches from the listed tickets. Sage 4.3.0.1.alpha1 would be based on Sage 4.3.0.1.alpha0 with patches from the listed tickets. And so on. One then builds each alpha release on t2.math and see which one fails. I admit this is tedious, especially the process of applying patches. But it's one way to find out which alpha release and hence which batch of tickets results in a build failure on t2.math. I'm implementing this plan and will report results in a day or two. (Building Sage on t2.math takes about a day.) -- Regards Minh Van Nguyen -- 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
