[R-pkg-devel] Warning: replacing previous import ...
r@||@@tubner @end|ng |rom gm@||@com
Fri Jun 28 13:23:09 CEST 2019
in your NAMESPACE you import both mvtnorm and mclust completely. The
warning should go away if you change this to importFrom(...) with only
the methods you actually need, in particular dmvnorm either from
mvtnorm or from mclust. Alternatively, you could leave out the imports
and always use the fully qualified names. This makes it easy to use
both mvtnorm::dmvnorm and mclust::dmvnorm in the same package.
On Fri, Jun 28, 2019 at 1:10 PM Christian Martin Hennig
<christian.hennig using unibo.it> wrote:
> Dear list,
> I'm maintainer of the fpc package and got an email that I need to
> replace a warning that has come up. The warning is:
> "Warning: replacing previous import ‘mclust::dmvnorm’ by
> ‘mvtnorm::dmvnorm’ when loading ‘fpc’"
> Back story: A few month ago I was contacted by the maintainer of mclust
> that they now incorporate their own dmvnorm function. As dmvnorm is used
> in my package, he suggested to replace all dmvnorm by mvtnorm::dmvnorm,
> which I did. Initially this was accepted without warning by CRAN.
> I don't really understand what I should do about the warning. Isn't
> mvtnorm::dmvnorm the way to do this, if I want to go on using mvtnorm's
> dmvnorm function? All "dmvnorm" occurrences in my package are now
> mvtnorm::dmvnorm as intended and requested. Both mclust and mvtnorm are
> imported. The only (probably somewhat stupid) idea I have is to list the
> import of mvtnorm before mclust in NAMESPACE (currently mclust is
> imported forst), but this seems silly to me - what if I wanted to use
> both mvtnorm::dmvnorm and mclust::dmvnorm?
> Any hint?
> Christian Hennig
> Dipartimento di Scienze Statistiche "Paolo Fortunati",
> Universita di Bologna, phone +39 05120 98163
> christian.hennig using unibo.it
> currently on leave from UCL; UCL email still works
> R-package-devel using r-project.org mailing list
More information about the R-package-devel