That seems to have worked, thanks!

The question remains, though: is the failure of the method documented in 
the installation guide a bug in the installation or in the guide?


On Friday, January 29, 2016 at 2:25:44 PM UTC-5, Volker Braun wrote:
>
> Ok forgot quotes:
>
> branch: "6.10"
>
> On Friday, January 29, 2016 at 7:37:23 PM UTC+1, mjs wrote:
>>
>> Thanks. Now fails with 
>>
>> /home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/activate 
>> python -m binary_pkg.cmdline --config sage.yaml --checkout
>> Namespace(build=False, checkout=True, config='sage.yaml', debug=False, 
>> dist=False, info=False, log=None, option_help=False, package='', 
>> stage=False)
>> Traceback (most recent call last):
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
>>  
>> line 170, in _run_module_as_main
>>     "__main__", mod_spec)
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
>>  
>> line 85, in _run_code
>>     exec(code, run_globals)
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/binary_pkg/cmdline.py", line 
>> 78, in <module>
>>     launch()
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/binary_pkg/cmdline.py", line 
>> 67, in launch
>>     git_clone(config)
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/binary_pkg/git_interface.py", 
>> line 15, in git_clone
>>     'git', 'clone', config.repository, '-b', config.branch, 
>> config.source_path
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
>>  
>> line 556, in check_call
>>     retcode = call(*popenargs, **kwargs)
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
>>  
>> line 537, in call
>>     with Popen(*popenargs, **kwargs) as p:
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
>>  
>> line 859, in __init__
>>     restore_signals, start_new_session)
>>   File 
>> "/home/mjs/src/binary-pkg-master/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
>>  
>> line 1395, in _execute_child
>>     restore_signals, start_new_session, preexec_fn)
>> TypeError: Can't convert 'float' object to str implicitly
>> make[1]: *** [checkout-sage] Error 1
>> make[1]: Leaving directory `/home/mjs/src/binary-pkg-master/binary-pkg'
>> make: *** [package-sage] Error 2
>>
>> Works if I don't change the branch, but doesn't build the right version.
>>
>> On Friday, January 29, 2016 at 12:36:24 PM UTC-5, Volker Braun wrote:
>>>
>>> Open sage.yaml and replace
>>>
>>>     branch: develop
>>>
>>> with 
>>>
>>>     branch: 6.10
>>>
>>>
>>>
>>> On Friday, January 29, 2016 at 5:21:36 PM UTC+1, mjs wrote:
>>>>
>>>> So the Sage installation documentation that says that moving the tree 
>>>> and then running as root will fix everything is no longer correct? 
>>>>
>>>> Is there a step-by-step direction for building Sage with binary-pkg?  I 
>>>> tried downloading the binary-pkg zip file, but make complained that there 
>>>> was no Git repository, so I cloned the binary-pkg Git repo and typed 'make 
>>>> package-sage'. It appears to have built a tarball for sage-7.1 for my 
>>>> platform, but I wanted 6.10. It's not immediately apparent how to specify 
>>>> the version number.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Wednesday, January 27, 2016 at 2:53:48 PM UTC-5, Volker Braun wrote:
>>>>>
>>>>> Either compile Sage in place, or use 
>>>>> https://github.com/sagemath/binary-pkg 
>>>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fsagemath%2Fbinary-pkg&sa=D&sntz=1&usg=AFQjCNEnRuZWLIPZdOQL7_t0kfK9mesuvw>
>>>>>  
>>>>> to build a special relocatable version.
>>>>>
>>>>>
>>>>> On Wednesday, January 27, 2016 at 12:18:49 PM UTC-5, mjs wrote:
>>>>>>
>>>>>> It seems that at least some hard-coded paths are not repaired when  
>>>>>> the Sage directory tree is relocated.
>>>>>>
>>>>>> I built sage in my home directory, installed some optional packages, 
>>>>>> moved the whole tree to /usr/local/sage-6.10 and ran sage as root. Sage 
>>>>>> reported updating the hard-coded paths, but when I run the notebook 
>>>>>> server 
>>>>>> and attempt to plot, I get an error:
>>>>>>
>>>>>> prime_list = [2,3,5,7,11]
>>>>>>
>>>>>> list_plot(prime_list)
>>>>>>         
>>>>>>
>>>>>> /usr/local/sage-6.10/local/lib/python2.7/site-packages/sage/repl/rich_ou\
>>>>>> tput/display_manager.py:570: RichReprWarning: Exception in _rich_repr_
>>>>>> while displaying object: /home/mjs/src/sage-6.10/local/lib/libtatlas.so:
>>>>>> cannot open shared object file: Permission denied
>>>>>>   RichReprWarning,
>>>>>> Graphics object consisting of 1 graphics primitive
>>>>>>
>>>>>>
>>>>>> Is there a way to force the path rewrite or are there some paths that 
>>>>>> are just missed incorrectly?
>>>>>>
>>>>>> TIA.
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to