On Jul 13, 10:59 pm, Jaap Spies wrote:
> I think the documentation build system needs some polishing.
It's not really the fault of the documentation build system; it's the
upgrade and clone scripts that are at fault. In particular, the
decision to use hard links for the documentation build sy
Minh Nguyen wrote:
> Hi Jaap,
>
Hi Minh,
> On Tue, Jul 14, 2009 at 7:33 AM, Jaap Spies wrote:
>
>
>
>>> So it is save to do upgrade #81 to my systemwide sage install starting
>>> with sage-1.5.1,2? Latest install is sage-4.0.2.
>>>
>> Replying to myself: I gambled and:
>>
>>
>> [j...@paix ~]
Hi Jaap,
On Tue, Jul 14, 2009 at 7:33 AM, Jaap Spies wrote:
>> So it is save to do upgrade #81 to my systemwide sage install starting
>> with sage-1.5.1,2? Latest install is sage-4.0.2.
>>
>
> Replying to myself: I gambled and:
>
>
> [j...@paix ~]$ sage
> --
Jaap Spies wrote:
> William Stein wrote:
> [...]
>> I've also fixed this in the official upgrade server, so it shouldn't
>> cause trouble to anybody else.
>>
>> Thanks again for reporting this.
>>
>
> So it is save to do upgrade #81 to my systemwide sage install starting
> with sage-1.5.1,2? Late
William Stein wrote:
[...]
>
> I've also fixed this in the official upgrade server, so it shouldn't
> cause trouble to anybody else.
>
> Thanks again for reporting this.
>
So it is save to do upgrade #81 to my systemwide sage install starting
with sage-1.5.1,2? Latest install is sage-4.0.2.
C
On Fri, Jul 10, 2009 at 8:08 AM, Jan Groenewald wrote:
>
> Hi
>
> sage -upgrade 4.0 to 4.1:
>
>
> Finished extraction
>
> Host system
> uname -a:
> Linux hamerkop 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009
> x86_64 GNU/Linux
