> Can you open a ticket?
http://trac.sagemath.org/sage_trac/ticket/4955
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://www.informatik.uni-bremen.de/~malb
_jab: martinralbre...@jabber.cc
On Thu, Jan 8, 2009 at 8:43 AM, Martin Albrecht
wrote:
>
>> The only idea I have to deal with this is to copy all of extcode/magma
>> into .sage/extcode/magma say, and then have sage only use magma code
>> that's in .sage/extcode/magma/.
>> Whenever sage is upgraded, the .sage/extcode/magma would
> The only idea I have to deal with this is to copy all of extcode/magma
> into .sage/extcode/magma say, and then have sage only use magma code
> that's in .sage/extcode/magma/.
> Whenever sage is upgraded, the .sage/extcode/magma would have to get
> deleted and re-copied, using a facility similar
On Thu, Jan 8, 2009 at 5:48 AM, Martin Albrecht
wrote:
>
>> RuntimeError: While attempting to compile /usr/local/sage-3.2.3/data/
>> extcode//magma/latex/latex.m (Data file non-existent):
>> Can't open lock file /usr/local/sage-3.2.3/data/extcode//magma/latex/
>> latex.lck for writing (Permission
> RuntimeError: While attempting to compile /usr/local/sage-3.2.3/data/
> extcode//magma/latex/latex.m (Data file non-existent):
> Can't open lock file /usr/local/sage-3.2.3/data/extcode//magma/latex/
> latex.lck for writing (Permission denied)
>
> While attempting to compile /usr/local/sage-3.2.3
