Hi Pierre,

> ok, so it failed with :

You didn't answer John's crucial question :

> What version of sage are you running?  If it was 4.3.5 then you could
> do the following.  Start in the directory where sage is installed
> (usually called SAGE_ROOT).  I assume that this sage is in your path.

If it's not exactly the right one, then you probably need some more patch to 
import.
We can probably tell you but we have to kwnow the precise version of sage you
have. Since John is claiming that the patch correctly applies on 4.3.5 and
reading the log on trac "Rebase to 4.3.3" I think the patch should correctly
apply on 4.3.3, 4.3.4 and 4.3.5. Any other version should be some kind of
miracle. 

Cheers,

Florent

> m-guillot:sage-ratfunc pedro$ hg qpush
> applying trac4000_433_combined.patch
> patching file sage/libs/flint/fmpz_poly.pxi
> Hunk #1 FAILED at 2
> Hunk #3 FAILED at 109
> 2 out of 3 hunks FAILED -- saving rejects to file sage/libs/flint/
> fmpz_poly.pxi.rej
> patching file sage/rings/fraction_field_element.pyx
> Hunk #2 FAILED at 5
> Hunk #8 succeeded at 948 with fuzz 2 (offset -207 lines).
> 1 out of 8 hunks FAILED -- saving rejects to file sage/rings/
> fraction_field_element.pyx.rej
> patching file sage/rings/polynomial/polynomial_element_generic.py
> Hunk #1 FAILED at 604
> 1 out of 1 hunks FAILED -- saving rejects to file sage/rings/
> polynomial/polynomial_element_generic.py.rej
> patching file sage/schemes/elliptic_curves/ell_curve_isogeny.py
> Hunk #1 FAILED at 4183
> 1 out of 1 hunks FAILED -- saving rejects to file sage/schemes/
> elliptic_curves/ell_curve_isogeny.py.rej
> patch failed, unable to continue (try -v)
> patch failed, rejects left in working dir
> errors during apply, please fix and refresh
> trac4000_433_combined.patch

-- 
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

Reply via email to