ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: developer not verified error
Date: Sat, 16 Nov 2019 17:09:55 +0100	[thread overview]
Message-ID: <CALBOmsYNSCjf=Ai-C6Bmv2Qe3mAxi_-XeirRejSsrwwZoHX02w@mail.gmail.com> (raw)
In-Reply-To: <CAFMOkGUg9fVa00Oegw6r1rpyfFMaqRqkp09JykfVdVQLv5OtGA@mail.gmail.com>

Dear Alan,

On Fri, 15 Nov 2019 at 22:37, Alan Bowen <bowenalan03@gmail.com> wrote:
>
> Though I was able to download the latest ConTeXt beta without any problems, my attempt to update my ConText-LMTX installation was blocked. The error message was
>
> “mtxrun” cannot be opened because the developer cannot be verified
>
> macOS cannot verify that this app is free from malware.
>
> Safari downloaded this file on April 29, 2019.

Thanks a lot for the report, but I'm tripple-confused now.

First I thought that we would have troubles with the binaries as soon
as GateKeeper was introduced (not sure which macOS version started
causing troubles), but somehow there were none, which at least came as
a pleasant surprise to me. Maybe this has to do with the fact that
anything running inside Terminal has somewhat higher permissions than
regular app bundles. (I know that Audacity doesn't allow recording
unless you run it from the Terminal, for example.)

What confuses me most though is how the beta can work, while lmtx
doesn't. I have an impression that when you download something with
Safari as opposed to downloading with rsync, Safari simply "attaches"
something to the files automatically, marking them as "unsafe", and
unzipping doesn't really help either.

The difference between the usual context distribution and lmtx is that
lmtx usually starts by downloading it from the web (and also
transferring everything in a different way).

>  I am not sure why this is happening and wonder if it would OK to copy mxtrun from my ConTeXt installation and replace the version in my ConTeXt-LMTX installation with it.

I didn't look closely, but if mtxrun is just a symlink to luametatex,
can you maybe try to run

rsync -av \
    rsync://contextgarden.net/builds/luametatex/x86_64-darwinlegacy/luametatex \
    some/local/path/luametatex

to fetch luametatex and try to use that one? (You may try to make
mtxrun a symlink to it, or its copy.)

I'm curious if that will work. I don't yet dare to upgrade to Catalina
(in some ways the OS is worse with each new version).

If it doesn't work, we'll need to figure out how exactly to do the
notarisation (including paying 100 USD per year, which sounds stupid
enough from principle alone), and in any case we need to find a way to
make lmtx work for everyone.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2019-11-16 16:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 21:36 Alan Bowen
2019-11-16  9:02 ` Hans Hagen
2019-11-16 10:32 ` Otared Kavian
2019-11-16 16:09 ` Mojca Miklavec [this message]
2019-11-18 21:32   ` Henri Menke
2019-11-19  8:57     ` Hans Hagen
2019-11-16 22:27 ` Glen Helman
2019-11-17 16:30   ` Keith McKay
2019-11-18 21:25     ` Alan Bowen
2019-11-19  9:06       ` Taco Hoekwater
2019-11-19  9:41         ` Hans Hagen

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='CALBOmsYNSCjf=Ai-C6Bmv2Qe3mAxi_-XeirRejSsrwwZoHX02w@mail.gmail.com' \
    --to=mojca.miklavec.lists@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).