Re: [R-pkg-devel] Package required but not available: ‘arrow’
On 26 February 2024 at 09:19, Simon Urbanek wrote: | [requiring increased is] best way [..] and certainly the only good practice. No, not really. Another viewpoint, which is implemented in another project I contribute to, is where a version + build_revision tuple exists if, and only if, the underlying upload was accepted. Until then upload iterations are fine. Hence s/only good practive/one possible way/. Anyway: `arrow` is long back at CRAN (yay!) so this thread is done anyway. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
To quote Rob: "Version numbers are cheap" The way the policy is worded it is clear that you cannot complain if you didn't increase it as you are taking a risk. Also the the incoming FTP won't let you upload same version twice so it wasn't really a problem until more recently when there are multiple different ways to submit. Either way, changing the policy to MUST is probably the best way to avoid race conditions and certainly the only good practice. Cheers, Simon > On 25/02/2024, at 5:44 PM, Rolf Turner wrote: > > > On Fri, 23 Feb 2024 10:19:41 -0600 > Dirk Eddelbuettel wrote: > >> >> On 23 February 2024 at 15:53, Leo Mada wrote: >> | Dear Dirk & R-Members, >> | >> | It seems that the version number is not incremented: >> | # Archived >> | arrow_14.0.2.1.tar.gz 2024-02-08 11:57 3.9M >> | # Pending >> | arrow_14.0.2.1.tar.gz 2024-02-08 18:24 3.9M >> | >> | Maybe this is the reason why it got stuck in "pending". >> >> No it is not. >> >> The hint to increase version numbers on re-submission is a weaker >> 'should' or 'might', not a strong 'must'. >> >> I have uploaded a few packages to CRAN over the last two decades, and >> like others have made mistakes requiring iterations. I have not once >> increased a version number. > > That's as may be but IMHO (and AFAICS) it never hurts to increment the > version number, even if you've only corrected a trivial glitch. > > cheers, > > Rolf > > -- > Honorary Research Fellow > Department of Statistics > University of Auckland > Stats. Dep't. (secretaries) phone: > +64-9-373-7599 ext. 89622 > Home phone: +64-9-480-4619 > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
On Fri, 23 Feb 2024 10:19:41 -0600 Dirk Eddelbuettel wrote: > > On 23 February 2024 at 15:53, Leo Mada wrote: > | Dear Dirk & R-Members, > | > | It seems that the version number is not incremented: > | # Archived > | arrow_14.0.2.1.tar.gz 2024-02-08 11:57 3.9M > | # Pending > | arrow_14.0.2.1.tar.gz 2024-02-08 18:24 3.9M > | > | Maybe this is the reason why it got stuck in "pending". > > No it is not. > > The hint to increase version numbers on re-submission is a weaker > 'should' or 'might', not a strong 'must'. > > I have uploaded a few packages to CRAN over the last two decades, and > like others have made mistakes requiring iterations. I have not once > increased a version number. That's as may be but IMHO (and AFAICS) it never hurts to increment the version number, even if you've only corrected a trivial glitch. cheers, Rolf -- Honorary Research Fellow Department of Statistics University of Auckland Stats. Dep't. (secretaries) phone: +64-9-373-7599 ext. 89622 Home phone: +64-9-480-4619 __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
On 23 February 2024 at 15:53, Leo Mada wrote: | Dear Dirk & R-Members, | | It seems that the version number is not incremented: | # Archived | arrow_14.0.2.1.tar.gz 2024-02-08 11:57 3.9M | # Pending | arrow_14.0.2.1.tar.gz 2024-02-08 18:24 3.9M | | Maybe this is the reason why it got stuck in "pending". No it is not. The hint to increase version numbers on re-submission is a weaker 'should' or 'might', not a strong 'must'. I have uploaded a few packages to CRAN over the last two decades, and like others have made mistakes requiring iterations. I have not once increased a version number. If/when CRAN sees an error in its (automated, largely) processing, the package is moved and the space is cleared allowing a fresh upload. (Of course you cannot upload under the same filename twice _before_ the initial processing. By default uploads do not overwrite.) Arhive/ is distinct from pending. POSIX semantics on times also help: your example clearly shows that the one in archived is older by about 6 1/2 hours. That said, in case there are multiple rounds of email and discussion having distinct numbers may ease identification of the particular package and discussion thread. But it still makes sense to have this be a suggestion, not a requirement. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
Dear Dirk & R-Members, It seems that the version number is not incremented: # Archived arrow_14.0.2.1.tar.gz 2024-02-08 11:57 3.9M # Pending arrow_14.0.2.1.tar.gz 2024-02-08 18:24 3.9M Maybe this is the reason why it got stuck in "pending". Regarding such issues: maybe CRAN should warn if the version number of a new submission matches a previous one. Sincerely, Leonard [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available:‘arrow’
On 22 February 2024 at 04:01, Duncan Murdoch wrote: | For you to deal with this, you should make arrow into a suggested | package, For what it is worth, that is exactly what package tiledb does. Yet the Suggests: still lead to a NOTE requiring a human to override which did not happen until I gently nudged after the 'five work days' had lapsed. So full agreement that 'in theory' a Suggests: should help and is the weaker and simpler dependency. However 'in practice' it can still lead to being held up up when the weak-dependency package does not build. [ As for Dénes's point, most if not all the internals in package tiledb are actually on nanoarrow but we offer one code path returning an Arrow Table object and that requires 'arrow' the package for the instantiation. So it really all boils down to 'Lightweight is the right weight' as we say over at www.tinyverse.org. But given that the public API offers an Arrow accessor, it is a little late to pull back from it. And Arrow is a powerful and useful tool. Building it, however, can have its issues... ] Anyway, while poking around the issue when waiting, I was also told by Arrow developers that the issue (AFAICT a missing header) is fixed, and looking at CRAN's incoming reveals the package has been sitting there since Feb 8 (see https://cran.r-project.org/incoming/pending/). So would be good to hear from CRAN what if anything is happening here. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
FWIW the arrow maintainers are aware of this and we submitted a fix to CRAN a couple of weeks ago, which is currently in the review queue at https://cran.r-project.org/incoming/pending/ Nic On Thu, 22 Feb 2024 at 09:22, Park, Sung Jae wrote: > Thank you so much for all of you! I haven’t thought that ‘arrow’ package > itself will have an error. > Since ‘arrow’ package isn’t a crucial component of our package, I made > ‘arrow’ package into ‘Suggests’ and update cran-comment.md accordingly. > I appreciate your advice once again. > > Best, > --Sungjae > > From: Dénes Tóth > Date: Thursday, February 22, 2024 at 6:47 AM > To: Duncan Murdoch , Park, Sung Jae < > spa...@ufl.edu>, r-package-devel@r-project.org < > r-package-devel@r-project.org> > Subject: Re: [R-pkg-devel] Package required but not available: ‘arrow’ > [External Email] > > Depending on your use case you can also take a look at the nanoarrow > package ( > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3Dnanoarrow&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558568835%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=uJO%2BkxcEtEoDRg9ynyEYuOOCjO%2B30L05lwqIaPifijE%3D&reserved=0 > <https://cran.r-project.org/package=nanoarrow>). Maybe it > provides all the features you need and has a much smaller footprint than > 'arrow'. > > Best, > Denes > > > On 2/22/24 10:01, Duncan Murdoch wrote: > > If you look on the CRAN check results for arrow, you'll see it has > > errors on the Linux platforms that use clang, and can't be installed > there. > > > > For you to deal with this, you should make arrow into a suggested > > package, and if it is missing, work around that without generating an > > error. Another choice would be to work with the arrow developers to get > > it to install on the systems where it fails now, but it's a big package, > > so that would likely be a lot harder. > > > > Duncan Murdoch > > > > On 21/02/2024 5:15 p.m., Park, Sung Jae wrote: > >> Hi, > >> > >> I’m writing to seek assistance regarding an issue we’re encountering > >> during the submission process of our new package to CRAN. > >> The package in question is currently working smoothly on R CMD check > >> on Windows; however, we are facing a specific error when running R CMD > >> check on Debian. The error message we’ve got from CRAN is as follows: > >> > >> ``` > >> ❯ checking package dependencies ... ERROR > >>Package required but not available: ‘arrow’ > >> > >>See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ > >> manual. > >> ``` > >> > >> We have ensured that the ‘arrow’ package is properly listed in > >> DESCRIPTION file under the ‘Imports:’. > >> Could you please provide guidance on how to resolve this? Any help > >> will be valuable. > >> > >> Thank you in advance. > >> > >> Best, > >> --Sungjae > >> > >> > >> > >> [[alternative HTML version deleted]] > >> > >> __ > >> R-package-devel@r-project.org mailing list > >> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558577549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=osbKs4kHdz70V75aL3IcTsoc9hWi1m2G5x4Yp9SiiRE%3D&reserved=0 > <https://stat.ethz.ch/mailman/listinfo/r-package-devel> > > > > __ > > R-package-devel@r-project.org mailing list > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558583779%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=9%2FKDNWc62Z9PRFIKGZjkGB8pj16134RKu694qO%2Fg6vs%3D&reserved=0 > <https://stat.ethz.ch/mailman/listinfo/r-package-devel> > > > > [[alternative HTML version deleted]] > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
Thank you so much for all of you! I haven’t thought that ‘arrow’ package itself will have an error. Since ‘arrow’ package isn’t a crucial component of our package, I made ‘arrow’ package into ‘Suggests’ and update cran-comment.md accordingly. I appreciate your advice once again. Best, --Sungjae From: Dénes Tóth Date: Thursday, February 22, 2024 at 6:47 AM To: Duncan Murdoch , Park, Sung Jae , r-package-devel@r-project.org Subject: Re: [R-pkg-devel] Package required but not available: ‘arrow’ [External Email] Depending on your use case you can also take a look at the nanoarrow package (https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3Dnanoarrow&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558568835%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=uJO%2BkxcEtEoDRg9ynyEYuOOCjO%2B30L05lwqIaPifijE%3D&reserved=0<https://cran.r-project.org/package=nanoarrow>). Maybe it provides all the features you need and has a much smaller footprint than 'arrow'. Best, Denes On 2/22/24 10:01, Duncan Murdoch wrote: > If you look on the CRAN check results for arrow, you'll see it has > errors on the Linux platforms that use clang, and can't be installed there. > > For you to deal with this, you should make arrow into a suggested > package, and if it is missing, work around that without generating an > error. Another choice would be to work with the arrow developers to get > it to install on the systems where it fails now, but it's a big package, > so that would likely be a lot harder. > > Duncan Murdoch > > On 21/02/2024 5:15 p.m., Park, Sung Jae wrote: >> Hi, >> >> I’m writing to seek assistance regarding an issue we’re encountering >> during the submission process of our new package to CRAN. >> The package in question is currently working smoothly on R CMD check >> on Windows; however, we are facing a specific error when running R CMD >> check on Debian. The error message we’ve got from CRAN is as follows: >> >> ``` >> ❯ checking package dependencies ... ERROR >>Package required but not available: ‘arrow’ >> >>See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ >> manual. >> ``` >> >> We have ensured that the ‘arrow’ package is properly listed in >> DESCRIPTION file under the ‘Imports:’. >> Could you please provide guidance on how to resolve this? Any help >> will be valuable. >> >> Thank you in advance. >> >> Best, >> --Sungjae >> >> >> >> [[alternative HTML version deleted]] >> >> __ >> R-package-devel@r-project.org mailing list >> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558577549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=osbKs4kHdz70V75aL3IcTsoc9hWi1m2G5x4Yp9SiiRE%3D&reserved=0<https://stat.ethz.ch/mailman/listinfo/r-package-devel> > > __ > R-package-devel@r-project.org mailing list > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=05%7C02%7Cspark7%40ufl.edu%7C1e2fd4f4cb684488106208dc339c0e93%7C0d4da0f84a314d76ace60a62331e1b84%7C0%7C0%7C638441992558583779%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=9%2FKDNWc62Z9PRFIKGZjkGB8pj16134RKu694qO%2Fg6vs%3D&reserved=0<https://stat.ethz.ch/mailman/listinfo/r-package-devel> > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
Depending on your use case you can also take a look at the nanoarrow package (https://cran.r-project.org/package=nanoarrow). Maybe it provides all the features you need and has a much smaller footprint than 'arrow'. Best, Denes On 2/22/24 10:01, Duncan Murdoch wrote: If you look on the CRAN check results for arrow, you'll see it has errors on the Linux platforms that use clang, and can't be installed there. For you to deal with this, you should make arrow into a suggested package, and if it is missing, work around that without generating an error. Another choice would be to work with the arrow developers to get it to install on the systems where it fails now, but it's a big package, so that would likely be a lot harder. Duncan Murdoch On 21/02/2024 5:15 p.m., Park, Sung Jae wrote: Hi, I’m writing to seek assistance regarding an issue we’re encountering during the submission process of our new package to CRAN. The package in question is currently working smoothly on R CMD check on Windows; however, we are facing a specific error when running R CMD check on Debian. The error message we’ve got from CRAN is as follows: ``` ❯ checking package dependencies ... ERROR Package required but not available: ‘arrow’ See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ manual. ``` We have ensured that the ‘arrow’ package is properly listed in DESCRIPTION file under the ‘Imports:’. Could you please provide guidance on how to resolve this? Any help will be valuable. Thank you in advance. Best, --Sungjae [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
This error indicates that the arrow package is unavailable on the system where your package is checked. At https://cran.r-project.org/web/checks/check_results_arrow.html you can see that the arrow package is currently not working with clang on fedora an debian. This is not something that you can fix. All you can do is report this with the arrow maintainers if it is not already reported, and wait until this is fixed. HTH, Jan On 21-02-2024 23:15, Park, Sung Jae wrote: Hi, I’m writing to seek assistance regarding an issue we’re encountering during the submission process of our new package to CRAN. The package in question is currently working smoothly on R CMD check on Windows; however, we are facing a specific error when running R CMD check on Debian. The error message we’ve got from CRAN is as follows: ``` ❯ checking package dependencies ... ERROR Package required but not available: ‘arrow’ See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ manual. ``` We have ensured that the ‘arrow’ package is properly listed in DESCRIPTION file under the ‘Imports:’. Could you please provide guidance on how to resolve this? Any help will be valuable. Thank you in advance. Best, --Sungjae [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Package required but not available: ‘arrow’
If you look on the CRAN check results for arrow, you'll see it has errors on the Linux platforms that use clang, and can't be installed there. For you to deal with this, you should make arrow into a suggested package, and if it is missing, work around that without generating an error. Another choice would be to work with the arrow developers to get it to install on the systems where it fails now, but it's a big package, so that would likely be a lot harder. Duncan Murdoch On 21/02/2024 5:15 p.m., Park, Sung Jae wrote: Hi, I’m writing to seek assistance regarding an issue we’re encountering during the submission process of our new package to CRAN. The package in question is currently working smoothly on R CMD check on Windows; however, we are facing a specific error when running R CMD check on Debian. The error message we’ve got from CRAN is as follows: ``` ❯ checking package dependencies ... ERROR Package required but not available: ‘arrow’ See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ manual. ``` We have ensured that the ‘arrow’ package is properly listed in DESCRIPTION file under the ‘Imports:’. Could you please provide guidance on how to resolve this? Any help will be valuable. Thank you in advance. Best, --Sungjae [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Package required but not available: ‘arrow’
Hi, I’m writing to seek assistance regarding an issue we’re encountering during the submission process of our new package to CRAN. The package in question is currently working smoothly on R CMD check on Windows; however, we are facing a specific error when running R CMD check on Debian. The error message we’ve got from CRAN is as follows: ``` ❯ checking package dependencies ... ERROR Package required but not available: ‘arrow’ See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’ manual. ``` We have ensured that the ‘arrow’ package is properly listed in DESCRIPTION file under the ‘Imports:’. Could you please provide guidance on how to resolve this? Any help will be valuable. Thank you in advance. Best, --Sungjae [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel