> On 06/ 6/10 10:53 AM, François Bissey wrote: > >>> You could also try > >>> > >>> sage -ba > >>> > >>> which will rebuild from scratch all Cython code. > >> > >> OK I will give it a go. > > > > No improvement. I am considering this upgrade officially failed > > on my machine. > > > > Francois > > Can anyone tell me what happens in a 'sage -upgrade'? I'm puzzled why this > can't be made to work. I would have thought as a minimum one would need to > > 1) Rebuild any new standard packages. > 2) Rebuild any standard package which depends on another package which has > been upgraded. > 3) Rebuild the library. > > Is '(2)' being done? If not, I suspect it would be more reliable. I would think it is done that way. Although sometimes there are difficulties. It's possible that I didn't actually found the right culprit in this case. pynac only depends on python so there's not much to rebuild. The list of updated package is very short so this is puzzling but bugs in upgrading system happen. Possibly in this case something went subtly wrong from 4.4.1->4.4.2->4.4.3
Note that 1) is actually divided into two parts: 1) Rebuild any new standard packages that sage depends on. 4) rebuild any new standard package that is a runtime dependency. in this case scipy* was rebuilt last. >From my work in sage-on-gentoo I don't think the separation between 1 and 4 is accurate in sage, but nothing that should be in 1 is in 4 so that's OK. Francois -- 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
