Sage 5.4.rc4 and documentation build fine on a fresh install of Ubuntu
12.10 x64, and Sage Cell Server installs and runs without issue from the
above sagecell-2012-11-06.spkg following the same instructions that were
successful for sage-5.4.rc3: http://pastebin.com/xQNgiZxQ
make ptestlong throws no errors after building Sage 5.4.rc4 and the
documentation:
All tests passed!
Total time for all tests: 2283.6 seconds
after installing the patches listed in Sage Trac #12719 (
http://trac.sagemath.org/sage_trac/ticket/12719):
sage -t --long -force_lib devel/sage/sage/interfaces/sage0.py # 1 doctests
failed
sage -t --long -force_lib devel/sage/sage/tests/cmdline.py # 1 doctests
failed
sage -t --long -force_lib devel/sage/sage/misc/sage_extension.py # 1
doctests failed
And then after installing Sage Cell Server:
sage -t --long -force_lib devel/sagenb-main/sagenb/notebook/interact.py #
1 doctests failed
sage -t --long -force_lib devel/sage/doc/en/prep/Programming.rst # 1
doctests failed
sage -t --long -force_lib devel/sage/sage/interfaces/sage0.py # 1
doctests failed
sage -t --long -force_lib devel/sage/sage/misc/sage_extension.py # 1
doctests failed
sage -t --long -force_lib devel/sage/sage/misc/html.py # 12 doctests
failed
sage -t --long -force_lib devel/sage/sage/misc/hg.py # 8 doctests failed
sage -t --long -force_lib devel/sage/sage/misc/misc.py # 13 doctests
failed
sage -t --long -force_lib devel/sage/sage/misc/latex.py # 4 doctests failed
sage -t --long -force_lib devel/sage/sage/interacts/debugger.py # 1
doctests failed
*
Brandon Curtis, PhD Candidate
UC Berkeley - Chem/Bio Eng <http://www.linkedin.com/in/brandoncurtis>
<https://kindle.amazon.com/profile/Brandon-Curtis/5046185>
<https://plus.google.com/u/0/105858766264293200612/about>
<http://brandoncurtis.net>
<http://jbei.org>
*
On Tue, Nov 6, 2012 at 3:26 AM, Brandon Curtis <[email protected]>wrote:
> I've submitted a pull request for the default_config.py memory ceiling
> increase. I also updated 01-sage-embedded.patch and 02-sage-show.patch in
> sagecell to make them compatible with sage-5.4.rc3. I tried to submit
> another pull request for these changes, but that commit seems to be sitting
> on top of my first one. (after thinking about it for a while, this is
> obviously what 'branches' are all about - keep changes of different types
> separate but easily merged)
>
> Poked around in the sagecell directories until I figured out how to
> generate a fresh spkg containing my modified patches. Tested the spkg on a
> freshly-built sage-5.4.rc3 and it works great, so I've attached it to this
> email.
>
> The updated build instructions for sagecell-2012-11-06.spkg on
> sage-5.4.rc3 are available here: http://pastebin.com/edit.php?i=ZHTr4jSQ
>
> I'll get to readme.rst sometime this week. Thanks again!
>
>
> On Sat, Nov 3, 2012 at 7:26 PM, Brandon Curtis
> <[email protected]>wrote:
>
>> On Sat, Nov 3, 2012 at 4:09 PM, Jason Grout
>> <[email protected]>wrote:
>>
>>> On 11/3/12 5:06 PM, Brandon Curtis wrote:
>>>
>>>>
>>>> The proper thing to do is to make a fork on github, push your changes
>>> there, and submit a pull request [1]. I'll probably start compiling rc3
>>> and test your changes against rc3 sometime early next week.
>>>
>>
>> I just compiled rc3 and followed exactly my Sage Cell installation log
>> from rc2, and everything installed and appears to work perfectly.
>>
>>
>>> It looks like your 003 and 002 patches can be combined. That line that
>>> you change in 003 is actually already modified in 002.
>>>
>>
>> Patches 002 and 003 do modify the same line, but in different ways:
>> Patch 002 changes the line so that the sagecell spkg can successfully
>> install 02-sage-show.patch, but the change that 02-sage-show.patch makes is
>> incorrect. Patch 003 is then applied to correct that line. Ideally I
>> would just change 02-sage-show.patch instead of applying patches over
>> patches, but I haven't yet read the docs [1] to learn how to 'crack open'
>> the spkg to modify the individual patches held inside. If I attempt to
>> install the spkg and wait until it fails, then make the changes manually
>> and *hg -qrefresh*, the spkg complains that I 'have an outdated version'
>> of the patch I refreshed. Is it considered better practice to modify
>> existing patches, or to write entirely new patches to fix problems with
>> existing patches?
>>
>>
>>> Also, it would be great if you could submit a pull request to up the
>>> default memory allocation to 2GB. Apparently our initial defaults were way
>>> too low.
>>
>>
>> I'll read the documentation this weekend and hopefully learn enough about
>> git to submit that.
>>
>> Where and in what format can I contribute documentation? A sketch of my
>>>> installation procedure is available here:
>>>> Sage Cell Server 2 on Sage Math 5.4 rc2 - http://pastebin.com/7sBMHGdG
>>>>
>>>
>>> Can you change the existing installation documentation in the readme.rst
>>> file and submit a third pull request?
>>>
>>
>> I assume you mean this repository: https://github.com/sagemath/sagecell.
>> Am I correct to assume that the pre-built (2012-09.25) spkg is up-to-date,
>> since the last major changes to this repository occurred on that date?
>>
>>
>>> Thanks!
>>>
>>> Jason
>>>
>>> [1]
>>> https://help.github.com/**articles/fork-a-repo<https://help.github.com/articles/fork-a-repo>,
>>> https://help.github.com/**articles/using-pull-requests<https://help.github.com/articles/using-pull-requests>,
>>> plus there are lots of other tutorials found by searching for github, fork,
>>> pull request, etc.
>>>
>>>
>> Thanks for helping me get up to speed. I have no formal training in
>> software (I'm a chemical engineer), and I have always felt sort of weird
>> advocating open-source software with very little knowledge of the tools and
>> processes that actually produce it. Glad to finally contribute something
>> concrete.
>>
>> [1] http://www.sagemath.org/doc/developer/producing_spkgs.html
>>
>
>
--
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.
