[R-pkg-devel] bayespca package - CRAN test

Facundo Muñoz |@muv|e @end|ng |rom gm@||@com
Wed Jun 5 14:27:09 CEST 2019

If you have access to a linux box (or cygwin), there is this tool [1]
that lets you do something like

find . -name inst/include/*.h | xargs dos2unix

to fix all the line breaks in one shot.

There are also binaries for Windows so you should be able to do this
from your computer.



[1] https://waterlan.home.xs4all.nl/dos2unix.html

On 6/5/19 1:13 PM, D. Vidotto wrote:
> Dear members,
>                 Yesterday I submitted a package called 'bayespca' (version 0.0.2) to CRAN. Today, I received an e-mail saying that the package did not pass some test.
> Thus, today I have been working on fixing these problems (original three notes). While I could fix almost all of them, there is still one problem left which I cannot fix. It is the following one:
> * checking line endings in C/C++/Fortran sources/headers ... NOTE
> Found the following sources/headers with CR or CRLF line endings:
>   inst/include/aux_functions.h
>   inst/include/elbo_functions.h
>   inst/include/expectedvalues.h
>   inst/include/updateElbo.h
>   inst/include/updateExpected.h
>   inst/include/vbalgorithm.h
> Some Unix compilers require LF line endings.
> How can I fix these? Why are my cpp files in the source folder correct, while these headers are not? Furthermore, when I run the R CMD check -as-cran on my machine (Windows), the test about line endings pass with no problems. May you help me telling me how I can modify the line endings of the above files?
> Thank you in advance for your help.
> With kind regards,
> Davide Vidotto
> Tilburg University
> 	[[alternative HTML version deleted]]
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

More information about the R-package-devel mailing list