On Wednesday, June 9, 2010, Dima Pasechnik wrote:
> Well, I saw upgrades fail repeatedly, and William was writing here
> that -upgrade is basically not ready
> for prime time use.
>
> Indeed, one needs to have at least an spkg dependencies mechanism in
> place, before -upgrade
> can be done in a f
On 6 June 2010 11:47, François Bissey wrote:
>> 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 upgra
> 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.
> >
> > Fra
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 -up
> > 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
--
To post to this group, send an email to sage-devel@googlegroups.c
> You could also try
>
>sage -ba
>
> which will rebuild from scratch all Cython code.
OK I will give it a go.
> If you have an SMP machine, do
>export MAKE="make -j10"
> , where 10 is the number of cores, first. For example, on
> sage.math.washington.edu, I
> do "make -j24" and can bui
On Sat, Jun 5, 2010 at 11:49 PM, François Bissey
wrote:
>> It couldn't hurt to force a rebuild of pynac (or failing that Python).
>>
>> sage -f pynac-0.2.0.p3
>>
>>
>> Fortunately, whatever happened isn't going to happen to *everybody*.
>> I tested upgrading from 4.4.2 to 4.4.3 on our developme
> It couldn't hurt to force a rebuild of pynac (or failing that Python).
>
>sage -f pynac-0.2.0.p3
>
>
> Fortunately, whatever happened isn't going to happen to *everybody*.
> I tested upgrading from 4.4.2 to 4.4.3 on our development server, and
> it worked fine.
No luck with that. I even tr
On Sat, Jun 5, 2010 at 9:41 PM, François Bissey wrote:
> ./sage
> --
> | Sage Version 4.4.3, Release Date: 2010-06-04 |
> | Type notebook() for the GUI, and license() for information. |
> -
./sage
--
| Sage Version 4.4.3, Release Date: 2010-06-04 |
| Type notebook() for the GUI, and license() for information.|
--
--
10 matches
Mail list logo
