[R-pkg-devel] OFFICIAL: R-devel check error: package or NAMESPACE load failed, there is no package called broom

[Aphalo, Pedro J]

It seems that 'broom' itself is failing tests on CRAN under Windows oldrel, and this may cause it to be missing from the R installation running tests on CRAN.

See:
https://cran.r-project.org/web/checks/check_results_broom.html

Pedro.

--

Pedro J. Aphalo
University Lecturer, Principal Investigator
Organismal and Evolutionary Biology (OEB) Research Programme
University of Helsinki
Finland


> -----Original Message-----
> From: R-package-devel <r-package-devel-bounces using r-project.org> On Behalf Of
> Hadley Wickham
> Sent: 10 September 2019 15:16
> To: Georgina Anderson <Georgina.Anderson using phe.gov.uk>
> Cc: r-package-devel using r-project.org
> Subject: Re: [R-pkg-devel] OFFICIAL: R-devel check error: package or
> NAMESPACE load failed, there is no package called broom
> 
> This works for me locally too, so I'd recommend trying win-devel again.
> Sometimes you catch it in an inconsistent state and your check fails for reasons
> unrelated to your package.
> 
> Hadley
> 
> On Sat, Sep 7, 2019 at 3:50 PM Georgina Anderson
> <Georgina.Anderson using phe.gov.uk> wrote:
> >
> > OFFICIAL
> >
> > Hi
> >
> > Any help with the following update to my package PHEindicatormethods
> would be appreciated.
> >
> > I have made a very minor change to the package to fix dependencies on the
> tidyr:nest() function as tidyr v 1.0.0 is due to be released with breaking changes
> on 9th September.
> > The version I am trying to upload to CRAN is 1.1.5 available here:
> > https://github.com/PublicHealthEngland/PHEindicatormethods
> >
> >
> > When I run devtools::check_win_devel locally (Windows 10 laptop, R
> > 3.6.1, rStudio 1.2.1335) it passes with no NOTES, ERRORS or WARNINGS
> > (locally it also passes devtools::check_win on release and oldrelease
> > and devtools::check_rhub)
> >
> > When I submit to CRAN I have been notified that package
> PHEindicatormethods_1.1.5.tar.gz does not pass the incoming checks
> automatically, signposting failing pre-tests on Windows:
> >
> > * using R Under development (unstable) (2019-09-02 r77130)
> >
> > * using platform: x86_64-w64-mingw32 (64-bit)
> >
> > * using session charset: ISO8859-1
> >
> >
> >
> > This is the log file available for 7 days:
> > https://win-builder.r-project.org/incoming_pretest/PHEindicatormethods
> > _1.1.5_20190905_224346/Windows/00check.log
> >
> > Below are two sections from the log that show the errors:
> >
> >
> > > library('PHEindicatormethods')
> >
> > Error: package or namespace load failed for 'PHEindicatormethods' in
> loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]):
> >
> >  there is no package called 'broom'
> >
> > Execution halted
> >
> > ** running examples for arch 'x64' ... ERROR
> >
> > Running examples in 'PHEindicatormethods-Ex.R' failed
> >
> > The error occurred in:
> >
> > R Under development (unstable) (2019-09-02 r77130) -- "Unsuffered
> Consequences"
> >
> > Copyright (C) 2019 The R Foundation for Statistical Computing
> >
> > Platform: x86_64-w64-mingw32/x64 (64-bit)
> >
> >
> > Error: processing vignette 'WorkedExamples_phe_sii.Rmd' failed with
> diagnostics:
> >
> > package or namespace load failed for 'PHEindicatormethods' in
> loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]):
> >
> >  there is no package called 'broom'
> >
> > --- failed re-building 'WorkedExamples_phe_sii.Rmd'
> >
> > SUMMARY: processing the following file failed:
> >
> >   'WorkedExamples_phe_sii.Rmd'
> >
> > Error: Vignette re-building failed.
> >
> > Execution halted
> >
> > I have checked the broom package and its upstream dependency on generics -
> I notice the tidy() function was moved from broom to generics a while back but
> this was before I submitted the current version (1.1.3) of my package to CRAN
> so not sure this can be the problem, although one of my functions does
> reference broom::tidy().  The evidence seems to point to changes in R-devel
> causing something in my package to break but without being able to reproduce
> the errors seen by CRAN I'm finding it difficult to pinpoint the problem.
> >
> > Thanks
> > Georgie
> >
> >
> >
> *****************************************************************
> *****
> > **** The information contained in the EMail and any attachments is
> > confidential and intended solely and for the attention and use of the
> > named addressee(s). It may not be disclosed to any other person
> > without the express authority of Public Health England, or the
> > intended recipient, or both. If you are not the intended recipient,
> > you must not disclose, copy, distribute or retain this message or any
> > part of it. This footnote also confirms that this EMail has been swept
> > for computer viruses by Symantec.Cloud, but please re-sweep any
> > attachments before opening or saving. http://www.gov.uk/PHE
> >
> *****************************************************************
> *********
> >         [[alternative HTML version deleted]]
> >
> > ______________________________________________
> > R-package-devel using r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
> 
> 
> 
> --
> http://hadley.nz
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel