Leaving data in the wrong encoding is leaving a bug around waiting to
surface. Is the data correctly encoded as Latin1 (codepage 8859-1),
Windows 8 bit (codepage 1252, also sometimes referred to as Latin1) or some
Unicode encoding (likely UTF-8)?
Character mapping is not such an issue for
Hi Ivan, thanks for these helpful inputs! I have tested my package on an ubuntu
box, it seemed work well. I am currently working on setting up a debian
instance on aws, and hopefully I can catch the bug from there. Will keep you
posted if the bug is something we need be aware of. Thanks,
In my experience this NOTE does not interfere with CRAN submission and you
can ignore it.
Hadley
On Monday, September 19, 2022, Igor L wrote:
> Hello everybody,
>
> I'm testing my package with the devtools::check() function and I got a
> warning about found non-ASCII strings.
>
> These
If the Bioconductor packages are unconditional requirements, maybe you
should submit your package to Bioconductor rather than CRAN. Just from
the name ("multiomicsR") it looks like it might be appropriate there.
Duncan Murdoch
On 19/09/2022 2:14 a.m., Das, Sarmistha wrote:
Hello,
I ran
Hello,
I ran (1) R CMD check --as-cran mypackage.tar.gz without any error. But it
gives an error while running the package on (2) current version-of-R-devel as
my package uses Bioconductor package (that does not run on R version 4.3).
Please help me with any idea how to fix this error. I have
On Tue, 20 Sep 2022 03:28:09 +
"Zhang, Xueqiong" wrote:
> I don’t have a linux box, and was not able to check it via
> r-hub-linux-platforms since some of bioc dependencies are not
> installed on r-hub. What should I do for the error check, any ideas?
There are Debian builds for both x86_64
