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

[Greg Minshall]

> In short, no matter how large you try to span your test coverage and surface,
> there will always be a residual chance for something slipping through.

"the narrower the window, the more likely you are to hit it."  :)

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Dirk Eddelbuettel]

On 8 July 2021 at 10:41, Uwe Ligges wrote:
| It was likely an interim version of Rcpp (which never made it to CRAN) 
| that was causing trouble.

Yup, our bad.

While we test against 2300+ reverse depends, we only test against them _under
the most recent versions we have seen_ which affects the Rcpp under test, and
we do not have an (explicit) test vector for these 2300+ packages tested
against everything built under the _CRAN_ version of Rcpp.  So the need for
one small adjustment slipped til we made it to CRAN, which caused this issue,
and one for broom.mixed (as we communicated off-list to Ben).

In short, no matter how large you try to span your test coverage and surface,
there will always be a residual chance for something slipping through.

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Alex Chubaty]

Thanks Uwe! That fixed the issue for me too.

On Thu, Jul 8, 2021 at 2:41 AM Uwe Ligges 
wrote:

> It was likely an interim version of Rcpp (which never made it to CRAN)
> that was causing trouble.
> The winbuilder queues are set up to test against most recent CRAN
> submissions which caused the trouble in this case.
>
> Best,
> Uwe Ligges
>
> On 07.07.2021 22:42, Murray Efford wrote:
> > Likewise: secr now passes on Winbuilder for R-release.
> > Thanks
> > Murray
> >
> > 
> > From: Gianmarco Alberti 
> > Sent: 08 July 2021 08:21
> > To: r-package-devel@r-project.org
> > Cc: Murray Efford; Duncan Murdoch; Alex Chubaty; Uwe Ligges
> > Subject: Re: [R-pkg-devel] package test returns error when R version
> 4.1.0
> >
> > Dear All,
> > Thanks for the useful discussion.
> >
> > After Uwe’s prompt, I have tested the package again, and everything is
> fine now.
> > Was it a CRAN issue?
> >
> > Whatever the issue was, I am glad my new version is bound to be on CRAN
> soon (I have just submitted it).
> >
> > Best
> > Gianmarco
> >
> > 
> > Dr Gianmarco Alberti (PhD Udine)
> > Lecturer in Spatial Forensics
> > Coordinator of the BA dissertations
> > Department of Criminology
> > Faculty for Social Wellbeing
> > Room 332, Humanities B (FEMA)
> > University of Malta, Msida, Malta (Europe) - MSD 2080
> > tel +356 2340 3718
> >
> > Academic profiles
> > https://www.researchgate.net/profile/Gianmarco_Alberti4<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.researchgate.net%2Fprofile%2FGianmarco_Alberti4=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130923706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=h8Vd1hD4UYCABtO2KXooCaVJ20XkNPizQUisles3WG4%3D=0
> >
> > https://malta.academia.edu/GianmarcoAlberti<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmalta.academia.edu%2FGianmarcoAlberti=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=zts7AUM0HDuFCDEIY8bKnZ9gtW2XNlsc%2FmGyRpldKc4%3D=0
> >
> >
> > Google Scholar profile
> > https://scholar.google.com/citations?user=tFrJKQ0J=en<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fscholar.google.com%2Fcitations%3Fuser%3DtFrJKQ0J%26hl%3Den=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=1EFXaEOiQUnYxmyH3YXpeY7UnxJmJIlNs4J4kyYLkfs%3D=0
> >
> >
> > Correspondence Analysis website
> > http://cainarchaeology.weebly.com/<
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcainarchaeology.weebly.com%2F=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=CsvmSG6H6Hdo32dt95ylIXFJL80zBFKpwp8Jck5awns%3D=0
> >
> >
> > R packages on CRAN:
> > CAinterprTools
> > https://cran.r-project.org/web/packages/CAinterprTools/index.html<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2FCAinterprTools%2Findex.html=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=LAeqHw6HR8j99IxLlt142lRP9Zr0OHvQuaRSMgE6tz4%3D=0
> >
> >
> > GmAMisc
> > https://cran.r-project.org/package=GmAMisc<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3DGmAMisc=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=0g8Doj4UduPhPihoTd0M5i8UkHEAu526hW8bw%2FLqW2A%3D=0
> >
> >
> > movecost
> > https://cran.r-project.org/web/packages/movecost/index.html<
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2Fmovecost%2Findex.html=04%7C01%7Cmurray.effor

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

[Uwe Ligges]

It was likely an interim version of Rcpp (which never made it to CRAN) 
that was causing trouble.
The winbuilder queues are set up to test against most recent CRAN 
submissions which caused the trouble in this case.


Best,
Uwe Ligges

On 07.07.2021 22:42, Murray Efford wrote:

Likewise: secr now passes on Winbuilder for R-release.
Thanks
Murray


From: Gianmarco Alberti 
Sent: 08 July 2021 08:21
To: r-package-devel@r-project.org
Cc: Murray Efford; Duncan Murdoch; Alex Chubaty; Uwe Ligges
Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0

Dear All,
Thanks for the useful discussion.

After Uwe’s prompt, I have tested the package again, and everything is fine now.
Was it a CRAN issue?

Whatever the issue was, I am glad my new version is bound to be on CRAN soon (I 
have just submitted it).

Best
Gianmarco


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.researchgate.net%2Fprofile%2FGianmarco_Alberti4=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130923706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=h8Vd1hD4UYCABtO2KXooCaVJ20XkNPizQUisles3WG4%3D=0>
https://malta.academia.edu/GianmarcoAlberti<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmalta.academia.edu%2FGianmarcoAlberti=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=zts7AUM0HDuFCDEIY8bKnZ9gtW2XNlsc%2FmGyRpldKc4%3D=0>

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fscholar.google.com%2Fcitations%3Fuser%3DtFrJKQ0J%26hl%3Den=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=1EFXaEOiQUnYxmyH3YXpeY7UnxJmJIlNs4J4kyYLkfs%3D=0>

Correspondence Analysis website
http://cainarchaeology.weebly.com/<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcainarchaeology.weebly.com%2F=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=CsvmSG6H6Hdo32dt95ylIXFJL80zBFKpwp8Jck5awns%3D=0>

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2FCAinterprTools%2Findex.html=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=LAeqHw6HR8j99IxLlt142lRP9Zr0OHvQuaRSMgE6tz4%3D=0>

GmAMisc
https://cran.r-project.org/package=GmAMisc<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3DGmAMisc=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=0g8Doj4UduPhPihoTd0M5i8UkHEAu526hW8bw%2FLqW2A%3D=0>

movecost
https://cran.r-project.org/web/packages/movecost/index.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2Fmovecost%2Findex.html=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130953573%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=NTlgzW0PBh7RvbhNWb9ZCWsUG8Fh2NcVIqX%2Flta9%2FJ4%3D=0>

On 7 Jul 2021, 16:47 +0200, Uwe Ligges , wrote:
Can you pls try again now.

Best,
Uwe Ligges

On 06.07.2021 23:18, Murray Efford wrote:
I also get from Winbuilder:

** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'secr'

even for the tar.gz of the version secr 4.4.4 that currently passes all checks 
on CRAN. Perhaps it is significant that secr also imports from raster

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

[Murray Efford]

Likewise: secr now passes on Winbuilder for R-release.
Thanks
Murray


From: Gianmarco Alberti 
Sent: 08 July 2021 08:21
To: r-package-devel@r-project.org
Cc: Murray Efford; Duncan Murdoch; Alex Chubaty; Uwe Ligges
Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0

Dear All,
Thanks for the useful discussion.

After Uwe’s prompt, I have tested the package again, and everything is fine now.
Was it a CRAN issue?

Whatever the issue was, I am glad my new version is bound to be on CRAN soon (I 
have just submitted it).

Best
Gianmarco


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.researchgate.net%2Fprofile%2FGianmarco_Alberti4=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130923706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=h8Vd1hD4UYCABtO2KXooCaVJ20XkNPizQUisles3WG4%3D=0>
https://malta.academia.edu/GianmarcoAlberti<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmalta.academia.edu%2FGianmarcoAlberti=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=zts7AUM0HDuFCDEIY8bKnZ9gtW2XNlsc%2FmGyRpldKc4%3D=0>

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fscholar.google.com%2Fcitations%3Fuser%3DtFrJKQ0J%26hl%3Den=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=1EFXaEOiQUnYxmyH3YXpeY7UnxJmJIlNs4J4kyYLkfs%3D=0>

