[R-pkg-devel] clarification about missing suggested packages.

[Ben Bolker]

  We are working on a resubmission of a package 
(https://github.com/glmmTMB/glmmTMB/issues/721 for people who want all 
the gory details). Our last hurdle is that one of the packages in 
"Suggests:", DHARMa, is currently unavailable on Solaris, even though it 
in good standing on CRAN 
. (This stems 
from a circular dependency: DHARMa can't be built on Solaris because the 
_previous_ version of glmmTMB, which DHARMa imports, had a bug on 
Solaris ...)


  We have been testing on r-hub's solaris platform, where DHARMa is 
similarly unavailable. We can only pass tests if we set 
_R_CHECK_FORCE_SUGGESTS_=false; otherwise we get an error that says some 
suggested packages are missing.


  It is my understanding that the CRAN maintainers can either

   * test with _R_CHECK_FORCE_SUGGESTS_=false and yell at us if we have 
used any missing/unavailable packages unconditionally or


   * test with _R_CHECK_FORCE_SUGGESTS_=true and ensure that all 
suggested packages are installed


but that it would be unreasonable to reject package A because it has a 
Suggests: dependency on package B that is in good standing on CRAN but 
is not available on a particular CRAN testing platform, as long as 
package A only uses package B conditionally.


  Thoughts/opinions/evidence?

  cheers
Ben Bolker

---
From the current CRAN policy:

Packages on which a CRAN package depends should be available from a 
mainstream repository: if any mentioned in ‘Suggests’ or ‘Enhances’ 
fields are not from such a repository, where to obtain them at a 
repository should be specified in an ‘Additional_repositories’ field of 
the DESCRIPTION file (as a comma-separated list of repository URLs) or 
for other means of access, described in the ‘Description’ field.


A package listed in ‘Suggests’ or ‘Enhances’ should be used 
conditionally in examples or tests if it cannot straightforwardly be 
installed on the major R platforms. (‘Writing R Extensions’ recommends 
that they are always used conditionally.)


__
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

[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  > 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
> 
> )
>  >
>  > 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 

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