On Wed, Nov 25, 2009 at 7:34 AM, Florent Hivert
<florent.hiv...@univ-rouen.fr> wrote:
> Hi Michel,
>
>> On Nov 25, 1:15 pm, Michel <michel.vandenbe...@uhasselt.be> wrote:
>> > Too bad. I really need those determinants. Will
>> >
>> > sage -upgrade
>> >
>> > magically put things right for me?
>>
>> Probably. I can confirm that in 4.2.1 the problem does not occur.
>>
>> > I feel hesitant to spend another day compiling sage.
>>
>> An upgrade should be *much* faster than a complete build from scratch!
>
> This is especially true since since sage-4.2.1 in only a bug-fix release from
> sage-4.2. Nevertheles, if you want a much cheaper fixes you can just apply the
> two patches from #5639.
>
> hg_sage.patch("http://trac.sagemath.org/sage_trac/raw-attachment/ticket/5639/trac_5639.patch";)
> hg_sage.patch("http://trac.sagemath.org/sage_trac/raw-attachment/ticket/5639/trac-5639-doctest.patch";)
>
> and then restart sage with sage -br.
>
> Note: I'm not sure what will happen if you then try to upgrade without
> unapplying the patches. probably nothing...
It should be fine, assuming one understands hg at all. Upgrading just
does "hg pull", so properly merges in only changes, unless there are
conflicts, which there won't be in this case.
William
--
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