Correspondence Analysis website
http://cainarchaeology.weebly.com/<https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcainarchaeology.weebly.com%2F=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130933658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=CsvmSG6H6Hdo32dt95ylIXFJL80zBFKpwp8Jck5awns%3D=0>

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2FCAinterprTools%2Findex.html=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=LAeqHw6HR8j99IxLlt142lRP9Zr0OHvQuaRSMgE6tz4%3D=0>

GmAMisc
https://cran.r-project.org/package=GmAMisc<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3DGmAMisc=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130943618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=0g8Doj4UduPhPihoTd0M5i8UkHEAu526hW8bw%2FLqW2A%3D=0>

movecost
https://cran.r-project.org/web/packages/movecost/index.html<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2Fmovecost%2Findex.html=04%7C01%7Cmurray.efford%40otago.ac.nz%7Cc4dbf78cce0a48d0d11708d94184c644%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612862130953573%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=NTlgzW0PBh7RvbhNWb9ZCWsUG8Fh2NcVIqX%2Flta9%2FJ4%3D=0>

On 7 Jul 2021, 16:47 +0200, Uwe Ligges , wrote:
Can you pls try again now.

Best,
Uwe Ligges

On 06.07.2021 23:18, Murray Efford wrote:
I also get from Winbuilder:

** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'secr'

even for the tar.gz of the version secr 4.4.4 that currently passes all checks 
on CRAN. Perhaps it is significant that secr also imports from raster that had 
a new version on CRAN 18th June.

Murray Efford


From: R-package-devel  on behalf of 
Duncan Murdoch 
Sent: 07 July 2021 08:28
To: Alex Chubaty
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] package test returns e

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

[Gianmarco Alberti]

Dear All,
Thanks for the useful discussion.

After Uwe’s prompt, I have tested the package again, and everything is fine now.
Was it a CRAN issue?

Whatever the issue was, I am glad my new version is bound to be on CRAN soon (I 
have just submitted it).

Best
Gianmarco


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 7 Jul 2021, 16:47 +0200, Uwe Ligges , wrote:
> Can you pls try again now.
>
> Best,
> Uwe Ligges
>
> On 06.07.2021 23:18, Murray Efford wrote:
> > I also get from Winbuilder:
> >
> > ** byte-compile and prepare package for lazy loading
> > ERROR: lazy loading failed for package 'secr'
> >
> > even for the tar.gz of the version secr 4.4.4 that currently passes all 
> > checks on CRAN. Perhaps it is significant that secr also imports from 
> > raster that had a new version on CRAN 18th June.
> >
> > Murray Efford
> >
> > 
> > From: R-package-devel  on behalf of 
> > Duncan Murdoch 
> > Sent: 07 July 2021 08:28
> > To: Alex Chubaty
> > Cc: r-package-devel@r-project.org
> > Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0
> >
> > On 06/07/2021 4:15 p.m., Alex Chubaty wrote:
> > > Thanks for the suggestion Duncan.
> > >
> > > The same code version ran on winbuilder last week, but it's broken this
> > > week.
> >
> > If that happened with a released version of R, then it could be that
> > some new package version is causing the problem, or it could be a
> > transient problem on Winbuilder.
> >
> > Devel versions of R change every day, so there are more possibilities
> > for origins of the problem there.
> >
> > Duncan Murdoch
> >
> > >
> > > I'll compare the dependencies between the two packages and focus on
> > > those used by both for now, to see if it's caused by a broken dependency.
> > >
> > > Alex
> > >
> > >
> > > On Tue, Jul 6, 2021 at 2:08 PM Duncan Murdoch  > > <mailto:murdoch.dun...@gmail.com>> wrote:
> > >
> > > Both NegLogoR and movecost have a lot of hard dependencies -- so many
> > > that I'm unwilling to install them with the limited bandwidth that I
> > > have right now. I suspect that's related to the problem: some
> > > dependency install is failing, and that causes something else to fail,
> > > and that leads to the not-very-informative failure messages.
> > >
> > > This kind of problem is quite a lot of work to debug. If I were going
> > > to attempt to do it, I would go for a bisection strategy:
> > >
> > > - Do you have any old revision which succeeds? If so, use bisection
> > > on the revisions until you find the change which first triggers the
> > > error.
> > >
> > > - Perhaps no versions succeed, because something external to your
> > > package has triggered the error. In this case, bisection would work on
> > > the dependencies: cut out half of the dependencies and all the code
> > > that depends on those. Have you fixed the error? If so, add back half
> > > of the dependencies, otherwise cut out half of the remaining ones.
> > >
> > > - If you're still getting the errors after cutting out all of the
> > > dependencies, then start cutting out code and data. Etc.
> > >
> > > In any case, try to find a version of the package that doesn't trigger
> > > the error, and a minimal change to it that does. Then perhaps you'll
> > > understand the root cause of the error.
> > >
> > > Duncan Murdoch
> > >
> > > On 06/07/2021 3:11 p.m., Alex Chubaty wrote:
> > > > FWIW I'm having the same issue with package NetLogoR (
> > > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg

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

[Uwe Ligges]

Can you pls try again now.

Best,
Uwe Ligges

On 06.07.2021 23:18, Murray Efford wrote:

I also get from Winbuilder:

** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'secr'

even for the tar.gz of the version secr 4.4.4 that currently passes all checks 
on CRAN. Perhaps it is significant that secr also imports from raster that had 
a new version on CRAN 18th June.

Murray Efford


From: R-package-devel  on behalf of Duncan 
Murdoch 
Sent: 07 July 2021 08:28
To: Alex Chubaty
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0

On 06/07/2021 4:15 p.m., Alex Chubaty wrote:

Thanks for the suggestion Duncan.

The same code version ran on winbuilder last week, but it's broken this
week.


If that happened with a released version of R, then it could be that
some new package version is causing the problem, or it could be a
transient problem on Winbuilder.

Devel versions of R change every day, so there are more possibilities
for origins of the problem there.

Duncan Murdoch



I'll compare the dependencies between the two packages and focus on
those used by both for now, to see if it's caused by a broken dependency.

Alex


On Tue, Jul 6, 2021 at 2:08 PM Duncan Murdoch mailto:murdoch.dun...@gmail.com>> wrote:

 Both NegLogoR and movecost have a lot of hard dependencies -- so many
 that I'm unwilling to install them with the limited bandwidth that I
 have right now.  I suspect that's related to the problem:  some
 dependency install is failing, and that causes something else to fail,
 and that leads to the not-very-informative failure messages.

 This kind of problem is quite a lot of work to debug.  If I were going
 to attempt to do it, I would go for a bisection strategy:

- Do you have any old revision which succeeds?  If so, use bisection
 on the revisions until you find the change which first triggers the
 error.

- Perhaps no versions succeed, because something external to your
 package has triggered the error.  In this case, bisection would work on
 the dependencies:  cut out half of the dependencies and all the code
 that depends on those.  Have you fixed the error?  If so, add back half
 of the dependencies, otherwise cut out half of the remaining ones.

