Re: [R-pkg-devel] R package test breakage catch 22

2017-05-02 Thread William Revelle
Uwe, As the author of “B” (the psych package) I will submit it once Jonathon confirms he is ready to submit “A” (the jmv package). Thanks for the help. Bill > On May 2, 2017, at 10:27 AM, Uwe Ligges > wrote: > > Submit B first and write in the submission comments that A will fail but a

Re: [R-pkg-devel] R package test breakage catch 22

2017-05-02 Thread Uwe Ligges
Submit B first and write in the submission comments that A will fail but a version of A is ready to be submitted once B is accepted. Best, Uwe Ligges On 02.05.2017 06:13, Johannes Ranke wrote: how does one solve this catch-22? I see these possibilities a) reduce the precision of the tes

Re: [R-pkg-devel] R package test breakage catch 22

2017-05-01 Thread Johannes Ranke
> how does one solve this catch-22? I see these possibilities a) reduce the precision of the tests in A, so the test passes with both versions of B b) a submission of both packages at the same time, with a message in the comments, explaining to CRAN why it is necessary that both are published

[R-pkg-devel] R package test breakage catch 22

2017-05-01 Thread Jonathon Love
hi, i currently face the following situation: my package, package A, depends on package B. i have unit tests in package A which expect results, which are in part as a result of calculations from package B. package B has made some changes, which leads to slightly different results being calc