Replies: 3 comments 2 replies
-
@jeroen could you please comment? Then I think it's worth adding to the docs, probably in https://docs.r-universe.dev/publish/troubleshoot-build.html |
Beta Was this translation helpful? Give feedback.
-
The test case, {fasterize}, was moved from
I suppose we need (4) to resolve this? |
Beta Was this translation helpful? Give feedback.
-
Yes those steps sound about right. Indeed updating the package on CRAN will speed up the process. Otherwise it could take up to a month for the https://cran.r-universe.dev/fasterize to get rebuilt and detect the redirected git origin. You can also speed up the process by putting the universe URL in the package description, I think that will instantly fix things. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If a package is on GitHub and CRAN, and on R-Universe through an organization with an R-Universe repo and
packages.json
, what's the best order of operations for moving the package to another GitHub organization?I think it's this:
packages.json
. This will remove it from the original org's universe.2a) If not, make sure the new organization has its own universe and add the package to
packages.json
.Beta Was this translation helpful? Give feedback.
All reactions