- If you're still getting the errors after cutting out all of the
 dependencies, then start cutting out code and data. Etc.

 In any case, try to find a version of the package that doesn't trigger
 the error, and a minimal change to it that does.  Then perhaps you'll
 understand the root cause of the error.

 Duncan Murdoch

 On 06/07/2021 3:11 p.m., Alex Chubaty wrote:
  > FWIW I'm having the same issue with package NetLogoR (
  > 
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPredictiveEcology%2FNetLogoR%2Fdata=04%7C01%7Cmurray.efford%40otago.ac.nz%7C0215a2eac18a47b8f63108d940bcd5d9%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612003078338060%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=5XPRhpw3sUyHbOiiupslC%2BZ0pCxcvNekFmWzmZkQPig%3Dreserved=0
 
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPredictiveEcology%2FNetLogoR%2Fdata=04%7C01%7Cmurray.efford%40otago.ac.nz%7C0215a2eac18a47b8f63108d940bcd5d9%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612003078348021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=faXwrXOP1RHKEsPrqjmOhg4O8MWayRou6%2B1Y%2BPIj%2FuY%3Dreserved=0>)
  >
  > Passing windows tests locally but code can't be lazy loaded on
 winbuilder,
  > except for oldrel.
  >
  > Alex
  >
  >
  >
  >
  >
  > On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
  > gianmarcoalbe...@gmail.com <mailto:gianmarcoalbe...@gmail.com>>
 wrote:
  >
  >> Thank you all. I appreciate your help and discussion so far.
  >>
  >> To complicate the matter further, I have done an experiment. I
 have tried
  >> to test a new version which is 99.9% identical to the last
 official one on
  >> CRAN because I wanted to understand if the issue was with some
 new code
  >> added to the version I have been testing in the last couple of days.
  >>
  >> The new version 1.2 (virtually identical to the 1.1 on CRAN) did
 not pass
  >> the tests as per my earlier description. Same errors. The only
 Ok is on my
  >> computer and with devtools’ winoldrealeases()
  >>
  >> I really don’t know that to do next.
  >>
  >> Best
  >> Gm
  >>

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

[Murray Efford]

I also get from Winbuilder:

** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'secr'

even for the tar.gz of the version secr 4.4.4 that currently passes all checks 
on CRAN. Perhaps it is significant that secr also imports from raster that had 
a new version on CRAN 18th June.

Murray Efford


From: R-package-devel  on behalf of 
Duncan Murdoch 
Sent: 07 July 2021 08:28
To: Alex Chubaty
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0

On 06/07/2021 4:15 p.m., Alex Chubaty wrote:
> Thanks for the suggestion Duncan.
>
> The same code version ran on winbuilder last week, but it's broken this
> week.

If that happened with a released version of R, then it could be that
some new package version is causing the problem, or it could be a
transient problem on Winbuilder.

Devel versions of R change every day, so there are more possibilities
for origins of the problem there.

Duncan Murdoch

>
> I'll compare the dependencies between the two packages and focus on
> those used by both for now, to see if it's caused by a broken dependency.
>
> Alex
>
>
> On Tue, Jul 6, 2021 at 2:08 PM Duncan Murdoch  <mailto:murdoch.dun...@gmail.com>> wrote:
>
> Both NegLogoR and movecost have a lot of hard dependencies -- so many
> that I'm unwilling to install them with the limited bandwidth that I
> have right now.  I suspect that's related to the problem:  some
> dependency install is failing, and that causes something else to fail,
> and that leads to the not-very-informative failure messages.
>
> This kind of problem is quite a lot of work to debug.  If I were going
> to attempt to do it, I would go for a bisection strategy:
>
>- Do you have any old revision which succeeds?  If so, use bisection
> on the revisions until you find the change which first triggers the
> error.
>
>- Perhaps no versions succeed, because something external to your
> package has triggered the error.  In this case, bisection would work on
> the dependencies:  cut out half of the dependencies and all the code
> that depends on those.  Have you fixed the error?  If so, add back half
> of the dependencies, otherwise cut out half of the remaining ones.
>
>- If you're still getting the errors after cutting out all of the
> dependencies, then start cutting out code and data. Etc.
>
> In any case, try to find a version of the package that doesn't trigger
> the error, and a minimal change to it that does.  Then perhaps you'll
> understand the root cause of the error.
>
> Duncan Murdoch
>
> On 06/07/2021 3:11 p.m., Alex Chubaty wrote:
>  > FWIW I'm having the same issue with package NetLogoR (
>  > 
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPredictiveEcology%2FNetLogoR%2Fdata=04%7C01%7Cmurray.efford%40otago.ac.nz%7C0215a2eac18a47b8f63108d940bcd5d9%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612003078338060%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=5XPRhpw3sUyHbOiiupslC%2BZ0pCxcvNekFmWzmZkQPig%3Dreserved=0
> 
> <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPredictiveEcology%2FNetLogoR%2Fdata=04%7C01%7Cmurray.efford%40otago.ac.nz%7C0215a2eac18a47b8f63108d940bcd5d9%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637612003078348021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=faXwrXOP1RHKEsPrqjmOhg4O8MWayRou6%2B1Y%2BPIj%2FuY%3Dreserved=0>)
>  >
>  > Passing windows tests locally but code can't be lazy loaded on
> winbuilder,
>  > except for oldrel.
>  >
>  > Alex
>  >
>  >
>  >
>  >
>  >
>  > On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
>  > gianmarcoalbe...@gmail.com <mailto:gianmarcoalbe...@gmail.com>>
> wrote:
>  >
>  >> Thank you all. I appreciate your help and discussion so far.
>  >>
>  >> To complicate the matter further, I have done an experiment. I
> have tried
>  >> to test a new version which is 99.9% identical to the last
> official one on
>  >> CRAN because I wanted to understand if the issue was with some
> new code
>  >> added to the version I have been testing in the last couple of days.
>  >>
>  >> The new version 1.2 (virtually identical to the 1.1 on CRAN) did
> not pass
>  >> the tests as per my earlier description. Same errors. The only
&

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

[Duncan Murdoch]

On 06/07/2021 4:15 p.m., Alex Chubaty wrote:

Thanks for the suggestion Duncan.

The same code version ran on winbuilder last week, but it's broken this 
week.


If that happened with a released version of R, then it could be that 
some new package version is causing the problem, or it could be a 
transient problem on Winbuilder.


Devel versions of R change every day, so there are more possibilities 
for origins of the problem there.


Duncan Murdoch



I'll compare the dependencies between the two packages and focus on 
those used by both for now, to see if it's caused by a broken dependency.


Alex


On Tue, Jul 6, 2021 at 2:08 PM Duncan Murdoch > wrote:


Both NegLogoR and movecost have a lot of hard dependencies -- so many
that I'm unwilling to install them with the limited bandwidth that I
have right now.  I suspect that's related to the problem:  some
dependency install is failing, and that causes something else to fail,
and that leads to the not-very-informative failure messages.

This kind of problem is quite a lot of work to debug.  If I were going
to attempt to do it, I would go for a bisection strategy:

   - Do you have any old revision which succeeds?  If so, use bisection
on the revisions until you find the change which first triggers the
error.

   - Perhaps no versions succeed, because something external to your
package has triggered the error.  In this case, bisection would work on
the dependencies:  cut out half of the dependencies and all the code
that depends on those.  Have you fixed the error?  If so, add back half
of the dependencies, otherwise cut out half of the remaining ones.

   - If you're still getting the errors after cutting out all of the
dependencies, then start cutting out code and data. Etc.

In any case, try to find a version of the package that doesn't trigger
the error, and a minimal change to it that does.  Then perhaps you'll
understand the root cause of the error.

Duncan Murdoch

On 06/07/2021 3:11 p.m., Alex Chubaty wrote:
 > FWIW I'm having the same issue with package NetLogoR (
 > https://github.com/PredictiveEcology/NetLogoR/
)
 >
 > Passing windows tests locally but code can't be lazy loaded on
winbuilder,
 > except for oldrel.
 >
 > Alex
 >
 >
 >
 >
 >
 > On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
 > gianmarcoalbe...@gmail.com >
wrote:
 >
 >> Thank you all. I appreciate your help and discussion so far.
 >>
 >> To complicate the matter further, I have done an experiment. I
have tried
 >> to test a new version which is 99.9% identical to the last
official one on
 >> CRAN because I wanted to understand if the issue was with some 
new code

 >> added to the version I have been testing in the last couple of days.
 >>
 >> The new version 1.2 (virtually identical to the 1.1 on CRAN) did
not pass
 >> the tests as per my earlier description. Same errors. The only
Ok is on my
 >> computer and with devtools’ winoldrealeases()
 >>
 >> I really don’t know that to do next.
 >>
 >> Best
 >> Gm
 >>
 >> 
 >> Dr Gianmarco Alberti (PhD Udine)
 >> Lecturer in Spatial Forensics
 >> Coordinator of the BA dissertations
 >> Department of Criminology
 >> Faculty for Social Wellbeing
 >> Room 332, Humanities B (FEMA)
 >> University of Malta, Msida, Malta (Europe) - MSD 2080
 >> tel +356 2340 3718
 >>
 >> Academic profiles
 >> https://www.researchgate.net/profile/Gianmarco_Alberti4

 >> https://malta.academia.edu/GianmarcoAlberti

 >>
 >> Google Scholar profile
 >> https://scholar.google.com/citations?user=tFrJKQ0J=en

 >>
 >> Correspondence Analysis website
 >> http://cainarchaeology.weebly.com/

 >>
 >> R packages on CRAN:
 >> CAinterprTools
 >>
