From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: developer not verified error
Date: Fri, 15 Nov 2019 16:36:49 -0500 [thread overview]
Message-ID: <CAFMOkGUg9fVa00Oegw6r1rpyfFMaqRqkp09JykfVdVQLv5OtGA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 538 bytes --]
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.
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.
Alan
[-- Attachment #1.2: Type: text/html, Size: 1771 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-11-15 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 21:36 Alan Bowen [this message]
2019-11-16 9:02 ` Hans Hagen
2019-11-16 10:32 ` Otared Kavian
2019-11-16 16:09 ` Mojca Miklavec
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=CAFMOkGUg9fVa00Oegw6r1rpyfFMaqRqkp09JykfVdVQLv5OtGA@mail.gmail.com \
--to=bowenalan03@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).