For the record, the problem is more general: the r-release-macos-x86_64 CRAN
checks of my package secr failed to update for 4.6.0 (2023-05-23) or 4.6.1
(2023-07-10) and remain stuck at version 4.5.10 (all MacOS binaries updated OK).
From: R-package-devel
On 16 July 2023 at 14:31, Simon Urbanek wrote:
| I looked into it and there was no issue on the build machine or staging
server, so it will require some more digging in the international waters ..
hopefully sometime next week…
Thanks for checking, sometimes one-offs happen.
Dirk
--
dirk.edd
I looked into it and there was no issue on the build machine or staging server,
so it will require some more digging in the international waters .. hopefully
sometime next week…
Cheers,
Simon
> On 16/07/2023, at 11:25, Dirk Eddelbuettel wrote:
>
>
> Simon,
>
> On 12 July 2023 at 19:02, Di
Simon,
On 12 July 2023 at 19:02, Dirk Eddelbuettel wrote:
|
| Simon,
|
| It looks like some result mirroring / pushing from your machines to CRAN fell
| over. One of my packages, digest 0.6.33, arrived on CRAN about a week ago,
| is built almost everywhere (apart from macOS_release_x86_64 stu
