-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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] arrow violates the CRAN policy on downloading binary software #39806
Comments
Thanks for letting us know about this @rafapereirabr. Please bear with us for the moment; we are working to get this resolved before their deadline. We’ll let you know as soon as we have an update. |
Thanks to the arrow team for dealing with this. You probably know all this already but fwiw, CRAN policy has always allowed binary installs "with permission" (from CRAN) and continues to host packages that install software binaries.
|
@rafapereirabr The |
Thanks for sharing this info, @gilbertocamara . I hope the @apache team will find a similar solution to this issue. |
Hi, I wish you a lot of strength @thisisnic . Your package is awesome, it has become a must-have for R. I use it everyday. Thank you for your precious work. |
Thanks @arnaud-feldmann, though the arrow R package is a team effort and definitely not just me! Things are progressing anyway - we'll update the community in due course. |
Hi folks, We’re still working to respond to CRAN’s evolving requirements on external C++ libraries, and while we believe we know what we need to do to meet the new requirements, it’s not clear that we can resolve everything before February 9. As an interim measure, we are starting to submit PRs to packages that import arrow to make sure they have the updates they need to stay on CRAN while arrow is removed. It won’t be possible for us to get to all of the packages that rely on arrow, but if we haven’t gotten to yours, feel free to ping us here and we can make suggestions and offer code review. For packages that We are committed to doing what it takes to maintaining arrow on CRAN. If arrow gets removed this week, we will work to resubmit it as soon as possible. Nic and the arrow team |
Are there any updates regarding the Feb 9 deadline? Arrow is obviously not archived yet, so has CRAN postponed the deadline? |
We've submitted another version of the R package and also emailed CRAN to discuss some details, but have not heard back from them yet. The new version of the R package is currently pending manual inspection. We haven't had any further interaction with CRAN regarding the deadline. |
Thank you for the update @thisisnic! And thank you for working through this! |
@thisisnic Just a note / guess / question from afar (while having a package that "Suggests: arrow" on hold at CRAN in 'inspect'): the issues seen at the CRAN results page also bite. Does the pending 14.0.2.1 overcome those clang issues? |
@eddelbuettel Yeah, thanks for pointing that out, but we do keep an eye on that stuff as it's pretty essential. |
I am sure you do @thisisnic -- and thanks for looking after it. Any idea if/when the (FWIW the Vienna machine had an impasse where it didn't build Rcpp either, which was resolved AFAIK by rolling back at their end. I have less insight into the Fedora issue. It all looks a little like an upstream clang problem?) |
It's resolved on our end, as mentioned above we are pending manual inspection and that hasn't changed. You'd have to ask CRAN 🤷 |
Sounds good, and thanks! I am in the same boat but behind you 'waiting on your issue to resolved'. It is always a little hard to tell from the outside, but it did look like we are currently waiting only on them so thanks for confirming, and let's hope they get their clang17 setup sorted out. |
Right, that makes sense! I think we ended up with a slightly different fix to you - we needed to update one of our C++ headers to include something we weren't including before and that resolved the issue, so we didn't end up asking them to change anything about their setup. |
@eddelbuettel In case you're curious: #40010 |
Dammit Dirk, I wanted to post the update 😂 Yep, thanks for bearing with us folks, version 14.0.2.1 is now on CRAN, with the previous issues resolved! |
Thanks @thisisnic and the {arrow} team ! |
Describe the bug, including details regarding any error messages, version, and platform.
Hi all. Several package developers who maintain packages that depend on
arrow
received this email below from CRAN:arrow
is a game changer in R, so I'm opening this issue hopping the developer community can find a solution to this. Thank you for a fantasticarrow
package in R.Component(s)
R
The text was updated successfully, but these errors were encountered: