On Sun, Nov 2, 2008 at 11:39 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Nov 2, 11:35 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Sun, Nov 2, 2008 at 10:02 AM, mabshoff
>>
>>
>>
>> <[EMAIL PROTECTED]> wrote:
>>
>> > On Nov 2, 9:45 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> >> On Sun, Nov 2, 2008 at 9:32 AM, mabshoff
>>
>> > <SNIP>
>>
>> >> > Are you talking about the "sig" files? They seem to be ASCII, so the
>> >> > issue is easy enough to fix,
>>
>> >> Yes, and that's the fix.
>>
>> > Ok, I attached each .m file into Magma and then checked all .sig files
>> > into the extcode repo. Patch is up at #4424 for someone's reviewing
>> > pleasure :)
>>
>> Unfortunately, this doesn't work. I have changed it to wontfix, and
>> posted the following message on the ticket:
>>
>> Unfortunately, this doesn't work. Probably the .sig files depend on
>> the version of Magma.
>
> Sigh, I was afraid that that might happen.
>
>> I tried applying your patch and got then using
>> it as a different user and got:
>>
>> {{{
>> Runtime error in 'AttachSpec': Could not remove the invalid signature
>> file /Users/wstein/sage/data/extcode//magma/latex/latex.sig
>>
>> }}}
>>
>> Since there are dozens of Magma versions out there, and we can't know
>> which one people are using, there is literally *no possible way* to
>> solve this problem without the user running a command such as
>> {{{
>> sage: magma('2')}}}
>>
>> as a user with write permissions to the extcode/magma directory.
>>
>> Since the error message clearly states that this is a permissions
>> problem, there is nothing further to do really (i.e., nothing on the
>> sage side). This is just the way Magma works.
>>
>
> Ok, how about a script for the extcode.spkg that attaches each file to
> a Magma session in case Magma is installed on the system?
If we do that, somebody else will complain just as much or more
about Sage starting up and running Magma as root, or something.
It could be done though. And it wouldn't require attaching each file -- all
you have to do is put this line in the spkg-install:
sage -c "magma('1')"
That will run magma, which automatically attaches *all* of the
magma code and generates the sig files, or it will go boom
and give an error if there is no magma installed.
I'm not sure if we should do this though, since I recall getting numerous
complaints over the years from people about Sage starting up and
running as root "do stuff" during the install process, but I've never
once before seen the complaint about magma and permissions that
resulted in #4424. I'm guessing that people typically know precisely
what to do in the situation of #4424 so that's what it isn't a problem
(in fact, the reporter of #4424 knew precisely what to do).
It's your call whether to add
sage -c "magma('1')"
to the spkg-install for extcode.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
