I also recommend reinstalling and making sure it works. I also
recommend making sure you actually run roxygen either via roxygenize()
or devtools::document() to make sure that your changes get written to
the NAMESPACE file. Your NAMESPACE on your github is a few months old
still.
-Dason
stamp telling you that it's producing that note 24
and 28 seconds into the check but I could be wrong. Either way the
relevant output for how long the examples take look like:
user system elapsed
cfa 8.05 0.36 10.08
That which tells you total it took 10.08 seconds to run the examples
seem like a bad person to have an association with if you ask me.
Changing the package's name seems to be much too high of a cost (if
even possible) to shake the extremely loose association one might see
the package having with Bill Cosby. It's not like you called your
package "ISIS&q
What you want is to specify the OS_type in your DESCRIPTION file. This is
documented in writing R extensions
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#The-DESCRIPTION-file
-Dason Kurkiewicz
On Jul 7, 2017 1:30 AM, "Disa Mhembere" wrote:
> Hello,
>
> I mad
You'll want to examine the note on the SystemRequirements field for the
DESCRIPTION file in the same link as before. Actually maybe you should
spend some time reading through that documentation - it's a bit dry but
will get you more familiar with what's possible.
-Dason Kurkiewicz
pecification on the minimum
version of R it would know not to run on those and you won't get the
errors.
-Dason Kurkiewicz
On Jul 20, 2017 11:43 AM, "Jernej Jevšenak"
wrote:
> Hi,
>
> recently, my first R package dendroExtra
> <https://cran.r-project.org/package=dend
It tells you what the warning is. You need to specify a license in your
DESCRIPTION file. You should really fill the entire thing out properly
anyways.
On Aug 10, 2017 12:39 PM, wrote:
> Thank you for pointing that out, this solved the ERROR in the R CMD check.
> I've updated the repo.
>
> Unfor
es that they used to
import in favor of a different package and you don't notice it then
you're going to end up installing a package on the user's system that
they don't actually need.
tldr: Just list the packages you explicitly need.
-Dason Kurkiewicz
On Tue, Aug 29, 2017 at
Did you write it from scratch or modify the function from the package
you were referencing? There may be some licensing issues you need to
consider either way.
-Dason
On Thu, Nov 9, 2017 at 3:53 AM, LUCA BELMONTE wrote:
> Dear Brian,
> Dear Uwe,
>
> Thank you for your replies.
>
> I wrote a fun
Do you get the same error if you try to build on the command line outside
of RStudio?
On Nov 28, 2017 3:51 PM, "Rampal Etienne" wrote:
> Dear all,
>
> I updated RStudio, Rtools and R-devel, and then I tried to build a package
> in RStudio that I had been able to build before without any problems
there should be any
issues.
-Dason Kurkiewicz
On Mar 1, 2018 11:36 AM, "Brian G. Peterson" wrote:
... bumping this in the hopes that someone has an answer ...
On Fri, 2018-01-26 at 10:35 -0600, Brian G. Peterson wrote:
> I'm preparing a new release of PerformanceAnalytics, and a
11 matches
Mail list logo