https://cran.r-project.org/web/packages/CAinterprTools/index.html

 >>
 >> GmAMisc
 >> https://cran.r-project.org/package=GmAMisc

 >>
 >> movecost
 >> https://cran.r-project.org/web/packages/movecost/index.html

 >> 
 >> Il 6 lug 2021, 14:53 +0200, brodie gaslam via R-package-devel <
 >> r-package-devel@r-project.org

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

[Alex Chubaty]

Thanks for the suggestion Duncan.

The same code version ran on winbuilder last week, but it's broken this
week.

I'll compare the dependencies between the two packages and focus on those
used by both for now, to see if it's caused by a broken dependency.

Alex


On Tue, Jul 6, 2021 at 2:08 PM Duncan Murdoch 
wrote:

> Both NegLogoR and movecost have a lot of hard dependencies -- so many
> that I'm unwilling to install them with the limited bandwidth that I
> have right now.  I suspect that's related to the problem:  some
> dependency install is failing, and that causes something else to fail,
> and that leads to the not-very-informative failure messages.
>
> This kind of problem is quite a lot of work to debug.  If I were going
> to attempt to do it, I would go for a bisection strategy:
>
>   - Do you have any old revision which succeeds?  If so, use bisection
> on the revisions until you find the change which first triggers the error.
>
>   - Perhaps no versions succeed, because something external to your
> package has triggered the error.  In this case, bisection would work on
> the dependencies:  cut out half of the dependencies and all the code
> that depends on those.  Have you fixed the error?  If so, add back half
> of the dependencies, otherwise cut out half of the remaining ones.
>
>   - If you're still getting the errors after cutting out all of the
> dependencies, then start cutting out code and data. Etc.
>
> In any case, try to find a version of the package that doesn't trigger
> the error, and a minimal change to it that does.  Then perhaps you'll
> understand the root cause of the error.
>
> Duncan Murdoch
>
> On 06/07/2021 3:11 p.m., Alex Chubaty wrote:
> > FWIW I'm having the same issue with package NetLogoR (
> > https://github.com/PredictiveEcology/NetLogoR/)
> >
> > Passing windows tests locally but code can't be lazy loaded on
> winbuilder,
> > except for oldrel.
> >
> > Alex
> >
> >
> >
> >
> >
> > On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
> > gianmarcoalbe...@gmail.com> wrote:
> >
> >> Thank you all. I appreciate your help and discussion so far.
> >>
> >> To complicate the matter further, I have done an experiment. I have
> tried
> >> to test a new version which is 99.9% identical to the last official one
> on
> >> CRAN because I wanted to understand if the issue was with some  new code
> >> added to the version I have been testing in the last couple of days.
> >>
> >> The new version 1.2 (virtually identical to the 1.1 on CRAN) did not
> pass
> >> the tests as per my earlier description. Same errors. The only Ok is on
> my
> >> computer and with devtools’ winoldrealeases()
> >>
> >> I really don’t know that to do next.
> >>
> >> Best
> >> Gm
> >>
> >> 
> >> Dr Gianmarco Alberti (PhD Udine)
> >> Lecturer in Spatial Forensics
> >> Coordinator of the BA dissertations
> >> Department of Criminology
> >> Faculty for Social Wellbeing
> >> Room 332, Humanities B (FEMA)
> >> University of Malta, Msida, Malta (Europe) - MSD 2080
> >> tel +356 2340 3718
> >>
> >> Academic profiles
> >> https://www.researchgate.net/profile/Gianmarco_Alberti4
> >> https://malta.academia.edu/GianmarcoAlberti
> >>
> >> Google Scholar profile
> >> https://scholar.google.com/citations?user=tFrJKQ0J=en
> >>
> >> Correspondence Analysis website
> >> http://cainarchaeology.weebly.com/
> >>
> >> R packages on CRAN:
> >> CAinterprTools
> >> https://cran.r-project.org/web/packages/CAinterprTools/index.html
> >>
> >> GmAMisc
> >> https://cran.r-project.org/package=GmAMisc
> >>
> >> movecost
> >> https://cran.r-project.org/web/packages/movecost/index.html
> >> 
> >> Il 6 lug 2021, 14:53 +0200, brodie gaslam via R-package-devel <
> >> r-package-devel@r-project.org>, ha scritto:
> >>>
>  On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com <
> >> dbosa...@gmail.com> wrote:
> 
>  Martin:
> 
>  What I suggested was he remove the LazyData entry from the description
> >> file
>  if he was NOT lazy loading data.  If someone is lazy loading data,
> >> then that
>  is a different situation, and they obviously need to set the entry.
> 
>  But clearly Gm has a different problem.  He has now tried "LazyData:
> >> true",
>  "LazyData: false", and removing the LazyData entry entirely.  And he
> is
>  still getting this error:
> 
>  * installing *source* package 'movecost' ...
>  ** using staged installation
>  ** R
>  ** data
>  ** byte-compile and prepare package for lazy loading
>  ERROR: lazy loading failed for package 'movecost'
>  * removing 'd:/RCompile/CRANguest/R-release/lib/movecost'
> >>>
> >>> FWIW I think this is lazy loading of the code, which I think is
> >>> different to what LazyData controls.  This is described in
> >>> R-Internals:
> >>>
> >>> https://cran.r-project.org/doc/manuals/R-ints.html#Lazy-loading
> >>>
> >>> I know 

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

[Duncan Murdoch]

Both NegLogoR and movecost have a lot of hard dependencies -- so many 
that I'm unwilling to install them with the limited bandwidth that I 
have right now.  I suspect that's related to the problem:  some 
dependency install is failing, and that causes something else to fail, 
and that leads to the not-very-informative failure messages.


This kind of problem is quite a lot of work to debug.  If I were going 
to attempt to do it, I would go for a bisection strategy:


 - Do you have any old revision which succeeds?  If so, use bisection 
on the revisions until you find the change which first triggers the error.


 - Perhaps no versions succeed, because something external to your 
package has triggered the error.  In this case, bisection would work on 
the dependencies:  cut out half of the dependencies and all the code 
that depends on those.  Have you fixed the error?  If so, add back half 
of the dependencies, otherwise cut out half of the remaining ones.


 - If you're still getting the errors after cutting out all of the 
dependencies, then start cutting out code and data. Etc.


In any case, try to find a version of the package that doesn't trigger 
the error, and a minimal change to it that does.  Then perhaps you'll 
understand the root cause of the error.


Duncan Murdoch

On 06/07/2021 3:11 p.m., Alex Chubaty wrote:

FWIW I'm having the same issue with package NetLogoR (
https://github.com/PredictiveEcology/NetLogoR/)

Passing windows tests locally but code can't be lazy loaded on winbuilder,
except for oldrel.

Alex





On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
gianmarcoalbe...@gmail.com> wrote:


Thank you all. I appreciate your help and discussion so far.

To complicate the matter further, I have done an experiment. I have tried
to test a new version which is 99.9% identical to the last official one on
CRAN because I wanted to understand if the issue was with some  new code
added to the version I have been testing in the last couple of days.

The new version 1.2 (virtually identical to the 1.1 on CRAN) did not pass
the tests as per my earlier description. Same errors. The only Ok is on my
computer and with devtools’ winoldrealeases()

I really don’t know that to do next.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

Il 6 lug 2021, 14:53 +0200, brodie gaslam via R-package-devel <
r-package-devel@r-project.org>, ha scritto:



On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com <

dbosa...@gmail.com> wrote:


Martin:

What I suggested was he remove the LazyData entry from the description

file

if he was NOT lazy loading data.  If someone is lazy loading data,

then that

is a different situation, and they obviously need to set the entry.

But clearly Gm has a different problem.  He has now tried "LazyData:

true",

