-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current CRAN failures and potential removal #586
Comments
Aside from the I fixed that particular issue as part of #574. I'll extract the change to a standalone PR and address the other |
Just double-checking compatibility against 2.26 and 2.31 as well, might as well add the minimum updates needed for that too |
@jgabry are we able to submit updates to CRAN if we can't get in touch with Ben before the archival deadline on the 10th? |
I actually talked to him yesterday. He’s aware of the situation and will
merge your PRs and submit the release in time.
Thanks for your help with this!
…On Tue, Apr 4, 2023 at 2:04 AM Andrew Johnson ***@***.***> wrote:
@jgabry <https://github.com/jgabry> are we able to submit updates to CRAN
if we can't get in touch with Ben before the archival deadline on the 10th?
—
Reply to this email directly, view it on GitHub
<#586 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3PQQ7QHWXIYCX54LLLEXTW7O2WTANCNFSM6AAAAAAWRREGPE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Oh brilliant, thanks for checking! |
Updated rstanarm is now on CRAN |
We've received:
<snip>
Is there anything that we can do? It looks like the issue list isn't terrible (and some are ignorable).
It would be good to know if fixes are in progress.
The text was updated successfully, but these errors were encountered: