Re: [R-pkg-devel] package test returns error when R version 4.1.0

Hello, Thank you. Yes I just tried that option, but I still get the same  error: https://win-builder.r-project.org/2OF2vD11Uxe3 Gm Dr Gianmarco Alberti (PhD Udine) Lecturer in Spatial Forensics Coordinator of the BA dissertations Department of

Re: [R-pkg-devel] weird C stack traces from win-builder, due to brms/rstan load?

On 05/07/2021 2:50 p.m., Bill Dunlap wrote: I think the stack trace is omitting the initial underscore in the symbol name: > c++filt _ZN4Rcpp8CppClassC1EPNS_6ModuleEPNS_10class_BaseERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE Rcpp::CppClass::CppClass(Rcpp::Module*,

Re: [R-pkg-devel] package test returns error when R version 4.1.0

Gm: Did you try completely removing the LazyData line from the description file? David From: Gianmarco Alberti Sent: Monday, July 5, 2021 5:13 PM To: r-package-devel@r-project.org; Uwe Ligges ; dbosa...@gmail.com Subject: RE: [R-pkg-devel] package test returns error when R version

Re: [R-pkg-devel] package test returns error when R version 4.1.0

Hello, Thank you all for the suggestions. I am starting being a bit worried because I seem not being able to fix the issue. I have never experienced issues with this package (movecost); the last new version I have released to CRAN was released a couple of weeks ago with no issue whatsoever.

Re: [R-pkg-devel] weird C stack traces from win-builder, due to brms/rstan load?

I think the stack trace is omitting the initial underscore in the symbol name: > c++filt _ZN4Rcpp8CppClassC1EPNS_6ModuleEPNS_10class_BaseERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE Rcpp::CppClass::CppClass(Rcpp::Module*, Rcpp::class_Base*, std::__cxx11::basic_string, std::allocator >&)

Re: [R-pkg-devel] weird C stack traces from win-builder, due to brms/rstan load?

On 7/5/21 2:01 PM, Duncan Murdoch wrote: On 05/07/2021 10:32 a.m., Ben Bolker wrote:    I'm running into trouble checking a new release of the 'broom.mixed' package on win-builder.  I think it is some kind of rstan problem.    

Re: [R-pkg-devel] weird C stack traces from win-builder, due to brms/rstan load?

On 05/07/2021 10:32 a.m., Ben Bolker wrote: I'm running into trouble checking a new release of the 'broom.mixed' package on win-builder. I think it is some kind of rstan problem. The broom.mixed package loads the brms

[R-pkg-devel] weird C stack traces from win-builder, due to brms/rstan load?

I'm running into trouble checking a new release of the 'broom.mixed' package on win-builder. I think it is some kind of rstan problem. The broom.mixed package loads the brms package, and loads several pre-computed objects

Re: [R-pkg-devel] package test returns error when R version 4.1.0

For the lazy loading error, if you are not intentionally lazy loading data, you should remove the lazy loading entry from the description file. Previously this was not causing any problems with the CRAN checks, but now it is. -Original Message- From: R-package-devel On Behalf Of

Re: [R-pkg-devel] package test returns error when R version 4.1.0

I think the Bioconductor error on R-hub is a red herring. The error message is printed, but the actual error is ignored. So this is really only an issue if you do need a Bioconductor package for the check. I think the issue might be that for R-devel CRAN binaries are x64 only, but R CMD INSTALL

Re: [R-pkg-devel] package test returns error when R version 4.1.0

Hello, Thanks for your reply. I got mixed results using: devtools::check_win_oldrelease() - STATUS OK (R version 4.0.5) - https://win-builder.r-project.org/7qy6PL8C7ye7 devtools::check_win_release() - 1 ERROR (R version 4.1.0) - https://win-builder.r-project.org/hlA15dFq5BdR

Re: [R-pkg-devel] package test returns error when R version 4.1.0

What happens when you test it on winbuilder? It is configured like the CRAN incoming checks and there should be all relevant packages available. Best, Uwe Ligges On 05.07.2021 11:16, Gianmarco Alberti wrote: Hello, Further to my earlier email, I think I have located a likely issue, and I

Re: [R-pkg-devel] package test returns error when R version 4.1.0

Hello, Further to my earlier email, I think I have located a likely issue, and I would appreciate feedback. I ran devtools::check_rhub(), and somewhere in the flood of the output I got there is the following message: Bioconductor does not yet build and check packages for R version 4.2 The

[R-pkg-devel] package test returns error when R version 4.1.0

Good morning, I got stuck on what follows. I have tested a new version of my package locally (on a MAC), and everything is fine. I got mixed results using: devtools::check_win_oldrelease() - STATUS OK (R version 4.0.5) -  https://win-builder.r-project.org/7qy6PL8C7ye7