"LazyData: false", and removing the LazyData entry entirely.  And he is
still getting this error:

* installing *source* package 'movecost' ...
** using staged installation
** R
** data
** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'movecost'
* removing 'd:/RCompile/CRANguest/R-release/lib/movecost'


FWIW I think this is lazy loading of the code, which I think is
different to what LazyData controls.  This is described in
R-Internals:

https://cran.r-project.org/doc/manuals/R-ints.html#Lazy-loading

I know nothing about it so I will not comment further.

Best,

B.

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


 [[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel



[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel



__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Alex Chubaty]

FWIW I'm having the same issue with package NetLogoR (
https://github.com/PredictiveEcology/NetLogoR/)

Passing windows tests locally but code can't be lazy loaded on winbuilder,
except for oldrel.

Alex





On Tue, Jul 6, 2021 at 10:18 AM Gianmarco Alberti <
gianmarcoalbe...@gmail.com> wrote:

> Thank you all. I appreciate your help and discussion so far.
>
> To complicate the matter further, I have done an experiment. I have tried
> to test a new version which is 99.9% identical to the last official one on
> CRAN because I wanted to understand if the issue was with some  new code
> added to the version I have been testing in the last couple of days.
>
> The new version 1.2 (virtually identical to the 1.1 on CRAN) did not pass
> the tests as per my earlier description. Same errors. The only Ok is on my
> computer and with devtools’ winoldrealeases()
>
> I really don’t know that to do next.
>
> Best
> Gm
>
> 
> Dr Gianmarco Alberti (PhD Udine)
> Lecturer in Spatial Forensics
> Coordinator of the BA dissertations
> Department of Criminology
> Faculty for Social Wellbeing
> Room 332, Humanities B (FEMA)
> University of Malta, Msida, Malta (Europe) - MSD 2080
> tel +356 2340 3718
>
> Academic profiles
> https://www.researchgate.net/profile/Gianmarco_Alberti4
> https://malta.academia.edu/GianmarcoAlberti
>
> Google Scholar profile
> https://scholar.google.com/citations?user=tFrJKQ0J=en
>
> Correspondence Analysis website
> http://cainarchaeology.weebly.com/
>
> R packages on CRAN:
> CAinterprTools
> https://cran.r-project.org/web/packages/CAinterprTools/index.html
>
> GmAMisc
> https://cran.r-project.org/package=GmAMisc
>
> movecost
> https://cran.r-project.org/web/packages/movecost/index.html
> 
> Il 6 lug 2021, 14:53 +0200, brodie gaslam via R-package-devel <
> r-package-devel@r-project.org>, ha scritto:
> >
> > > On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com <
> dbosa...@gmail.com> wrote:
> > >
> > > Martin:
> > >
> > > What I suggested was he remove the LazyData entry from the description
> file
> > > if he was NOT lazy loading data.  If someone is lazy loading data,
> then that
> > > is a different situation, and they obviously need to set the entry.
> > >
> > > But clearly Gm has a different problem.  He has now tried "LazyData:
> true",
> > > "LazyData: false", and removing the LazyData entry entirely.  And he is
> > > still getting this error:
> > >
> > > * installing *source* package 'movecost' ...
> > > ** using staged installation
> > > ** R
> > > ** data
> > > ** byte-compile and prepare package for lazy loading
> > > ERROR: lazy loading failed for package 'movecost'
> > > * removing 'd:/RCompile/CRANguest/R-release/lib/movecost'
> >
> > FWIW I think this is lazy loading of the code, which I think is
> > different to what LazyData controls.  This is described in
> > R-Internals:
> >
> > https://cran.r-project.org/doc/manuals/R-ints.html#Lazy-loading
> >
> > I know nothing about it so I will not comment further.
> >
> > Best,
> >
> > B.
> >
> > __
> > R-package-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
>
> [[alternative HTML version deleted]]
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Gianmarco Alberti]

Thank you all. I appreciate your help and discussion so far.

To complicate the matter further, I have done an experiment. I have tried to 
test a new version which is 99.9% identical to the last official one on CRAN 
because I wanted to understand if the issue was with some  new code added to 
the version I have been testing in the last couple of days.

The new version 1.2 (virtually identical to the 1.1 on CRAN) did not pass the 
tests as per my earlier description. Same errors. The only Ok is on my computer 
and with devtools’ winoldrealeases()

I really don’t know that to do next.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

Il 6 lug 2021, 14:53 +0200, brodie gaslam via R-package-devel 
, ha scritto:
>
> > On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com 
> >  wrote:
> >
> > Martin:
> >
> > What I suggested was he remove the LazyData entry from the description file
> > if he was NOT lazy loading data.  If someone is lazy loading data, then that
> > is a different situation, and they obviously need to set the entry.
> >
> > But clearly Gm has a different problem.  He has now tried "LazyData: true",
> > "LazyData: false", and removing the LazyData entry entirely.  And he is
> > still getting this error:
> >
> > * installing *source* package 'movecost' ...
> > ** using staged installation
> > ** R
> > ** data
> > ** byte-compile and prepare package for lazy loading
> > ERROR: lazy loading failed for package 'movecost'
> > * removing 'd:/RCompile/CRANguest/R-release/lib/movecost'
>
> FWIW I think this is lazy loading of the code, which I think is
> different to what LazyData controls.  This is described in
> R-Internals:
>
> https://cran.r-project.org/doc/manuals/R-ints.html#Lazy-loading
>
> I know nothing about it so I will not comment further.
>
> Best,
>
> B.
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[brodie gaslam via R-package-devel]

> On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com 
>  wrote:
>
> Martin:
>
> What I suggested was he remove the LazyData entry from the description file
> if he was NOT lazy loading data.  If someone is lazy loading data, then that
> is a different situation, and they obviously need to set the entry.
>
> But clearly Gm has a different problem.  He has now tried "LazyData: true",
> "LazyData: false", and removing the LazyData entry entirely.  And he is
> still getting this error:
>
> * installing *source* package 'movecost' ...
> ** using staged installation
> ** R
> ** data
> ** byte-compile and prepare package for lazy loading
> ERROR: lazy loading failed for package 'movecost'
> * removing 'd:/RCompile/CRANguest/R-release/lib/movecost'

FWIW I think this is lazy loading of the code, which I think is
 different to what LazyData controls.  This is described in 
R-Internals:

https://cran.r-project.org/doc/manuals/R-ints.html#Lazy-loading

I know nothing about it so I will not comment further.

Best,

B.

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[dbosak01]

Martin:

What I suggested was he remove the LazyData entry from the description file
if he was NOT lazy loading data.  If someone is lazy loading data, then that
is a different situation, and they obviously need to set the entry. 

But clearly Gm has a different problem.  He has now tried "LazyData: true",
"LazyData: false", and removing the LazyData entry entirely.  And he is
still getting this error:  

* installing *source* package 'movecost' ...
** using staged installation
** R
** data
** byte-compile and prepare package for lazy loading
ERROR: lazy loading failed for package 'movecost'
* removing 'd:/RCompile/CRANguest/R-release/lib/movecost'


So changing the description entry isn't helping.  Maybe someone else has a
suggestion of what to try next.


David

-Original Message-
From: Martin Maechler  
Sent: Tuesday, July 6, 2021 6:35 AM
To: David 
Cc: 'Gianmarco Alberti' ;
r-package-devel@r-project.org; 'Uwe Ligges'

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

>>>>>   
>>>>> on Mon, 5 Jul 2021 17:46:54 -0400 writes:

> Gm:


> Did you try completely removing the LazyData line from the
> description file?


> David

Dear David,

where did you get this "idea" that 'LazyData'  is not good  for  R 4.1.0 and
newer ?

R's own  {datasets} package  *does* use lazyloading, and so do most
(formally) recommended packages, and I think most packages I (co-)maintain,
i.e., around two dozen CRAN packages do use lazyloaded data.

---
*) The `Matrix` package is a big exception with 'Lazyload: No'
because its datasets partly are (S4-) classed objects from the package
itself, and -- as the "WRE" ('Writing R Extensions') manual states --
package datasets must not *need* the package itself when they should be lazy
loaded.

Martin

