I notice the CRAN pdf didn't justify correctly long texts inside \code{}
even having "," or spaces irrespective of the status of the argument
(oneliner or multiliner)
in source (.R / .Rd)
https://imgur.com/RvjzMDh
I noticed also that it is not a problem in a pkgdown doc:
https://imgur.com/LsmuPE1
Hi Dirk,
ok, I think I got what you meant. The error for insight-checks came from
panelr, which is a suggested package. I contacted the maintainer, who said
that he won't be able to fix panelr in time, so I removed the test for the
panelr-package from insight. So, for this submission, no matter wh
Dear all,
I have submitted a patch release (1.6.0) of my package metan
(https://cran.r-project.org/web/packages/metan/) to fix an additional issue
and implement some improvements. All local checks had no errors or warnings,
but after the submission process, I received the following message.
<<
Hi Dirk,
I'm not sure I got what you mean? Locally, I used RStudio with R4.0 to check
the package. The checks I mentioned below were the official CRAN check
pages. I have now tried to run the checks on rhub, however, I'm not sure how
to access the logs:
https://builder.r-hub.io/status/insight_0.8
Hi Daniel,
On 4 June 2020 at 08:19, Daniel Lüdecke wrote:
| the package in question is "insight"
| (https://cran.r-project.org/package=insight). Since a few days, the test for
| the panelr-package fails, because panelr itself fails on many systems
| (https://cran.r-project.org/web/checks/check_r
