Thanks both for your quick answers,
I've implemented a solution to avoid the keyring issue by handling
properly the error, and catch it properly in test-all.R (as a better
control to deactivate CI integration tests if Zenodo token is invalid -
which is the case on CRAN).
https://github.com/e
On Wed, Sep 2, 2020 at 11:11 PM Dirk Eddelbuettel wrote:
>
>
> On 2 September 2020 at 23:59, Emmanuel Blondel (GMAIL) wrote:
[...]
> | Your advice in order to solve that would be much appreciated,
>
> Life, as they say, "is too short" so you could just comment-out the test.
Indeed, it is probably
On 2 September 2020 at 23:59, Emmanuel Blondel (GMAIL) wrote:
| Dear all,
|
| I've received a notification of errors from CRAN on some package (zen4R)
| recently updated, being asked to fix within the 2 weeks before archiving.
|
| The error deals with 'keyring' package import at test time, on
Dear all,
I've received a notification of errors from CRAN on some package (zen4R)
recently updated, being asked to fix within the 2 weeks before archiving.
The error deals with 'keyring' package import at test time, on _Fedora_
flavors only.
See https://cran.r-project.org/web/checks/check_res
