Re: [R-pkg-devel] Need help testing for Apple

2020-03-11 Thread David Winsemius
> On Mar 11, 2020, at 11:39 AM, Neal Fultz wrote: > > Hello, > > I am working on a package that does terminal graphics for hterm, but iterm2 > should work too; if you have an apple computer with iterm2, could you > please help test it for me? > > Installation: > >

Re: [Rd] R CMD INSTALL cannot recognize full path on Windows

2020-03-11 Thread Wang Jiefei
Thanks for your test result Simon, I really appreciate it. I borrowed a new laptop and found the issue is only reproducible on my machine, so there is something not in R or the package that causes this problem. I will stop chattering and try to figure out where the problem is. Thanks again for

Re: [Rd] R CMD INSTALL cannot recognize full path on Windows

2020-03-11 Thread Simon Urbanek
Jiefei, you did not commit all files into the example package - your example has things like RcppExports.cpp as well as additional flags which are not in your GH project. I suspect the issue is with the extra flags you're adding - those don't come from R. Please make sure you can replicate the

Re: [Bioc-devel] commit access to the Bioconductor Git repository of multtest package

2020-03-11 Thread Yongchao Ge
Thanks Nitesh, I will git push the bug fix later tonight to fix the build error, as Katie said it was quite urgent. Yongchao On Wed, Mar 11, 2020 at 4:42 PM Turaga, Nitesh < nitesh.tur...@roswellpark.org> wrote: > I've enabled commit access. > > Yongchao should have access now. > > > On Mar

Re: [R-pkg-devel] check --as-cran error on Rd file

2020-03-11 Thread Duncan Murdoch
On 11/03/2020 11:44 a.m., Charles Geyer wrote: blurfle$ cat sped.Rcheck/00check.log * using log directory ‘/home/geyer/Software/sped/package/sped.Rcheck’ * using R Under development (unstable) (2020-03-10 r77920) * using platform: x86_64-pc-linux-gnu (64-bit) * using session charset: UTF-8 *

Re: [Bioc-devel] commit access to the Bioconductor Git repository of multtest package

2020-03-11 Thread Turaga, Nitesh
I've enabled commit access. Yongchao should have access now. > On Mar 11, 2020, at 4:40 PM, Katie Pollard > wrote: > > We will move to this solution soon. I don’t have git set up for BioC yet. The > last change I made was when we were still on svn. So, to get the fix done > quickly and to

Re: [Bioc-devel] commit access to the Bioconductor Git repository of multtest package

2020-03-11 Thread Katie Pollard
We will move to this solution soon. I don’t have git set up for BioC yet. The last change I made was when we were still on svn. So, to get the fix done quickly and to allow Yongchao to deal with fixes without an extra step through me, it would be really great if you could enable commit for him.

Re: [Bioc-devel] commit access to the Bioconductor Git repository of multtest package

2020-03-11 Thread Turaga, Nitesh
Hi I can give you commit access, but have you explored fixing the bug on the GitHub repository and then having Katie sync it with Bioconductor? If you still feel that having access to the Bioconductor git repo is the best option, I'll go ahead and give you access. Best, Nitesh > On Mar

[Bioc-devel] commit access to the Bioconductor Git repository of multtest package

2020-03-11 Thread Yongchao Ge
Hi Nitesh, By reading the email from other messages in Bioc-devel emails. There is only one maintainer that is allowed in each package. I am a maintainer of another BioC package, but not the maintainer of the multtest package. The request by Katie to add me as a co-maintainer of multtest package

Re: [Rd] rounding change

2020-03-11 Thread Hervé Pagès
Thanks for the heads up. The new result for round(51/80, digits=3) is also consistent with sprintf("%.3f", 51/80), format(51/80, digits=3), print(51/80, digits=3), and with the sprintf() function in C. Which is somehow satisfying. H. On 3/5/20 05:54, Therneau, Terry M., Ph.D. via R-devel

[R-pkg-devel] check --as-cran error on Rd file

2020-03-11 Thread Charles Geyer
blurfle$ cat sped.Rcheck/00check.log * using log directory ‘/home/geyer/Software/sped/package/sped.Rcheck’ * using R Under development (unstable) (2020-03-10 r77920) * using platform: x86_64-pc-linux-gnu (64-bit) * using session charset: UTF-8 * using option ‘--as-cran’ * checking for file

[R-pkg-devel] Need help testing for Apple

