Replies: 3 comments 1 reply
-
OK you seem to have a legitimate use case. I'll bump the global limit to 150. We have a limit to prevent people from abusing resources by just creating universes with a ton of packages that aren't theirs. |
Beta Was this translation helpful? Give feedback.
1 reply
-
OK the limit is bumped now, can you fix the remaining problems on https://github.com/r-universe/phylotastic/actions/runs/5068762252/jobs/9101477740 ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks! I'll fix those now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I maintain https://phylotastic.r-universe.dev/builds from the repo https://github.com/phylotastic/phylotastic.r-universe.dev. I'm also a maintainer of the CRAN task view for phylogenetics. R-universe is great -- it's helped buffer our community against issues when one core package is at risk of being tossed from CRAN, for example.
However, our universe instance hasn't updated since March. I was trying to debug why it has stopped updating -- turns out as a personal instance it's limited to 100 packages, and I currently have 114.
What's the best procedure here? Is there a way to upgrade to a "community" instance? Should I have one for packages A-M and one for packages N-Z? etc.? I'll temporarily remove 14 packages, but it would be great to have all the ones in our community be available.
And thank you for all the work on R-universe -- it's really great.
Beta Was this translation helpful? Give feedback.
All reactions