ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Glen Helman <helmang@wabash.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: developer not verified error
Date: Sat, 16 Nov 2019 22:27:56 +0000	[thread overview]
Message-ID: <6E8513B7-93A0-4340-9941-3645562891F1@wabash.edu> (raw)
In-Reply-To: <CAFMOkGUg9fVa00Oegw6r1rpyfFMaqRqkp09JykfVdVQLv5OtGA@mail.gmail.com>


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

There seems to be a way around this built into Catalina, however awkward it may be.

I tried to install lmtx on a computer running Catalina that didn’t have an installation and received a similar error. (There seems to be a quarantine applying to the text of the script and not merely the file because I tried creating a new document with the same text and received the same response, and that response referred to the download of the original file.)

I did find that the “general” tab under “security & privacy” in the system preferences had, in addition to the usual two choices, a reference to the downloaded script with a button reading “allow anyway” (or something to that effect). When I tried to run the script again after clicking that button, the “developer cannot  be verified” dialogue included “open” as a choice; and, when I clicked that, the script ran successfully and the installation was usable.

I then tried the install script on another computer running Cataline where I had installed lmtx last spring. I ran into the “developer cannot be verified” response again, but the same workaround allowed the script to run, and the installation was updated.

Glen Helman

On Nov 15, 2019, at 4:36 PM, Alan Bowen <bowenalan03@gmail.com<mailto: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.

 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
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl<mailto: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
___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 5404 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
___________________________________________________________________________________

  parent reply	other threads:[~2019-11-16 22:27 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
2019-11-18 21:32   ` Henri Menke
2019-11-19  8:57     ` Hans Hagen
2019-11-16 22:27 ` Glen Helman [this message]
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=6E8513B7-93A0-4340-9941-3645562891F1@wabash.edu \
    --to=helmang@wabash.edu \
    --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).