-
Notifications
You must be signed in to change notification settings - Fork 33
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
BH 1.81.0 upgrade plan #88
Comments
I just submitted If anyone is interested in the fix, boost::beast string views switched internally from boost::detail::basic_string_view to boost::core::basic_string_view in the latest version. Of these the current one does not have a .to_string() method. Edit: It was rejected in pretest due to (I believe) (#89). I have informed CRAN. |
Thank you so much, also for the added color. I have seen (And good luck with CRAN. I always found them reasonable when I replied on such false positives. And an updated BH will be coming if all goes well by mid-Jan. Speaking of which, any update from the stan world @bgoodri ?) |
I have a real fix. Just testing the reverse dependencies. |
I would like to upload BH in the next few days. Of the six packages, only one ( Thoughts? |
I uploaded rstan to CRAN. It should be fine, but won't be approved until tomorrow at the earliest. |
Cool, thanks for the update! I will try to follow-up with BH and we can continue to coordinate here. Edit: With |
Seems like BH 1.81 is now on CRAN. |
Correct. It is now up on CRAN, I mentioned this issue, the two closed one and your 'pending' I will close this issue as completed, we can still discuss here needed. Big big thanks to everybody for the prompt help. |
@nx10: Yay! Glad to see it back! |
Thanks! They requested a couple documentation changes so it got delayed again. 2.0 soon™ |
Boost released 1.81.0 this week, and the BH package was updated to release 1.81.0-0 in PR #87. It can be accessed from the ghrr drat via
and similarly from r-universe. As usual we ran full reverse-dependency checks on Debian testing system (where gcc-12 is the default). The logs are in this commit at the rcpp-logs repo are reveal issues in these six packages
vector
) (maintainer emailed 2022-12-16) (heard back 2022-12-26, 'January should be fine') (version 1.9 on CRAN 2023-02-04)I have or will contact all maintainers by either email or PR. The plan would be to get all packages fixed in four weeks from now to permit a mid-January CRAN upload of BH 1.81.0.
Edit 2022-12-30 We now have 1.81.0-1 (via #90) which had another round of reverse-depends checks which revealed no new or changed issue.
The text was updated successfully, but these errors were encountered: