Simon,
Thanks for the clarification.
Regards,
Marc
> On Oct 11, 2019, at 4:55 PM, Simon Urbanek
> wrote:
>
> The issue is not the process, the issue is that Apple requires particular way
> to build the binaries with particular tools in order to even be able to pass
> the notarization
The issue is not the process, the issue is that Apple requires particular way
to build the binaries with particular tools in order to even be able to pass
the notarization process and our current build does not use those. We can't
change the tools in the middle of the release so for R 3.6.x
Hi,
I am going to presume that Simon is already aware of this, but there is a page
on the Apple Dev site that describes the workflow that can be
implemented/customized to automate the notarization process via scripting:
Kevin,
thanks for the report. We are aware of the notarization and there are plans,
but at this point it's unclear if it's even possible, given the various
constraints and the way R works (it's unlikely that R as it is will pass the
test). We definitely hope to have a solution for R 4.0.0, but
You could always issue
sudo spctl --master-disable
:-)-O
el
On 2019-10-11 19:59 , Kevin Ushey wrote:
> Hi,
>
> I'm seeing the following when I attempt to install R-patched, as from
> http://mac.r-project.org/:
>
> ---
>
> “R-3.6-branch-el-capitan-signed.pkg” can’t be opened because
Hi,
I'm seeing the following when I attempt to install R-patched, as from
http://mac.r-project.org/:
---
“R-3.6-branch-el-capitan-signed.pkg” can’t be opened because Apple
cannot check it for malicious software.
This software needs to be updated. Contact the developer for more information.
