[R-pkg-devel] check_win_release cannot find tidyr and other common packages?
Hi! I am preparing an R package to be uploaded to CRAN. I have already checked using rhub and every check passed. I have also checked using winbuilder for the release version of R (devtools:check_win_release) and there were no ERRORs or WARNINGs. However, for the devel version (devtools:check_win_devel) I got the following error: checking package dependencies ... ERROR Packages required but not available: 'tidyr', 'googlesheets', 'stringr', 'readtext' Package suggested but not available for checking: 'knitr' VignetteBuilder package required for checking but not installed: 'knitr' See section 'The DESCRIPTION file' in the 'Writing R Extensions' manual. I would really appreciate some help to figure out what's going on. This is the relevant part of my DESCRIPTION file: Imports: XML (>= 3.98), purrr (>= 0.2.4), dplyr (>= 0.7.8), tibble (>= 2.0.0), tidyr (>= 0.7.2), rlang (>= 0.3.0.1), googlesheets (>= 0.3.0), stringr (>= 1.4.0), readxl (>= 1.3.1), readtext (>= 0.7.1), zip (>= 2.0.4), xml2 (>= 1.2.0), rjson (>= 0.2.20), shiny (>= 1.3.2), tools (>= 3.5.3), utils (>= 3.5.3), R.utils (>= 2.9.0) Suggests: knitr (>= 1.9), rmarkdown (>= 1.12), testthat VignetteBuilder: knitr Report from win_builder: https://win-builder.r-project.org/EYkQRkLpS8oa/00check.log Thanks! Alberto [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] how to change from -fsanitize=undefined to -fsanitize=address
Good to know. I will pass it on to Dan. He said a few times that he wasn't an expert on this :). Thanks! Youyi On Sun, Dec 1, 2019 at 6:01 AM Dirk Eddelbuettel wrote: > > On 30 November 2019 at 23:24, Youyi Fong wrote: > | Here is a solution worked out by the wonderful staff from our scientific > | computing support team at the Fred Hutchinson Cancer Research Center. I > | really don't know how Dan did it, but the way he explained to me was that > | he came across this github repository by Dirk: > | https://github.com/rocker-org/r-devel-san-clang. There was the Docker > file > | which built the clang-san image, but he did not find the image itself in > | Docker Hub. So he built it himself and pushed it as > > It lives with all the other Rocker containers here: > > https://hub.docker.com/repository/docker/rocker/r-devel-ubsan-clang > > There is a minor 'san at GitHub, ubsan at Docker' labeling issue but you or > Dan could have asked, and the Docker tag clearly links back to > > https://github.com/rocker-org/r-devel-san-clang > > which is where you started from. Anyway, glad to know it helped! > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] how to change from -fsanitize=undefined to -fsanitize=address
On 30 November 2019 at 23:24, Youyi Fong wrote: | Here is a solution worked out by the wonderful staff from our scientific | computing support team at the Fred Hutchinson Cancer Research Center. I | really don't know how Dan did it, but the way he explained to me was that | he came across this github repository by Dirk: | https://github.com/rocker-org/r-devel-san-clang. There was the Docker file | which built the clang-san image, but he did not find the image itself in | Docker Hub. So he built it himself and pushed it as It lives with all the other Rocker containers here: https://hub.docker.com/repository/docker/rocker/r-devel-ubsan-clang There is a minor 'san at GitHub, ubsan at Docker' labeling issue but you or Dan could have asked, and the Docker tag clearly links back to https://github.com/rocker-org/r-devel-san-clang which is where you started from. Anyway, glad to know it helped! 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
Re: [R-pkg-devel] roxygen2 7.0.1 backslash escape error
Where can I find the current tex compiler / pandocs setup on CRAN check systems so I can adjust my CI, to replicate the failure? On Sat, Nov 30, 2019 at 11:45 AM Yoni wrote: > Thank you for the clarification regarding roxygen2, it does look like a > confounding issue. > > I will try to resolve the paths in the tex. > > Thank you for the help. > > On Sat, Nov 30, 2019 at 11:39 AM Iñaki Ucar > wrote: > >> >> >> El sáb., 30 nov. 2019 16:22, Yoni escribió: >> >>> Thank you for the clarification. >>> >>> I am then more confused. >>> >>> The CRAN version of the package (texPreview) has been unchanged since Oct >>> 23, at which point it was passing the checks with no errors. >>> >> >> If your package is sitting on CRAN since then, and in fact I see in your >> DESCRIPTION that you generated the docs with roxygen2 6.1.1, then the >> roxygen2 update has nothing to do with your check error. You run roxygen2; >> CRAN doesn't. >> >> Iñaki >> > > > -- > Yoni > > You do not learn to swim from books and lectures on the theory of buoyancy > (Box 1990) > -- 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
