it probably makes sense to more directly indicate what package is causing
problems (e.g., sharing the location of a public repository of the source) and
the nature of the error (cut-and-paste the check output here?). Likely this
will lead both to insight into 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"
<r-package-devel-boun...@r-project.org on behalf of e...@debian.org> wrote:
On 31 January 2020 at 09:11, Borini, Stefano wrote:
| Thanks. What is the recommended strategy in this case? Keep submitting
and patching until it passes?
Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
for others, and asking here, ... Imperfect, but doable.
It would be so nice to have actual Docker containers to reproduce issues.
Maybe one day.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
