@Gabor , I am having some really inconsistent and maddening errors coming through when I try to do development using the ADOS as described here withpak::pkg_install. Note that this is still using the devel version as the current release does not work at all for this.
The issue always arises when trying to use the repository URL, but not when using the local-on-machine location with pak::pkg_install. Further, remotes::install_git works just fine. I can build and check as such using devtools and can install using basic installation from local zip files, etc. So this really only appears when I'm using pakwith the remote.
If the local copy is up-to-date and I try to use the URL, I get a successful notification that No downloads are needed, so that tells me that pak can communicate with the repo and determine that the local version is up-to-date with the remote version.
However, when I update the remote version and then try to install it, I get the following error:
ℹ Packaging <package> <version>
Installing...
✔ Packaged <package> <version> (300ms)
ℹ Building <package> <version>
✖ Failed to build <package> <version>
Error:
! error in pak subprocess
Caused by error in `stop_task_build(state, worker)`:
! Failed to build source package '<package>'
Full installation output:
* installing *source* package '<package>' ...
staged installation is only possible with locking
** using non-staged installation
** help
No man pages found in package '<package>'
*** installing help indices
** building package indices
** testing if installed package can be loaded
Warning: S3 method '<method>' was declared in NAMESPACE but not found
Error: package or namespace load failed for '<package>' in namespaceExport(ns, exports):
undefined exports: <function names...>
Error: loading failed
Execution halted
ERROR: loading failed
* removing '<temp file location>'
Type .Last.error to see the more details.
which tells me the same set of errors regarding the "undefined exports" and lack of man pages. And to be clear, that method and those functions are defined and exported and listed in the NAMESPACE file, so that's not actually the problem.
If I try to run again I get a different error for every time thereafter:
Installing...
ℹ Building <package> <version>
Installing...
Error:
! error in pak subprocess
Caused by error in `read.dcf(con)`:
! Line starting '<package>/DESCRIPTION ...' is malformed!
Type .Last.error to see the more details.
which tells me
Error:
! error in pak subprocess
Caused by error in `read.dcf(con)`:
! Line starting '<package>/DESCRIPTION ...' is malformed!
but again, I know that it's not malformed when I make it locally, and I can run read.dcf on it in the local version without any issue.
I have had the same issue in multiple repositories, so it's not specific to one.
After a few hours digging, I have not been able to trace the error well given the structure of pak (esp the R6 aspects), nor have I been able to consistently recreate the error (sometimes pushing an update to the remotes fixes or causes the error, with seemingly no consistency, I have tried to strip the package down to bare bones but still have been hitting this issue).
Further making things a challenge, given that it's a private agency server, I can't share details and others won't be able to access. I also don't have a personal ADOS server (why would I ever?, I always use github) so I cna't recreate this outside of my workspace or create a reliable reproudcible example. Recognizing that, I realize that we have some serious limitations with what you can help with at this moment, but if you have any ideas, I'd be happy to try.
thanks so much!
