ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Damage of installation of context mkiv
Date: Wed, 21 Jul 2010 13:05:21 +0200	[thread overview]
Message-ID: <4C46D471.6060806@gyza.cz> (raw)
In-Reply-To: <4C46CF84.5050300@wxs.nl>

It is interesting that even though I back up the entire WIN32 directory, 
so after I had returned to its original state, so it just does not work...

Jaroslav



Dne 21.7.2010 12:44, Hans Hagen napsal(a):
> On 21-7-2010 12:28, Jaroslav Hajtmar wrote:
>> Hallo all,
>>
>> When I tried to update the new version of ConTeXt into texlive 2009
>> (uploading new files to BIN directory and run commands ctxtools
>> --update, texexec --make --all and luatools --generate), then ConTeXt
>> MKIV stopped working and I failed to return original state. What
>> happened and how to fix??
>> I get this message, when I run context:
>>
>> MTXrun | forcing cache reload
>> MTXrun | resolvers: warning: no lua configuration files found
>> MTXrun | resolvers
>> MTXrun | resolvers
>> MTXrun | the resolver databases are not present or outdated
>> MTXrun | resolvers: using suffix based filetype 'lua'
>> MTXrun | resolvers: using suffix based filetype 'lua'
>> MTXrun | resolvers: remembering file 'mtx-context.lua'
>> MTXrun | resolvers: using suffix based filetype 'lua'
>> MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
>
> it should be enough to do
>
> mtxrun --generate
>
> did you move texmfcnf.lua to the right web2c dir?
>
> 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
___________________________________________________________________________________


  parent reply	other threads:[~2010-07-21 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 10:28 Jaroslav Hajtmar
2010-07-21 10:44 ` Hans Hagen
2010-07-21 11:03   ` Jaroslav Hajtmar
2010-07-21 11:05   ` Jaroslav Hajtmar [this message]
2010-07-21 15:59     ` Hans Hagen
2010-07-21 23:26       ` Images missing from PDF when created by Adobe Tom
2010-07-22  1:58         ` Tom
2010-07-22  3:33           ` Wolfgang Schuster
2010-07-22  4:07             ` Tom
2010-07-22 18:44               ` Wolfgang Schuster
2010-07-22 19:02                 ` Hans Hagen
2010-07-23  0:44                 ` Tom
2010-07-23  6:03                   ` luigi scarso
2010-07-22 12:23         ` William Adams
2010-07-22 13:17           ` Tom
2010-07-22 13:28             ` William Adams

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=4C46D471.6060806@gyza.cz \
    --to=hajtmar@gyza.cz \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).