From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt update issue
Date: Thu, 7 Jan 2016 18:35:11 +0100 [thread overview]
Message-ID: <568EA1CF.7000204@wxs.nl> (raw)
In-Reply-To: <d9a4d2e7c244f479a1b6e508b60625a2@www.sxmail.de>
On 1/7/2016 5:35 PM, klerer@sxmail.de wrote:
> Dear list,
>
> I have experienced a problem updating the ConTeXt version I use on a
> current Linux operating system flavour beginning ca. two months ago.
> By that time, as was successfully applied several times before within
> the past year of me using ConTeXt, I initiated the update process on the
> bash console via one command recommended on the corresponding ConTeXt
> page: "sh ./first-setup.sh --context=current".
> Then, and on two other ocassions very recently, ConTeXt got stuck (after
> data had indeed been received and some actions concerning the usual
> update had been executed, too) giving back the following lines in the
> bash console that puzzled me a lot:
> "...
> This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/dev) (INITEX)
> system commands enabled.
> (/home/ichha lt/context/tex/texmf-context/tex/context/base/cont-nl.mkiv
> (/home/ichhalt/context/tex/texmf-context/tex/context/base/context.mkiv(/home/ichhalt/context/tex/texmf-context/tex/context/base/syst-ini.mkiv
> ! Undefined control sequence.
> l.1020 pdfoutput
> zerocount"
> I admit that this code example is quite short, but it is definitely the
> last that the whole ConTeXt update process returns-otherwise it stood still.
> What-except for uninstalling and re-installing ConTeXt-could help now?
> If ever possible, a conservation of my current ConTeXt installation
> appeared preferable to me.
> Thank you in advance.
this points to a mismatch in tex files and luatex ... you need to
install the context beta as the older current doesn't work with the new
luatex binary
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-01-07 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 16:35 klerer
2016-01-07 16:48 ` Wolfgang Schuster
2016-01-07 17:35 ` Hans Hagen [this message]
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=568EA1CF.7000204@wxs.nl \
--to=pragma@wxs.nl \
--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).