Kevin,
R-Forge is still alive but there are problems with the build queue as you
noticed. The problems occurred after R-Forge upgraded to R 4.4.0 - just as
there was a switch in the maintenance team at WU Wien.
The problem is with the Windows build/check tools which work fine when run
manually but either fail (if there is compiled code in the package) or stall
when run in batch mode.
Jorge, the new member in the admin team at WU, has been going through all the
scripts with Uwe (Ligges) but they haven't spotted the problem so far. I think
that the next step will be to migrate the Windows build/check processes to the
Win-Builder machine.
I hope that they will succeed in doing so in the next weeks. Apologies for the
inconvenience.
Best wishes,
Achim
On Tue, 2 Jul 2024, Kevin R. Coombes wrote:
Hi,
I have been maintaining packages in R-Forge for many tears. Last week I sent
an email to r-fo...@r-project.org to report problems with the build process.
It appears that any changes I have pushed to R-Forge over approximately the
last two months have resulted in the package remaining in the "Building"
state, even though the logs suggest that the package built successfully on
both LINUX and Windows. (Also, four of the six affected packages only
included changes to the man pages to clean up NOTEs from the R cmd checks on
old versions at CRAN, where the new versions now happily reside.) I have
received no response nor acknowledgement to my email to R-Forge.
Assuming that R-Forge has finally succumbed to the ravages of entropy, does
anyone have advice on creating a git project that contains multiple R
packages? (I really don't want to have to create 20+ new git projects, one
per package).
Best,
Kevin
______________________________________________
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
