-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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] DESCRIPTION changes to address CRAN feedback #3298
Conversation
@guolinke Could we submit to CRAN again? I want to be sure that this PR fixes the "misspelling" issue and gets us a different failure on Windows. I just built a package that could be submitted, from this branch: |
trying to fix this issue
The regex for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for trying so hard!
LGTM, but please check my inline comment: #3298 (comment).
Co-authored-by: Nikita Titov <[email protected]>
thanks @guolinke ! Ok I just added notes to I just pushed another set of changes. At your earliest convenience, could you try another submission with this tarball? |
@jameslamb it takes a long time to get the result this time... |
Thanks @guolinke . Ok this is good, I think this PR can be merged once CI finishes building. The 1 NOTE on both platforms can be safely ignored...it's just something that CRAN shows when you submit a package that isn't on CRAN yet. The ERROR on Windows would be fixed by #3187 . Now we have absolute, definitive evidence that #3187 is required...before this, I was pretty sure but not certain. Whenever you or @shiyu1994 pick that up, let me know if there's anything I can do to help. I can definitely create a CI job for 32-bit R based on #3187 (comment), and could help with any other setup. |
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
This addresses feedback from our first ever submission to CRAN!
#629 (comment)
LightGBM
in quotes. I remember we had to do this when we first submitteduptasticsearch
Biarch: false
inDESCRIPTION
. I thought that flag could be a way to publish a package that doesn't support 32-bit, but I don't think that works. Let's remove that field and we'll get a better error on CRAN 32-bit checks.This also proposes adding a
cran-comments.md
to track feedback from CRAN. Since the CRAN upload process involves back-and-forth with humans (not just automated checks), a lot of projects keep this type of file to hold a record of the things CRAN has asked them to do in the past. We do this inuptasticsearch
.