> Will L writes:
> To R-devel,
> In `R CMD build`, the ID of the user is automatically inserted into the
> DESCRIPTION file, e.g.
> Packaged: 2018-11-06 14:01:50 UTC;
> This is problematic for those of us who work in corporate settings. We must
> not divulge our user IDs in the packages
The latest version donot use BIOCINSTALLER or bioclite, still getting a
warning.
Errors are not detected in the current version, i.e. 2.3 version of maGUI.
But errors are getting reported in the earlier version i.e., 2.2 which is
not the making the current version to pass through the CRAN. I have
On 11/11/2018 6:53 PM, Duncan Murdoch wrote:
On 11/11/2018 3:39 PM, Jared Knowles wrote:
Hi!
I have a bit of a weird issue when I'm trying to check my package merTools
(source repo available here: https://github.com/jknowles/merTools
On Windows and Linux builds for R-release and R-devel, when
On 11/11/2018 3:39 PM, Jared Knowles wrote:
Hi!
I have a bit of a weird issue when I'm trying to check my package merTools
(source repo available here: https://github.com/jknowles/merTools
On Windows and Linux builds for R-release and R-devel, when R CMD CHECK
checks examples, it returns the
Not just a capitalization issue (mertools vs. merTools)?
Barring that, maybe locale trouble? Can you also do things like
LC_ALL=C R < merTools-Ex.R
?
Also, check for lines starting with "else" (I think you shouldn't be able to
run it line-by-line if that was the issue, though).
-pd
> On 11
To R-devel,
In `R CMD build`, the ID of the user is automatically inserted into the
DESCRIPTION file, e.g.
Packaged: 2018-11-06 14:01:50 UTC;
This is problematic for those of us who work in corporate settings. We must
not divulge our user IDs in the packages we develop and release.
Jim
Hi!
I have a bit of a weird issue when I'm trying to check my package merTools
(source repo available here: https://github.com/jknowles/merTools
On Windows and Linux builds for R-release and R-devel, when R CMD CHECK
checks examples, it returns the following error below:
Warning: parse error in
The release branch should be numbered 1.0.1, 1.0.2, 1.0.3, ...
The devel branch should be numbered 1.1.1, 1.1.2, 1.1.3, ...
It does not matter, from the build and distribution perspective, what your
github repository contains. What matters is the content of git.bioconductor.org
repository, the
Dear Wenhao,
regarding your two points:
1. If you have incremented your version number and pushed to one of the
Bioconductor servers (either upstream master or release), a build is
automatically triggered. The build cycle is 24 hours if I remember
correctly.
2.You don't need to have a
Dear all,
Currently, for both branches: master and RELEASE_3_8 in my github repository:
https://github.com/WT215/bayNorm/tree/master
have been updated with version number 1.0.2.
However, in the latest build report:
http://bioconductor.org/checkResults/3.8/bioc-LATEST/bayNorm/
the version
10 matches
Mail list logo
