ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Brian Wedde <wbrian@onlineed.com>
To: ntg-context@ntg.nl
Subject: Re: Broken Index Behavior?
Date: Mon, 5 Mar 2018 13:30:50 -0800	[thread overview]
Message-ID: <ce92f2ac-5296-d522-a722-877301c5808e@onlineed.com> (raw)
In-Reply-To: <CAG5iGsD8YWv-VVN8Xr2XhqcmxLbY=-inGuD6w-B_+W5e3R=o4w@mail.gmail.com>

Thanks Luigi. I am getting the "correct" results on my local workstation 
as well. However, when working on an installation on a Amazon Linux EC2 
instance, the index refuses to aggregate the results. This even happens 
if i copy my entire ConTeXt directory to the Amazon Linux machine 
verbatim. I have also tried the latest ConText version and get the same 
weird results. I am convinced that this has something to with the 
environment and not the installation itself, but I don't know where to 
look anymore. I am out of ideas. I have:

- Disabled SELinux
- Copied files from known working installation
- Installed latest versions
- chmod everything 777

Any ideas on where to look would still be appreciated.

Thanks

- brian
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-03-05 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  1:28 Brian Wedde
2018-03-02  9:50 ` luigi scarso
2018-03-05 21:30   ` Brian Wedde [this message]
2018-03-05 23:37     ` luigi scarso

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=ce92f2ac-5296-d522-a722-877301c5808e@onlineed.com \
    --to=wbrian@onlineed.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).