ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: Updating ConTeXt standalone problem on Mac OS X
Date: Tue, 26 Apr 2016 09:47:12 +0000	[thread overview]
Message-ID: <D5886B89-2ECD-49F2-A0B6-F5300AC2B929@uva.nl> (raw)
In-Reply-To: <CALBOmsbfbiYdeFk5NDLnWk3XEjSpLb7Q0uKXv=ScohNw-vVuNw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1749 bytes --]

I am running the same OSX El Capitan (from a non-administrator account) and I have no problems installing the ConTeXt-beta with the following script executed inside a fresk and empty directory:

#!/bin/bash
rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .
chmod a+x first-setup.sh
mkdir tex
cd tex
ln -s ~/Documents/TeX/texmf texmf-local
cd ..
sh ./first-setup.sh --context=beta >first-setup.log
#sh ./first-setup.sh --context=current >first-setup.log
#sh ./first-setup.sh --context=date >first-setup.log
exit


On 26 Apr 2016, at 11:34, Mojca Miklavec <mojca.miklavec.lists@gmail.com<mailto:mojca.miklavec.lists@gmail.com>> wrote:

On 26 April 2016 at 11:21, Jaroslav Hajtmar wrote:
Hello ConTeXist
I have a problem with updating ConTeXt on my Mac OS X (El Captain). When you
run the update script to me an error message appears, which surprises me,
since I logged on as the system administrator. Can anyone advise me on what
could be the problem.

Running rsync as an administrator has an ugly consequence that you end
up copying the UID and GUID as-is, so you might end up with files
owned by very strange or perhaps even non-existing users.

Maybe you could play with
   --chown=USER:GROUP
when calling rsync from first-setup.sh to start with.

Who currently owns bin and bin/luatex?

It is not impossible that something changed yesterday though (I was
messing with the server), but the installation works for me. What
happens if you run the installation as a regular user (to a fresh
directory)?

We should look into it, but I need some proper diagnosis first.

Mojca
___________________________________________________________________________________

Hans van der Meer





[-- Attachment #1.2: Type: text/html, Size: 3525 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2016-04-26  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  9:21 Jaroslav Hajtmar
2016-04-26  9:34 ` Mojca Miklavec
2016-04-26  9:47   ` Meer, Hans van der [this message]
2016-04-26 13:30   ` Jaroslav Hajtmar

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=D5886B89-2ECD-49F2-A0B6-F5300AC2B929@uva.nl \
    --to=h.vandermeer@uva.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).