--
Martin Maechler
ETH Zurich  and  R Core Team

 
> From: Gianmarco Alberti ..
> Sent: Monday, July 5, 2021 5:13 PM 
...

> 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 also tried to keep the new dependency and to drop the
> lazy download instead (in DESCRIPTION I have put LazyData:
> false). I got the same results as above.

> The package checks perfectly on my MAC, and checked
> perfectly when I asked a Win users to test the package on
> his PC (with the latest version of R).

> I am really scratching my head.

[]

> On 5 Jul 2021, 13:25 +0200, dbosa...@gmail.com
> <mailto:dbosa...@gmail.com> , wrote:


> 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.

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Martin Maechler]

>   
> on Mon, 5 Jul 2021 17:46:54 -0400 writes:

> Gm:


> Did you try completely removing the LazyData line from the
> description file?


> David

Dear David,

where did you get this "idea" that 'LazyData'  is not good  for
 R 4.1.0 and newer ?

R's own  {datasets} package  *does* use lazyloading, and so do
most (formally) recommended packages, and I think most packages
I (co-)maintain, i.e., around two dozen CRAN packages do use
lazyloaded data.

---
*) The `Matrix` package is a big exception with 'Lazyload: No'
because its datasets partly are (S4-) classed objects from the package
itself, and -- as the "WRE" ('Writing R Extensions') manual
states -- package datasets must not *need* the package itself when
they should be lazy loaded.

Martin

--
Martin Maechler
ETH Zurich  and  R Core Team

 
> From: Gianmarco Alberti ..
> Sent: Monday, July 5, 2021 5:13 PM 
...

> 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 also tried to keep the new dependency and to drop the
> lazy download instead (in DESCRIPTION I have put LazyData:
> false). I got the same results as above.

> The package checks perfectly on my MAC, and checked
> perfectly when I asked a Win users to test the package on
> his PC (with the latest version of R).

> I am really scratching my head.

[]

> On 5 Jul 2021, 13:25 +0200, dbosa...@gmail.com
>  , wrote:


