You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "amoeba (via GitHub)" <gi...@apache.org> on 2025/03/26 23:07:00 UTC
[I] [R] CRAN packaging checklist for version 19.0.2 [arrow]
amoeba opened a new issue, #45950:
URL: https://github.com/apache/arrow/issues/45950
### Describe the bug, including details regarding any error messages, version, and platform.
The rationale for this release is https://github.com/apache/arrow/issues/45949.
# Packaging Checklist for CRAN Release
For a high-level overview of the Arrow release process see the [Apache Arrow Release Management Guide](https://arrow.apache.org/docs/developers/release.html#post-release-tasks).
## Before the Arrow Release Candidate Is Created
- [ ] [Create a GitHub issue](https://github.com/apache/arrow/issues/new/) entitled `[R] CRAN packaging checklist for version X.Y.Z` and copy this checklist to the issue.
- [ ] Review deprecated functions to advance their deprecation status, including removing preprocessor directives that no longer apply (search for `ARROW_VERSION_MAJOR` in r/src).
- [ ] Evaluate the status of any failing [nightly tests and nightly packaging builds](http://crossbow.voltrondata.com). These checks replicate most of the checks that CRAN runs, so we need them all to be passing or to understand that the failures may (though won't necessarily) result in a rejection from CRAN.
- [ ] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_arrow.html).
- [ ] Ensure the contents of the README are accurate and up to date.
- [ ] Run `urlchecker::url_check()` on the R directory at the release candidate.
commit. Ignore any errors with badges as they will be removed in the CRAN release branch.
- [ ] [Polish NEWS](https://style.tidyverse.org/news.html#news-release) but do **not** update version numbers (this is done automatically later). You can find commits by, for example, `git log --oneline <sha of last release>..HEAD | grep "\[R\]"`.
- [ ] For major releases, prepare content for social media highlighting new features.
_Wait for the release candidate to be created._
## After the Arrow Release Candidate Has Been Created
- [ ] Create a CRAN-release branch from the release candidate commit, name the new branch `maint-X.Y.Z-r` and push to upstream.
## Prepare and Check Package That Will Be Released to CRAN
- [ ] `git fetch upstream && git checkout maint-X.Y.Z-r && git clean -f -d`.
- [ ] Run `make build`. This copies Arrow C++ into tools/cpp, prunes some unnecessary components, and runs `R CMD build` to generate the source tarball. Because this will install the package, you will need to ensure that the version of Arrow C++ available to the configure script is the same as the version that is vendored into the R package (e.g., you may need to unset `ARROW_HOME`).
- [ ] `devtools::check_built("arrow_X.Y.Z.tar.gz")` locally.
## Wait for Arrow Release Vote
- [ ] Release vote passed
## Generate R Package to Submit to CRAN
- [ ] If the release candidate commit updated, rebase the CRAN release branch on that commit.
- [ ] Pick any commits that were made to main since the release commit that were needed to fix CRAN-related submission issues identified in the above steps.
- [ ] Remove badges from README.md.
- [ ] Run `urlchecker::url_check()` on the R directory.
- [ ] Create a PR entitled `WIP: [R] Verify CRAN release-X.Y.Z-rcX`. Add a comment `@github-actions crossbow submit --group r` to run all R crossbow jobs against the CRAN-specific release branch.
- [ ] Run `Rscript tools/update-checksums.R <libarrow version>` to download the checksums for the pre-compiled binaries from the ASF artifactory into the tools directory.
- [ ] Regenerate arrow_X.Y.Z.tar.gz (i.e., `make build`).
## Check Binary Arrow C++ Distributions Specific to the R Package
- [ ] Upload the .tar.gz to [win-builder](https://win-builder.r-project.org/upload.aspx) (r-devel only) and confirm with Jon (who will automatically receive an email about the results) that the check is clean.
- [ ] Upload the .tar.gz to [macOS Builder](https://mac.r-project.org/macbuilder/submit.html) and confirm that the check is clean.
- [ ] Check `install.packages("arrow_X.Y.Z.tar.gz")` on Ubuntu and ensure that the hosted binaries are used.
- [ ] `devtools::check_built("arrow_X.Y.Z.tar.gz")` locally one more time (for luck).
## Submit Package to CRAN
_This step must be done by the current package maintainer._
- [ ] Upload arrow_X.Y.Z.tar.gz to the [CRAN submit page](https://xmpalantir.wu.ac.at/cransubmit/).
- [ ] Confirm the submission email.
## Wait for CRAN to Accept the Submission
- [ ] CRAN has accepted the submission.
- [ ] Tag the tip of the CRAN-specific release branch with `r-universe-release`.
- [ ] Add a new line to the matrix in the [backwards compatability job](https://github.com/apache/arrow/blob/main/dev/tasks/r/github.linux.arrow.version.back.compat.yml).
- [ ] (patch releases only) Update the package version in `ci/scripts/PKGBUILD`, `r/DESCRIPTION`, and `r/NEWS.md`.
- [ ] (CRAN-only releases) Rebuild news page with `pkgdown::build_news()` and submit a PR to the asf-site branch of the docs site with the contents of `arrow/r/docs/news/index.html` replacing the current contents of `arrow-site/docs/r/news/index.html`.
- [ ] (CRAN-only releases) Bump the version number in `r/pkgdown/assets/versions.json`, and update this on the [the `asf-site` branch of the docs site](https://github.com/apache/arrow-site) too..
- [ ] Review the packaging checklist template and update as needed.
- [ ] Wait for CRAN-hosted binaries on the [CRAN package page](https://cran.r-project.org/package=arrow) to reflect the new version.
- [ ] Post already-prepared content to social media.
- Use Bryce's [script](https://gist.githubusercontent.com/amoeba/4e26c064d1a0d0227cd8c2260cf0072a/raw/bc0d983152bdde4820de9074d4caee9986624bc5/new_contributors.R) for contributor calculation.
### Component(s)
R
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba closed issue #45950: [R] CRAN packaging checklist for version 19.0.1.1
URL: https://github.com/apache/arrow/issues/45950
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784486671
I pushed up https://github.com/apache/arrow/commit/b1ebcdb797d11dea36e98974a3941c028b404715 which I am hoping will work but I haven't tested it properly. I'll re-created the CRAN tarball and re-submit to Winbuilder in a sec here, 🤞 .
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2781109937
Ok, the open PRs are all done ^^^ are the 4 commits we need to cherry pick (I think that's all of them at least!). Do you still have time to do the patch release stuff @amoeba ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784281937
> After looking closer, I'm rethinking my above. It's possible the issue is that the patch in https://github.com/apache/arrow/commit/629e05fb75a07bbb4f9d5d04c3797f15b07291dd needs to be adapted to work on Windows.
Yeah I suspect that's true
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2790585942
Closing as complete. Binaries are still propagating on CRAN but everything else is wrapped up. I also forgot to thank @paleolimbot for the help on https://github.com/apache/arrow/pull/45951 which was greatly appreciated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2760054160
Commits to pull:
* https://github.com/apache/arrow/commit/629e05fb75a07bbb4f9d5d04c3797f15b07291dd
* the merge of #45958
* the merge of #45951
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784220089
After looking closer, I'm rethinking my above. It's possible the issue is that the patch in https://github.com/apache/arrow/commit/629e05fb75a07bbb4f9d5d04c3797f15b07291dd needs to be adapted to work on Windows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2783970973
I submitted to winbuilder and macbuilder ([release](https://mac.r-project.org/macbuilder/results/1744042317-56d15a437a886cca/), [devel](https://mac.r-project.org/macbuilder/results/1744042371-51d931c556b2b94d/)) and tested installation on Ubuntu from pre-build binaries. Waiting on winbuilder/macbuilder and then we should be good to go.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2787247376
Awesome. Thanks to you @jonkeane and @nealrichardson for addressing the CRAN issues in this release.
Post-release PRs up:
- https://github.com/apache/arrow/pull/46060
- https://github.com/apache/arrow-site/pull/638
Once those are merged I'll close this issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784013966
Hi @jonkeane, both macbuilders look good. If Winbuilder comes back clean, the final tarball is at https://files.brycemecum.com/arrow_19.0.1.1.tar.gz for you to submit to CRAN when you have a moment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784420250
Based on this comment and code,
https://github.com/apache/arrow/blob/8dd6625b754921368c5c812e588d6215eddb25a1/r/tools/nixlibs.R#L986-L993
I think we could just add a `@rm -rf ../windows` to `purify`. I'd like to test locally before pushing up to winbuilder but I don't seem to understand how/when that make target runs during build.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784080285
🙏 Thanks!
Winbuilder has a warning about symbols still: https://win-builder.r-project.org/rvH7wT4irAKs/00check.log
```
* checking compiled code ... WARNING
File 'arrow/libs/x64/arrow.dll':
Found '_ZSt4cerr', possibly from 'std::cerr' (C++)
Objects: '../windows/arrow-19.0.1/lib/x64-ucrt/libarrow.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libthrift.a',
'../windows/arrow-19.0.1/lib/x64/libarrow.a',
'../windows/arrow-19.0.1/lib/x64/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64/libthrift.a'
Found '_ZSt4cout', possibly from 'std::cout' (C++)
Objects: '../windows/arrow-19.0.1/lib/x64-ucrt/libarrow.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libparquet.a',
'../windows/arrow-19.0.1/lib/x64/libarrow.a',
'../windows/arrow-19.0.1/lib/x64/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64/libparquet.a'
Found '_assert', possibly from 'assert' (C)
Objects: '../windows/arrow-19.0.1/lib/x64/libnghttp2.a',
'../windows/arrow-19.0.1/lib/x64/libssh2.a'
Found '_exit', possibly from '_exit' (C)
Objects: '../windows/arrow-19.0.1/lib/i386/libbrotlienc.a',
'../windows/arrow-19.0.1/lib/i386/libbz2.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libcrypto.a',
'../windows/arrow-19.0.1/lib/x64/libcrypto.a'
Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
Objects: '../windows/arrow-19.0.1/lib/x64-ucrt/libarrow.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libarrow_acero.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libaws-c-common.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libaws-cpp-sdk-transfer.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libnghttp2.a',
'../windows/arrow-19.0.1/lib/x64/libarrow.a',
'../windows/arrow-19.0.1/lib/x64/libarrow_acero.a',
'../windows/arrow-19.0.1/lib/x64/libarrow_bundled_dependencies.a',
'../windows/arrow-19.0.1/lib/x64/libaws-c-common.a',
'../windows/arrow-19.0.1/lib/x64/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64/libaws-cpp-sdk-transfer.a',
'../windows/arrow-19.0.1/lib/x64/libnghttp2.a'
Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
Objects: '../windows/arrow-19.0.1/lib/x64-ucrt/libbrotlienc.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libbz2.a',
'../windows/arrow-19.0.1/lib/x64/libbrotlienc.a',
'../windows/arrow-19.0.1/lib/x64/libbz2.a'
Found 'rand', possibly from 'rand' (C)
Objects:
'../windows/arrow-19.0.1/lib/x64-ucrt/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64-ucrt/libthrift.a',
'../windows/arrow-19.0.1/lib/x64/libaws-cpp-sdk-core.a',
'../windows/arrow-19.0.1/lib/x64/libthrift.a'
Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784331151
We might need to do that, but also thinking this through: the windows builds _do_ download binaries, and it's possible the `.so`s are coming from there. So we might need to build those for this patch too? I don't know off the top of my head if https://github.com/apache/arrow/commit/629e05fb75a07bbb4f9d5d04c3797f15b07291dd definitely would also remove the `.so`s on windows or if that's *nix only
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784755938
Thanks for this! I've submitted it 🤞
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.2 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2756247809
I think we actually want this to be 19.0.1.1 so we can use the 19.0.1 libarrow binaries
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2756268021
Ah, right. Changed the title.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "jonkeane (via GitHub)" <gi...@apache.org>.
jonkeane commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2786341220
> thanks, package arrow_19.0.1.1.tar.gz is on its way to CRAN.
🎉
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784608881
With that last patch, Winbuilder looks fixed. @jonkeane latest tarball is at https://files.brycemecum.com/arrow_19.0.1.1.tar.gz for submission.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2781732814
Hey @jonkeane, Re:
> Do you still have time to do the patch release stuff
I do. I'll get started on that now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784134429
Ah, I guess that makes sense. I'm guessing we need to re-prepare the Windows build, I'll look into that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [R] CRAN packaging checklist for version 19.0.1.1 [arrow]
Posted by "assignUser (via GitHub)" <gi...@apache.org>.
assignUser commented on issue #45950:
URL: https://github.com/apache/arrow/issues/45950#issuecomment-2784547568
I have opened https://github.com/apache/arrow/issues/46050 for the symbol issue and https://github.com/apache/arrow/issues/46051 for the news backport.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org