ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <gnwiii@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ubuntu and Context MKIV
Date: Sun, 22 Aug 2010 18:43:46 -0300	[thread overview]
Message-ID: <AANLkTi=mDkF_7jb7bStkskywfnF7ersnTeJOfCU60dqb@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1008221320530.2793@ybpnyubfg.ybpnyqbznva>

On Sun, Aug 22, 2010 at 2:23 PM, Aditya Mahajan <adityam@umich.edu> wrote:

> On Sun, 22 Aug 2010, Xan wrote:
>
>> I file a bug:
>>
>> https://bugs.launchpad.net/ubuntu/+source/context/+bug/622253
>>
>> Please, provide any comments you want.
>
> What you have reported there is not a bug. After installing ConTeXt, you
> need to run (luatools --generate) as a normal user; only then mtx-contex.lua
> will be found.

The need to run "luatools --generate" is not sufficiently
visible (it is in README.MarkIV).   Any package that requires
user configuration steps should have a mechanism to inform
the user that such steps are required.  I suspect the damage
was already done by the time the OP tried "luatools --generate" ,
and was perhaps made worse by running the command from
a root prompt.

> In your case, running luatools --generate does not help, and that is the
> bug.

You are right, but with a system like context it is sometimes better to
avoid stressing the tools by following standard procedures.

The OP ended up with /etc/texmf/web2c/pdftex, which suggests that
MkII and/or fmtutil tried to install formats under /etc/texmf/web2c.   It may
be too much to expect luatools to recover when things are not where they
belong and files under $HOME are not owned by the user.

-- 
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-08-22 21:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 10:15 Xan
2010-08-19 10:52 ` George N. White III
2010-08-19 11:51   ` Xan
2010-08-19 13:48     ` George N. White III
2010-08-19 17:07       ` Xan
2010-08-20  0:07         ` George N. White III
2010-08-20  0:11     ` Aditya Mahajan
2010-08-20  0:13     ` Aditya Mahajan
2010-08-20 12:33       ` George N. White III
2010-08-20 21:41       ` Xan
2010-08-20 22:30         ` George N. White III
2010-08-21 14:58           ` Xan
2010-08-21 19:06             ` George N. White III
2010-08-22 14:35               ` Xan
2010-08-22 17:23                 ` Aditya Mahajan
2010-08-22 21:43                   ` George N. White III [this message]
2010-08-23  7:53                     ` Xan
2010-08-23 11:11                       ` George N. White III
2010-08-23  7:50                   ` Xan
2010-08-20  9:41   ` Peter Schorsch
2010-08-22 21:43     ` George N. White III

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='AANLkTi=mDkF_7jb7bStkskywfnF7ersnTeJOfCU60dqb@mail.gmail.com' \
    --to=gnwiii@gmail.com \
    --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).