Gábor,
sorry for the late reply. The issue is that arm64 binaries get signed no matter
what (requirement by the kernel), but our post-install process changes the path
entries (moving dependent libraries to $R_HOME/lib etc.) which invalidates the
(anonymous) signatures. For released pkg that's
On Wed, Nov 17, 2021 at 8:45 PM Prof Brian Ripley wrote:
>
> On 17/11/2021 19:32, Gábor Csárdi wrote:
> > On Wed, Nov 17, 2021 at 8:14 PM Prof Brian Ripley
> > wrote:
> > [...]
> >> With the tarball I get a popup telling me
> >>
> >> “R.framework” cannot be opened because the developer cannot be
On 17/11/2021 19:32, Gábor Csárdi wrote:
On Wed, Nov 17, 2021 at 8:14 PM Prof Brian Ripley wrote:
[...]
With the tarball I get a popup telling me
“R.framework” cannot be opened because the developer cannot be verified.
Interesting. I am on 12.0.1 and there is no popup, but there is a
crash r
On Wed, Nov 17, 2021 at 8:14 PM Prof Brian Ripley wrote:
[...]
> With the tarball I get a popup telling me
>
> “R.framework” cannot be opened because the developer cannot be verified.
Interesting. I am on 12.0.1 and there is no popup, but there is a
crash report with
Exception Type:EXC_B
On 17/11/2021 07:17, Prof Brian Ripley wrote:
On 16/11/2021 22:28, Gábor Csárdi wrote:
This is Monterey:
❯ uname -a
Darwin Gabors-MacBook-Pro-3.local 21.1.0 Darwin Kernel Version 21.1.0:
Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
arm64
The R-devel build segfaults:
❯
