Hi all, this is not just Lion that is causing trouble. I opened #11619 about problem with building some python bits under a linux-3.0 kernel. Some bits of the building system looks at the major version number of linux to determine that it needs to build stuff in plat-linux2. On linux-3.0 it looks for a non-existent plat-linux3....
There is also the fact that a number of packages check: sys.platform == 'linux2' which will break. Apparently matplotlib has ben fixing a number of these recently. Python upstream is still undecided on what to do: http://bugs.python.org/issue12326 I'll introduce a fix for python-2.7 in #9958 at some point but the current python-2.6 will need fixing and python packages will have to be checked. Francois I see on macos prefix. I think it would be a good idea to get > > m4ri-20110715 and the new m4rie package at the same time. > > http://trac.sagemath.org/sage_trac/ticket/11574 > > http://trac.sagemath.org/sage_trac/ticket/9562 > > > > Christopher could you make ebuilds for these two? I'll handle the > > patches in sage itself during the 4.7.2 cycle, I'll probably push > > upstream as well so we carry the patches for as short a time as > > possible. > > > > I am currently preparing a pari-2.5.0 ebuild and a separate pari-data > > ebuild I'll post silmutaneously in s-o-g and sci. The pari-data will be > > hot so as to avoid manifest problems when upstream update there > > tarballs. > > > > I have also heavily contributed to sage-prefix with Burcin, so far it's > > fun I have built a functional sage-4.7_rc0 but I pushed more recent > > sage now. https://bitbucket.org/burcin/sage-prefix/wiki/Home > > Volker is semi-involved too. There is a chance that this project will > > benefit us in the long run. > > > > Python-2.7 issues, I have to update a few patches and all the build and > > warning stuff is in 4.7.2_alpha0. All that will be left are the patches > > in http://trac.sagemath.org/sage_trac/ticket/9958 > > While some nice stuff has come out of > > http://trac.sagemath.org/sage_trac/ticket/11339 > > It seems no matter how we squeeze libsingular some breakage appears > > somewhere else. > > > > There is a sympy 0.7.1 coming out fast which will include all the > > current > > patches so I'll wait until it's out before asking Andrey Grozin to > > incorporate a few of our changes in. He is very helpful. > > > > What are you guys up to? Do you have any worries or suggestions on > > things > > we should be doing? > > > > Cheers, > > Francois > > > > This email may be confidential and subject to legal privilege, it may > > not reflect the views of the University of Canterbury, and it is not > > guaranteed to be virus free. If you are not an intended recipient, > > please notify the sender immediately and erase all copies of the message > > and any attachments. > > > > Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more > > information. > > Hi, > > first of all, thank you for the informative summary! > > I am also busy with work because I started my PhD last month (now I get paid > > :) !) and I am going to relocate to Mainz but there is still enough time > :left > > that I can dedicate to our project. > > I thought about regular (?) meetings at #gentoo-science so we can coordinate > the work and issues - I have to admit that I do not always exactly know > what has to be done. > > I will commit ebuilds for m4ri(e) commit shortly. > > Regarding plans for the future, I still think of lowering the number of > dependencies by making them optional with USE flags (I think this is still > the biggest hurdle of Sage). However, I am not sure if or to what extent > this can be done. > Hi, that's good to know that you have some time. For irc meetings the main problem is time zone. I am on New Zealand time and I am currently unable to do irc from 5pm-1am (and at that time I should really go to bed). Other people's time zone and schedule have to be considered. One current problem I forgot to mention is jmol. We need to move to jmol 12 there is will in sage to so as well. jmol 11 is broken on variety of newer browsers so we need to move to 12. I have applied some patch to sagenb to use jmol-12.0.45 in sage-notebook-0.8.19 but it is broken. Someone needs to look at it. The patches may need a refresh to latest version in http://trac.sagemath.org/sage_trac/ticket/9238 Note that jmol is about to get a separate spkg as well: http://trac.sagemath.org/sage_trac/ticket/11503 Francois (snow is falling tonight, haven't seen a snowfall since 2002) This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information. -- 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