2020-03-11 Thread Neal Fultz
Hello, I am working on a package that does terminal graphics for hterm, but iterm2 should work too; if you have an apple computer with iterm2, could you please help test it for me? Installation: remotes::install_github("nfultz/osc1337") Then run this demo: demo("barplot", "osc1337")

Re: [R-pkg-devel] Fwd: Re: [CRAN-pretest-archived] CRAN submission SSLR 0.9.0

2020-03-11 Thread Martin Morgan
After running R CMD check SSLR_0.9.0.tar.gz there is a file SSLR.Rcheck/SSLR-Ex.R. Try running that R -f SSLR.Rcheck/SSLR-Ex.R my guess is that somewhere else in the examples you load a package that has a generic 'fit' that masks SSLR::fit in your package, so R is not able to find your

Re: [R-pkg-devel] Fwd: Re: [CRAN-pretest-archived] CRAN submission SSLR 0.9.0

2020-03-11 Thread Henrik Bengtsson
'fpalomares', it's not clear if you can reproduce this locally or not, but make sure you can reproduce it locally. I could using: R CMD check --as-cran SSLR_0.9.0.tar.gz with R 3.6.3 on Ubuntu 18.04. In other words, this is neither a problem with the CRAN incoming checks nor win-builder. Yes,

Re: [Bioc-devel] Bioconductor Release 3.11 Schedule

2020-03-11 Thread Turaga, Nitesh
Hello Bioconductor developers, As per the release schedule, I wanted to add that Bioconductor is now taking submission of Docker images as well. Please note that the same deadlines apply for the docker images and packages. Relevant links for Docker image submissions are: 1. General Docker

Re: [R-pkg-devel] Package windows binaries not updating?

2020-03-11 Thread Uwe Ligges
Sorry, takes longer as I we use a lot of COU cychecking ... Uwe On 11.03.2020 15:23, Joe Thorley wrote: Hi All Version 0.4.0 of the chk package was accepted by CRAN over a week ago (on March 3rd 2020). However, the windows binaries have not yet updated for r-devel and r-release.

Re: [Rd] R CMD INSTALL cannot recognize full path on Windows

2020-03-11 Thread Wang Jiefei
Thanks a lot for your suggestions. I see what you mean. I have removed all unnecessary files and dependences on https://github.com/Jiefei-Wang/example, but still no luck. I've tried to install the package as a user, not admin, but I got the same error. Also, I apologize for spamming the mail list.

Re: [R-pkg-devel] Fwd: Re: [CRAN-pretest-archived] CRAN submission SSLR 0.9.0

2020-03-11 Thread Duncan Murdoch
Uwe Ligges answered you yesterday on this question. Duncan Murdoch On 11/03/2020 7:39 a.m., fpaloma...@correo.ugr.es wrote: Hi, I dont know how to fix this problem: https://win-builder.r-project.org/VK8P07E1QHFA/ The error is: Error in UseMethod("fit") : no applicable method for 'fit'

[R-pkg-devel] Package windows binaries not updating?

2020-03-11 Thread Joe Thorley
Hi All Version 0.4.0 of the chk package was accepted by CRAN over a week ago (on March 3rd 2020). However, the windows binaries have not yet updated for r-devel and r-release. https://cran.r-project.org/web/packages/chk/index.html Is

Re: [Rd] R CMD INSTALL cannot recognize full path on Windows

2020-03-11 Thread Wang Jiefei
Thanks, Tomas. I took your suggestion and change the make file to test1:=$(shell $(R_HOME)/bin/R --slave -e 'runif(3)') all: testPackage.dll echo "test1 is $(test1)" echo "R_HOME is $(R_HOME)" However, R CMD INSTALL still gives me the same error: > R CMD INSTALL testPackage_1.0.tar.gz*

Re: [Rd] R CMD INSTALL cannot recognize full path on Windows

2020-03-11 Thread Tomas Kalibera
Thanks, Jiefei, unfortunately your example does not work on my system, and also it is far from minimal. The error message you are getting is from Windows and could be caused for example by accidental quoting of the path using single quotes. Issues with RStudio or devtools would have to be

Re: [Bioc-devel] R CMD build error for 3.10 (but not 3.11)

2020-03-11 Thread L Rutter
Dear Lori: Thank you for your helpful e-mail. This is just a note that I completed the recommended steps: 1) Checked that my DESCRIPTION file contains version 1.3.2 2) Issued the following three commands: git fetch --all git pull upstream master git push upstream master There were no error