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=tFrJKQ0AAAAJ&hl=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
