Le jeudi 24 janvier 2013 21:01:33 UTC+1, Emmanuel Charpentier a écrit :
> [ Snip... ]
> > Any advice ?
>
>> Go for it! Create a Trac ticket and post a new spkg.
>>
>
> I will do that. But not immediately : RealLife(TM) has its exigences...
>
> [ Later ] almost done :
dropping the new source code was a breeze. I had to delete the
install_parallel patch, which does something already in the new source.
Installation was uneventful, and the new code do fix my gripe : rjags and
coda can be installed now, and seem functional.
However, I have two ptestlong failures, (both expectable in hindsight...) :
sage -t --long -force_lib devel/sage/sage/interfaces/r.py
**********************************************************************
File "/home/sage/sage-5.6/devel/sage-main/sage/interfaces/r.py", line 555:
sage: r.version()
Expected:
((2, 14, 0), 'R version 2.14.0 (2011-10-31)')
Got:
((2, 15, 2), 'R version 2.15.2 (2012-10-26)')
**********************************************************************
File "/home/sage/sage-5.6/devel/sage-main/sage/interfaces/r.py", line 2049:
sage: r.version()
Expected:
((2, 14, 0), 'R version 2.14.0 (2011-10-31)')
Got:
((2, 15, 2), 'R version 2.15.2 (2012-10-26)')
**********************************************************************
2 items had failures:
1 of 4 in __main__.example_16
1 of 4 in __main__.example_80
***Test Failed*** 2 failures.
I do not (yet) know where to find these doctests and how to present the
relevant patches. Any pointers ? My view of the sage development process is
not yet absolutely clear...
Emmanuel
> Charpentier
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.
