CRAN rebuilds binary packages because of (potential) changes in
build-time dependencies. ABI changes, in the loose sense of the term.
E.g. package A can call the shared library of another package B. If
the ABI of B changes, then you need to rebuild A.
AFAICT packages are rebuilt frequently and oft
something and you
want to retest the whole lot against it.
--
Stefano Borini
Principal Analytical Tools Developer
AstraZeneca R&D BioPharmaceuticals | Data Science & AI | Early Biometrics &
Statistical Innovation
From: Iñaki Ucar
Date: Thursday, 17 March 2022 at 10:16
To: "Bor
Hello,
Validated software needs to ensure consistency and reproducibility of its
environment, potentially in years' time, when the audit comes. For this reason,
we identify all SHA of the packages we download from CRAN to ensure that the
package has not changed after the fact, something that ma
nto the problem being flagged by the builder, and
the reason why you are not able to reproduce it.
Martin Morgan
On 1/31/20, 9:04 AM, "R-package-devel on behalf of Dirk Eddelbuettel"
wrote:
On 31 January 2020 at 09:11, Borini, Stefano wrote:
| Thanks. What is th
Thanks. What is the recommended strategy in this case? Keep submitting and
patching until it passes?
On 30/01/2020, 22:48, "Dirk Eddelbuettel" wrote:
On 30 January 2020 at 21:40, Borini, Stefano wrote:
| I am currently trying to submit a package to CRAN, and I see no pr
I am currently trying to submit a package to CRAN, and I see no problems in
running the test on my package on Linux ubuntu 18.04 and the latest compiled R.
Is there a docker image of the CRAN automatic build system so that one can try
to reproduce the problem in house?
Thanks
_
