Thank you for the advice. I think that (a) is a problem to implement since the new roxygen2 is on the CRAN systems and I can not control which version they are using to build the package in the checks.
I have gone with option (c), which is unfortunate since I will need to change my examples twice to accommodate a problem that another package, that has such a high degree of reverse dependency, has created. On Sat, Nov 30, 2019 at 9:42 AM Hugh Parsonage <hugh.parson...@gmail.com> wrote: > You could (a) install the updated roxygen from github and rebuild the man/ > files ; (b) manually edit the Rd files without using roxygen ; or (c) > remove the examples until you can apply the fix. > > On Sun, 1 Dec 2019 at 1:26 am, Yoni <yon...@gmail.com> wrote: > >> I received a message from CRAN yesterday stating my package is erroring on >> all the systems all of a sudden. >> >> https://cran.r-project.org/web/checks/check_results_texPreview.html >> >> After some investigation the root of the errors looks like it came from >> the >> new release of roxygen2 (7.0.1). >> >> https://github.com/r-lib/roxygen2/issues/990 >> >> Is there anything I can do in the interim to fix this problem since I do >> not know when this apparent bug fix will be pushed to CRAN, relieving my >> errors in the documentation builds, which could be beyond the warning >> period (2019-12-13), which the package will be removed from CRAN. >> >> Thank you >> >> [[alternative HTML version deleted]] >> >> ______________________________________________ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel >> > -- Yoni You do not learn to swim from books and lectures on the theory of buoyancy (Box 1990) [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