> 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.

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Gianmarco Alberti]

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 Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 23:46 +0200, dbosa...@gmail.com, wrote:
> 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 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.
>
> The new version I am trying to get on CRAN has just one difference: the 
> ‘chorn’ package has been added to the dependencies.
> Now, I have tried to drop that new dependency, and I have run the tests. Same 
> result.
> The test using devtools::check_win_release() and devtools::check_win_devel() 
> both return 1 error (lazy loading failed for package ‘movecost’)
>
> The test using devtools::check_win_oldrelease() is OK.
>
>
> I also tried to keep the new dependency and to drop the lazy download instead 
> (in DESCRIPTION I have put LazyData: false). I got the same results as above.
>
> The package checks perfectly on my MAC, and checked perfectly when I asked a 
> Win users to test the package on his PC (with the latest version of R).
>
>
> I am really scratching my head.
>
> Best
> Gm
>
> 
> Dr Gianmarco Alberti (PhD Udine)
> Lecturer in Spatial Forensics
> Coordinator of the BA dissertations
> Department of Criminology
> Faculty for Social Wellbeing
> Room 332, Humanities B (FEMA)
> University of Malta, Msida, Malta (Europe) - MSD 2080
> tel +356 2340 3718
>
> Academic profiles
> https://www.researchgate.net/profile/Gianmarco_Alberti4
> https://malta.academia.edu/GianmarcoAlberti
>
> Google Scholar profile
> https://scholar.google.com/citations?user=tFrJKQ0J=en
>
> Correspondence Analysis website
> http://cainarchaeology.weebly.com/
>
> R packages on CRAN:
> CAinterprTools
> https://cran.r-project.org/web/packages/CAinterprTools/index.html
>
> GmAMisc
> https://cran.r-project.org/package=GmAMisc
>
> movecost
> https://cran.r-project.org/web/packages/movecost/index.html
> 
> On 5 Jul 2021, 13:25 +0200, dbosa...@gmail.com, wrote:
>
> > 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 
> > Gianmarco Alberti
> > Sent: Monday, July 5, 2021 5:27 AM
> > To: r-package-devel@r-project.org; Uwe Ligges 
> > 
> > Subject: 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
> >
> > devtools::check_win_devel() - 1 ERROR (R Under development (unstable) - 
> > https://win-builder.r-project.org/uQ0LGZ7v0E5h
> >
> > The reported error is to be:
> > ERROR: lazy loading failed for package ‘movecost’
> >
> > Since I couldn’t understand the actual underlying issue, I ran 
> > devtools::ch

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

[dbosak01]

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 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.

 

The new version I am trying to get on CRAN has just one difference: the ‘chorn’ 
package has been added to the dependencies.

Now, I have tried to drop that new dependency, and I have run the tests. Same 
result.

The test using devtools::check_win_release() and devtools::check_win_devel() 
both return 1 error (lazy loading failed for package ‘movecost’)

 

The test using devtools::check_win_oldrelease() is OK.

 

 

I also tried to keep the new dependency and to drop the lazy download instead 
(in DESCRIPTION I have put LazyData: false). I got the same results as above.

 

The package checks perfectly on my MAC, and checked perfectly when I asked a 
Win users to test the package on his PC (with the latest version of R).

 

 

I am really scratching my head.

 

Best

Gm




Dr Gianmarco Alberti (PhD Udine)

Lecturer in Spatial Forensics
Coordinator of the BA dissertations

Department of Criminology

Faculty for Social Wellbeing

Room 332, Humanities B (FEMA)

University of Malta, Msida, Malta (Europe) - MSD 2080

tel +356 2340 3718



Academic profiles

https://www.researchgate.net/profile/Gianmarco_Alberti4

https://malta.academia.edu/GianmarcoAlberti



Google Scholar profile

https://scholar.google.com/citations?user=tFrJKQ0J 
<https://scholar.google.com/citations?user=tFrJKQ0J=en> =en



Correspondence Analysis website

http://cainarchaeology.weebly.com/



R packages on CRAN:

CAinterprTools

https://cran.r-project.org/web/packages/CAinterprTools/index.html



GmAMisc

https://cran.r-project.org/package=GmAMisc



movecost

https://cran.r-project.org/web/packages/movecost/index.html



On 5 Jul 2021, 13:25 +0200, dbosa...@gmail.com <mailto:dbosa...@gmail.com> , 
wrote:



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 mailto:r-package-devel-boun...@r-project.org> > On Behalf Of Gianmarco Alberti
Sent: Monday, July 5, 2021 5:27 AM
To: r-package-devel@r-project.org <mailto:r-package-devel@r-project.org> ; Uwe 
Ligges mailto:lig...@statistik.tu-dortmund.de> >
Subject: 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

devtools::check_win_devel() - 1 ERROR (R Under development (unstable) - 
https://win-builder.r-project.org/uQ0LGZ7v0E5h

The reported error is to be:
ERROR: lazy loading failed for package ‘movecost’

Since I couldn’t understand the actual underlying issue, I ran 
devtools::check_rhub() (as described in my earlier email) which brought to the 
fore the Bioconductor issue.

I have tested the package on Win (R version 4.1) and everything was fine.

I hope I have addressed your question.
Please let me know if you need any other relevant info from my end.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080 tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J 
<https://scholar.google.com/citations?user=tFrJKQ0J=en> =en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 11:20 +0200, Uwe Ligges mailto:lig...@statistik.tu-dortmund.de> >, wrote:



What happens when you test it on winbuilder?
It is configured like the CR

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

[Gianmarco Alberti]

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.

The new version I am trying to get on CRAN has just one difference: the ‘chorn’ 
package has been added to the dependencies.
Now, I have tried to drop that new dependency, and I have run the tests. Same 
result.
The test using devtools::check_win_release() and devtools::check_win_devel() 
both return 1 error (lazy loading failed for package ‘movecost’)

The test using devtools::check_win_oldrelease() is OK.


I also tried to keep the new dependency and to drop the lazy download instead 
(in DESCRIPTION I have put LazyData: false). I got the same results as above.

The package checks perfectly on my MAC, and checked perfectly when I asked a 
Win users to test the package on his PC (with the latest version of R).


I am really scratching my head.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 13:25 +0200, dbosa...@gmail.com, wrote:
> 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 
> Gianmarco Alberti
> Sent: Monday, July 5, 2021 5:27 AM
> To: r-package-devel@r-project.org; Uwe Ligges 
> 
> Subject: 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
>
> devtools::check_win_devel() - 1 ERROR (R Under development (unstable) - 
> https://win-builder.r-project.org/uQ0LGZ7v0E5h
>
> The reported error is to be:
> ERROR: lazy loading failed for package ‘movecost’
>
> Since I couldn’t understand the actual underlying issue, I ran 
> devtools::check_rhub() (as described in my earlier email) which brought to 
> the fore the Bioconductor issue.
>
> I have tested the package on Win (R version 4.1) and everything was fine.
>
> I hope I have addressed your question.
> Please let me know if you need any other relevant info from my end.
>
> Best
> Gm
>
> 
> Dr Gianmarco Alberti (PhD Udine)
> Lecturer in Spatial Forensics
> Coordinator of the BA dissertations
> Department of Criminology
> Faculty for Social Wellbeing
> Room 332, Humanities B (FEMA)
> University of Malta, Msida, Malta (Europe) - MSD 2080 tel +356 2340 3718
>
> Academic profiles
> https://www.researchgate.net/profile/Gianmarco_Alberti4
> https://malta.academia.edu/GianmarcoAlberti
>
> Google Scholar profile
> https://scholar.google.com/citations?user=tFrJKQ0J=en
>
> Correspondence Analysis website
> http://cainarchaeology.weebly.com/
>
> R packages on CRAN:
> CAinterprTools
> https://cran.r-project.org/web/packages/CAinterprTools/index.html
>
> GmAMisc
> https://cran.r-project.org/package=GmAMisc
>
> movecost
> https://cran.r-project.org/web/packages/movecost/index.html
> 
> On 5 Jul 2021, 11:20 +0200, Uwe Ligges , 
> wrote:
> > 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 
> > > would appreciate feedback.
> > >
> &g

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

[dbosak01]

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 
Gianmarco Alberti
Sent: Monday, July 5, 2021 5:27 AM
To: r-package-devel@r-project.org; Uwe Ligges 
Subject: 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

devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
https://win-builder.r-project.org/uQ0LGZ7v0E5h

The reported error is to be:
ERROR: lazy loading failed for package ‘movecost’

Since I couldn’t understand the actual underlying issue, I ran 
devtools::check_rhub() (as described in my earlier email) which brought to the 
fore the Bioconductor issue.

I have tested the package on Win (R version 4.1) and everything was fine.

I hope I have addressed your question.
Please let me know if you need any other relevant info from my end.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080 tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 11:20 +0200, Uwe Ligges , wrote:
> 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 
> > 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 complete report that I got from devtools::check_rhub() is here:
> > https://builder.r-hub.io/status/movecost_1.2.tar.gz-cbda0dbe4d7a4144
> > 98921e9ab2a54aaf
> >
> >
> > Any idea about how to proceed in order for me to get my package on CRAN?
> > I am noticing that I am not the only one experiencing that isse 
> > (https://github.com/r-hub/rhub/issues/471).
> >
> > Best
> > GmA
> >
> > 
> > Dr Gianmarco Alberti (PhD Udine)
> > Lecturer in Spatial Forensics
> > Coordinator of the BA dissertations
> > Department of Criminology
> > Faculty for Social Wellbeing
> > Room 332, Humanities B (FEMA)
> > University of Malta, Msida, Malta (Europe) - MSD 2080 tel +356 2340 
> > 3718
> >
> > Academic profiles
> > https://www.researchgate.net/profile/Gianmarco_Alberti4
> > https://malta.academia.edu/GianmarcoAlberti
> >
> > Google Scholar profile
> > https://scholar.google.com/citations?user=tFrJKQ0J=en
> >
> > Correspondence Analysis website
> > http://cainarchaeology.weebly.com/
> >
> > R packages on CRAN:
> > CAinterprTools
> > https://cran.r-project.org/web/packages/CAinterprTools/index.html
> >
> > GmAMisc
> > https://cran.r-project.org/package=GmAMisc
> >
> > movecost
> > https://cran.r-project.org/web/packages/movecost/index.html
> > 
> > On 5 Jul 2021, 09:49 +0200, Gianmarco Alberti , 
> > wrote:
> > > 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
> > >
> > > devtools::check_win_release() 

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

[Gábor Csárdi]

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 and R CMD check still try to install the
package for i386 as well. Dependencies (e.g. chron in this case) will
not be available on i386.

At least this is the issue for R-hub, because it uses CRAN binaries by
default: 
https://artifacts.r-hub.io/movecost_1.2.tar.gz-cbda0dbe4d7a414498921e9ab2a54aaf/movecost.Rcheck/00install.out

AFAICT Win-builder has its own package library, which might have i386
support, I don't know. So maybe the issue is different there.

Gabor

On Mon, Jul 5, 2021 at 11:27 AM Gianmarco Alberti
 wrote:
>
> 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
>
> devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
> https://win-builder.r-project.org/uQ0LGZ7v0E5h
>
> The reported error is to be:
> ERROR: lazy loading failed for package ‘movecost’
>
> Since I couldn’t understand the actual underlying issue, I ran 
> devtools::check_rhub() (as described in my earlier email) which brought to 
> the fore the Bioconductor issue.
>
> I have tested the package on Win (R version 4.1) and everything was fine.
>
> I hope I have addressed your question.
> Please let me know if you need any other relevant info from my end.
>
> Best
> Gm
>
> 
> Dr Gianmarco Alberti (PhD Udine)
> Lecturer in Spatial Forensics
> Coordinator of the BA dissertations
> Department of Criminology
> Faculty for Social Wellbeing
> Room 332, Humanities B (FEMA)
> University of Malta, Msida, Malta (Europe) - MSD 2080
> tel +356 2340 3718
>
> Academic profiles
> https://www.researchgate.net/profile/Gianmarco_Alberti4
> https://malta.academia.edu/GianmarcoAlberti
>
> Google Scholar profile
> https://scholar.google.com/citations?user=tFrJKQ0J=en
>
> Correspondence Analysis website
> http://cainarchaeology.weebly.com/
>
> R packages on CRAN:
> CAinterprTools
> https://cran.r-project.org/web/packages/CAinterprTools/index.html
>
> GmAMisc
> https://cran.r-project.org/package=GmAMisc
>
> movecost
> https://cran.r-project.org/web/packages/movecost/index.html
> 
> On 5 Jul 2021, 11:20 +0200, Uwe Ligges , 
> wrote:
> > 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 
> > > 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 complete report that I got from devtools::check_rhub() is here:
> > > https://builder.r-hub.io/status/movecost_1.2.tar.gz-cbda0dbe4d7a414498921e9ab2a54aaf
> > >
> > >
> > > Any idea about how to proceed in order for me to get my package on CRAN?
> > > I am noticing that I am not the only one experiencing that isse 
> > > (https://github.com/r-hub/rhub/issues/471).
> > >
> > > Best
> > > GmA
> > >
> > > 
> > > Dr Gianmarco Alberti (PhD Udine)
> > > Lecturer in Spatial Forensics
> > > Coordinator of the BA dissertations
> > > Department of Criminology
> > > Faculty for Social Wellbeing
> > > Room 332, Humanities B (FEMA)
> > > University of Malta, Msida, Malta (Europe) - MSD 2080
> > > tel +356 2340 3718
> > >
> > > Academic profiles
> > > https://www.researchgate.net/profile/Gianmarco_Alberti4
> > > https://malta.academia.edu/GianmarcoAlberti
> > >
> > > Google Scholar profile
> > > https://scholar.google.com/citations?user=tFrJKQ0J=en
> > >
> > > Correspondence Analysis website
> > > http://cainarchaeology.weebly.com/
> > >
> > > R packages on CRAN:
> > > CAinterprTools
> > > https://cran.r-project.org/web/packages/CAinterprTools/index.html
> > >
> > > GmAMisc
> > > https://cran.r-project.org/package=GmAMisc
> > >
> > > movecost
> > > https://cran.r-project.org/web/packages/movecost/index.html
> > > 
> > > On 5 Jul 2021, 09:49 +0200, Gianmarco Alberti 
> > > , wrote:
> > > > 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:
> > > > 

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

[Gianmarco Alberti]

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

devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
https://win-builder.r-project.org/uQ0LGZ7v0E5h

The reported error is to be:
ERROR: lazy loading failed for package ‘movecost’

Since I couldn’t understand the actual underlying issue, I ran 
devtools::check_rhub() (as described in my earlier email) which brought to the 
fore the Bioconductor issue.

I have tested the package on Win (R version 4.1) and everything was fine.

I hope I have addressed your question.
Please let me know if you need any other relevant info from my end.

Best
Gm


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 11:20 +0200, Uwe Ligges , wrote:
> 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 
> > 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 complete report that I got from devtools::check_rhub() is here:
> > https://builder.r-hub.io/status/movecost_1.2.tar.gz-cbda0dbe4d7a414498921e9ab2a54aaf
> >
> >
> > Any idea about how to proceed in order for me to get my package on CRAN?
> > I am noticing that I am not the only one experiencing that isse 
> > (https://github.com/r-hub/rhub/issues/471).
> >
> > Best
> > GmA
> >
> > 
> > Dr Gianmarco Alberti (PhD Udine)
> > Lecturer in Spatial Forensics
> > Coordinator of the BA dissertations
> > Department of Criminology
> > Faculty for Social Wellbeing
> > Room 332, Humanities B (FEMA)
> > University of Malta, Msida, Malta (Europe) - MSD 2080
> > tel +356 2340 3718
> >
> > Academic profiles
> > https://www.researchgate.net/profile/Gianmarco_Alberti4
> > https://malta.academia.edu/GianmarcoAlberti
> >
> > Google Scholar profile
> > https://scholar.google.com/citations?user=tFrJKQ0J=en
> >
> > Correspondence Analysis website
> > http://cainarchaeology.weebly.com/
> >
> > R packages on CRAN:
> > CAinterprTools
> > https://cran.r-project.org/web/packages/CAinterprTools/index.html
> >
> > GmAMisc
> > https://cran.r-project.org/package=GmAMisc
> >
> > movecost
> > https://cran.r-project.org/web/packages/movecost/index.html
> > 
> > On 5 Jul 2021, 09:49 +0200, Gianmarco Alberti , 
> > wrote:
> > > 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
> > >
> > > devtools::check_win_release() - 1 ERROR (R version 4.1.0) - 
> > > https://win-builder.r-project.org/hlA15dFq5BdR
> > >
> > > devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
> > > https://win-builder.r-project.org/uQ0LGZ7v0E5h
> > >
> > > The reported error seems to be:
> > > ERROR: lazy loading failed for package ‘movecost'
> > >
> > >
> > > I have asked a friend to run devtools::check() on his Win-based machine 
> > > (running R version 4.1.0), and the test returned no problems (0 error, 0 
> > > warning, 0 notes).
> > >
> > > Since I cannot reproduce the error neither on my computer nor on a 
> > > win-based machine, I am at loss of understanding where the issue actually 
> > > lies.
> > >
> > > I would really appreciate any help and/or suggestion.
> > >
> > > Best
> > > Gianmarco
> > >
> > >
> > >
> > >
> > > 
> > > Dr Gianmarco Alberti (PhD Udine)
> > > Lecturer 

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

[Uwe Ligges]

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 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 complete report that I got from devtools::check_rhub() is here:
https://builder.r-hub.io/status/movecost_1.2.tar.gz-cbda0dbe4d7a414498921e9ab2a54aaf


Any idea about how to proceed in order for me to get my package on CRAN?
I am noticing that I am not the only one experiencing that isse 
(https://github.com/r-hub/rhub/issues/471).

Best
GmA


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 09:49 +0200, Gianmarco Alberti , 
wrote:

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

devtools::check_win_release() - 1 ERROR (R version 4.1.0) - 
https://win-builder.r-project.org/hlA15dFq5BdR

devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
https://win-builder.r-project.org/uQ0LGZ7v0E5h

The reported error seems to be:
ERROR: lazy loading failed for package ‘movecost'


I have asked a friend to run devtools::check() on his Win-based machine 
(running R version 4.1.0), and the test returned no problems (0 error, 0 
warning, 0 notes).

Since I cannot reproduce the error neither on my computer nor on a win-based 
machine, I am at loss of understanding where the issue actually lies.

I would really appreciate any help and/or suggestion.

Best
Gianmarco





Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html



[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel



__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Gianmarco Alberti]

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 complete report that I got from devtools::check_rhub() is here:
https://builder.r-hub.io/status/movecost_1.2.tar.gz-cbda0dbe4d7a414498921e9ab2a54aaf


Any idea about how to proceed in order for me to get my package on CRAN?
I am noticing that I am not the only one experiencing that isse 
(https://github.com/r-hub/rhub/issues/471).

Best
GmA


Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html

On 5 Jul 2021, 09:49 +0200, Gianmarco Alberti , 
wrote:
> 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
>
> devtools::check_win_release() - 1 ERROR (R version 4.1.0) - 
> https://win-builder.r-project.org/hlA15dFq5BdR
>
> devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
> https://win-builder.r-project.org/uQ0LGZ7v0E5h
>
> The reported error seems to be:
> ERROR: lazy loading failed for package ‘movecost'
>
>
> I have asked a friend to run devtools::check() on his Win-based machine 
> (running R version 4.1.0), and the test returned no problems (0 error, 0 
> warning, 0 notes).
>
> Since I cannot reproduce the error neither on my computer nor on a win-based 
> machine, I am at loss of understanding where the issue actually lies.
>
> I would really appreciate any help and/or suggestion.
>
> Best
> Gianmarco
>
>
>
>
> 
> Dr Gianmarco Alberti (PhD Udine)
> Lecturer in Spatial Forensics
> Coordinator of the BA dissertations
> Department of Criminology
> Faculty for Social Wellbeing
> Room 332, Humanities B (FEMA)
> University of Malta, Msida, Malta (Europe) - MSD 2080
> tel +356 2340 3718
>
> Academic profiles
> https://www.researchgate.net/profile/Gianmarco_Alberti4
> https://malta.academia.edu/GianmarcoAlberti
>
> Google Scholar profile
> https://scholar.google.com/citations?user=tFrJKQ0J=en
>
> Correspondence Analysis website
> http://cainarchaeology.weebly.com/
>
> R packages on CRAN:
> CAinterprTools
> https://cran.r-project.org/web/packages/CAinterprTools/index.html
>
> GmAMisc
> https://cran.r-project.org/package=GmAMisc
>
> movecost
> https://cran.r-project.org/web/packages/movecost/index.html
> 

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[Gianmarco Alberti]

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

devtools::check_win_release() - 1 ERROR (R version 4.1.0) - 
https://win-builder.r-project.org/hlA15dFq5BdR

devtools::check_win_devel()  - 1 ERROR (R Under development (unstable) - 
https://win-builder.r-project.org/uQ0LGZ7v0E5h

The reported error seems to be:
ERROR: lazy loading failed for package ‘movecost'


I have asked a friend to run devtools::check() on his Win-based machine 
(running R version 4.1.0), and the test returned no problems (0 error, 0 
warning, 0 notes).

Since I cannot reproduce the error neither on my computer nor on a win-based 
machine, I am at loss of understanding where the issue actually lies.

I would really appreciate any help and/or suggestion.

Best
Gianmarco





Dr Gianmarco Alberti (PhD Udine)
Lecturer in Spatial Forensics
Coordinator of the BA dissertations
Department of Criminology
Faculty for Social Wellbeing
Room 332, Humanities B (FEMA)
University of Malta, Msida, Malta (Europe) - MSD 2080
tel +356 2340 3718

Academic profiles
https://www.researchgate.net/profile/Gianmarco_Alberti4
https://malta.academia.edu/GianmarcoAlberti

Google Scholar profile
https://scholar.google.com/citations?user=tFrJKQ0J=en

Correspondence Analysis website
http://cainarchaeology.weebly.com/

R packages on CRAN:
CAinterprTools
https://cran.r-project.org/web/packages/CAinterprTools/index.html

GmAMisc
https://cran.r-project.org/package=GmAMisc

movecost
https://cran.r-project.org/web/packages/movecost/index.html


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel