-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[R-package] CRAN requires a new release by Feb 14th #6791
Comments
To my knowledge, this information is wrong. GPBoost has some UBSAN issues, but these are not due to LightGBM. |
Ok great, thank you for the link and quick response! |
v4.6.0 is now on CRAN, and the Leaving this open though, because the jobs with those bashisms issues haven't been re-run, so those still show up at https://cran.r-project.org/web/checks/check_results_lightgbm.html. |
The bashisms issue is also now resolved at https://cran.r-project.org/web/checks/check_results_lightgbm.html Almost all of the CRAN checks have been run on
Which are not a problem... they've been there for as long as LightGBM was on CRAN and CRAN treats them as informational-only. This can now be closed. |
Description
On January 14th, I received the following email from Dr. Brian Ripley (speaking on behalf of CRAN):
To stay on CRAN, we must put up a new release (at least of the R package) by February 14th.
Notes
Problem 1: "installation issues on Alpine Linux"
details: https://cran.r-project.org/web/checks/check_results_lightgbm.html
fixed by: #6746
Problem 2: "GCC 15 has now reached 'stage 4'"
details: https://www.stats.ox.ac.uk/pub/bdr/gcc15/lightgbm.out)
fixed by: #6736
Problem 3: "lightgbm is also causing UBSAN issues in package gpboost"
Not sure what this refers to. I don't see any issues at these places:
@fabsig what does this note from CRAN refer to?
The text was updated successfully, but these errors were encountered: