Hello Spencer and thank you for your reply.
This is a good point as the package is indeed on GitHub, so I will
investigate it. But, like you pointed out, it is doubtful if testing on
these other systems (including Ubuntu) will catch a problem that is
reported on Debian.
And what causes it seems even more of a mystery to me.
Thanks again.
V.
Στις 2023-02-20 20:52, Spencer Graves έγραψε:
Hi, Vasileios:
Do you have it on GitHub?
If yes, do you use "GitHub Action" to test the package on multiple
platforms? I'm a contributor to the "fda" package. It's version on
GitHub is configured so every "git push" triggers auto tests on five
different platforms, testing it against the current "release" version
of R on the latest versions of macOS, Windows and Ubuntu plus the
development and previous release on Ubuntu.[1] I don't know if GitHub
action would support testing under Debian nor if testing under Ubuntu
would catch the problem that CRAN is catching on Debian.
However, having the package on GitHub also makes it easier for
someone else to clone the package and test it it for you ;-) This
community of R developers provides very valuable support for problems
like this.
Hope this help.
Spencer Graves
[1]https://github.com/JamesRamsay5/fda/blob/master/.github/workflows/R-CMD-check.yaml
On 2/20/23 6:38 AM, Vasileios Nikolaidis wrote:
Dear R-developers, I apologize for posting something that has probably
been discussed before (but missed it while searching the archives).
While trying to submit a newer version of my package to CRAN, it is
rejected as it fails on Debian. I will call this package APACKAGE
below (although it is named differently). It has passed all checks on
my Windows system (no errors or warnings).
The package (for many versions now) is configured as follows:
Imports: Rcpp , methods
LinkingTo: Rcpp
Suggests: R.rsp
The previous version of the package (already on CRAN) shows no errors
on CRAN checks, only NOTES for some platforms. Interestingly, a couple
of days ago I checked the CRAN checks and noticed that this exact
(previous) version of the package had one ERROR indicated, occurring
in some Debian flavor (r-devel-linux-x86_64-debian-gcc, if I remember
correctly). I changed nothing, but now it shows no errors for all
platforms (including Debian).
Now I am trying to submit a newer version and it not accepted as it
fails on Debian. Checking the log I see no syntax errors or warnings.
** testing if installed package can be loaded from temporary location
Error: package or namespace load failed for ‘APACKAGE’ in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
‘/srv/hornik/tmp/CRAN/APACKAGE.Rcheck/00LOCK-APACKAGE/00new/APACKAGE/libs/APACKAGE.so’:
/srv/hornik/tmp/CRAN/APACKAGE.Rcheck/00LOCK-APACKAGE/00new/APACKAGE/libs/APACKAGE.so:
undefined symbol: _ZTIN6nnlib25layerE
Error: loading failed.
I tried the R-Hub builder and it also fails for Platform Debian Linux,
R-devel, GCC. The process goes fine until the following:
Error: package or namespace load failed for ‘APACKAGE’ in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
'/home/docker/R/00LOCK-APACKAGE/00new/APACKAGE/libs/APACKAGE.so':
/home/docker/R/00LOCK-APACKAGE/00new/APACKAGE/libs/APACKAGE.so:
undefined symbol: _ZTIN6nnlib25layerE
Error: loading failed
Execution halted
ERROR: loading failed
* removing ‘/home/docker/R/APACKAGE’
Warning message:
In i.p(...) :
installation of package
‘/tmp/Rtmp7eBDvE/file1377f5861e3/APACKAGE_0.2.0.tar.gz’ had non-zero
exit status
It maybe something obvious, but I really cannot think of what else to
try to fix this issue.
Any help will be greatly appreciated.
______________________________________________
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
