From: Jean-Pierre Delange <adeimantos@free.fr>
To: ntg-context@ntg.nl
Subject: Re: update/install error
Date: Sat, 24 Sep 2016 12:51:13 +0200 [thread overview]
Message-ID: <2573ffc6-fe9c-d440-4662-5099670622b9@free.fr> (raw)
In-Reply-To: <3c7fef9f-997b-51fa-4ed8-6eaf5a4f4422@gmx.es>
Hello list !
There is no problem updating CTX under Linux Ubuntu
5.4.0-6ubuntu1~16.04.2, kernel 4.4.0-38-generic;
I've updated yesterday evening, without error :
mtx-context | ConTeXt Process Management 0.63
mtx-context |
mtx-context | main context file:
/home/adeimantos/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2016.09.12 18:27
Le 24/09/2016 à 12:28, Pablo Rodriguez a écrit :
> Hi Mikael,
>
> I can confirm the same error when updating standalone.
>
> Just in case it helps,
>
>
> Pablo
>
>
> On 09/23/2016 10:12 PM, Mikael P. Sundqvist wrote:
>> Hi, trying to update (running standalone, updating with
>>
>> sh ./first-setup.sh --update
>>
>> it runs for a while, and then halts on:
>>
>> lua error > lua error on line 74 in file
>> /home/mickep/ConTeXt/tex/texmf-context/tex/context/base/mkiv/node-rul.mkiv:
>>
>> ...eXt/tex/texmf-context/tex/context/base/mkiv/node-rul.lua:369: table
>> index is nil
>> stack traceback:
>> ...eXt/tex/texmf-context/tex/context/base/mkiv/node-rul.lua:369: in
>> function 'code'
>> ...eXt/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:84: in
>> function 'loadedluacode'
>> ...eXt/tex/texmf-context/tex/context/base/mkiv/luat-env.lua:104: in
>> function 'luafilechunk'
>> ...eXt/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:45: in
>> function 'registercode'
>> [ctxlua]:1: in main chunk
>>
>> 64 %D to deal with local settings at the \TEX\ end and remembering
>> parameters
>> 65 %D at the \LUA\ end. We might do things differently now, but as
>> settings normally
>> 66 %D don't change that often, we're not in a hurry to do that
>> now. The problem at
>> 67 %D the \LUA\ end is that we don't know when to clean up.
>> 68
>> 69 \unprotect
>> 70
>> 71 %definesystemattribute[ruled]
>> 72 %definesystemattribute[shifted]
>> 73
>> 74 >> \registerctxluafile{node-rul}{1.001}
>> 75
>> 76 \installcorenamespace{bar}
>> 77 \installcorenamespace{barindex}
>> 78 \installcorenamespace{barattribute}
>> 79 \installcorenamespace{barstack}
>> 80
>> 81 \installcommandhandler \??bar {bar} \??bar
>> 82
>> 83 \newtoks\t_node_rules_checklist
>> 84
>>
>> The same happens when I try to install in a fresh directory.
>>
>> This happens on a ubuntu machine where the standalone usually works very well.
>>
>> Best regards, Mikael
>
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-09-24 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 20:12 Mikael P. Sundqvist
2016-09-24 10:28 ` Pablo Rodriguez
2016-09-24 10:51 ` Jean-Pierre Delange [this message]
2016-09-24 10:56 ` Hans Hagen
2016-09-24 11:17 ` Csikos Bela
2016-09-24 11:22 ` Mikael P. Sundqvist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2573ffc6-fe9c-d440-4662-5099670622b9@free.fr \
--to=adeimantos@free.fr \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).