-
Notifications
You must be signed in to change notification settings - Fork 33
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
sparseMatrixStats #1465
Comments
Hi @const-ae Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
A reviewer has been assigned to your package. Learn what to expect IMPORTANT: Please read the instructions for setting |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. |
Shouldn't this (and MatrixGenerics) go into CRAN? |
I don't necessarily disagree ;) I guess the case for sparseMatrixStats being on BioConductor is that MatrixGenerics was submitted here and it makes sense to have them together. More generally, a lot of functionality around S4 is here on BioConductor (like S4Vectors), so it felt appropriate for me to submit both packages here as well. @PeteHaitch and @hpages, what would you say about this? |
I also don't necessarily disagree :) |
Thanks for introducing me to the term "bike-shedding" and the law of triviality. |
@lawremi I didn't mean that to dismiss your suggestion or concerns, which are well-placed. This really reflects my frustrations with myself for not being able to nail down the implementation |
@hpages has advocated for (initial) submission to Bioconductor, where it is much easier to mature packages, pointing to rhdf5 as an example |
I'll do some behinds the scenes stuff too to have this be able to build without waiting for MartrixGenerics to be accepted and without submitting under the other issue. hand tight and I'll kick off a new build when I have it set up so I can move forward with the review |
I recognize that Bioconductor wins in terms of developer convenience, but our community should be more proactive about sharing our general solutions and distributing through CRAN. Otherwise, only we will benefit. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. |
It is our understanding that R doesn't support C++14 on Windows yet. Please update to C++11 |
Hi Lori,
Oh, that is unfortunate. I thought that R 4.0 also meant Rtools 40 and thus finally a modern compiler on windows. |
It seems like its still being decided; see https://stat.ethz.ch/pipermail/r-devel/2020-April/079253.html |
We are ready to go with the Rtools40 whenever CRAN decides to switch over but as far as we are aware it is still being discussed. @hpages Do you know if this is truly the case when we switch to the new toolchain? |
Yep, we should be ready to switch (we have set up builds with the new toolchain for a small subset of packages). As for whether or not R core is going to switch in time for the R 4.0.0 release, I don't know more about this than what's being currently discussed on the R-devel mailing list. The thing is that we can't switch before they switch, which means that for now the SPB still has to use the old toolchain. So no C++14 features yet. So here you go: all the cards are on the table and I let you guys decide the strategy for getting sparseMatrixStats into Bioconductor in time for the release. |
We can wait to see when/if R 4.0.0 gives the official word that they will use the new toolchain. Until then it is up to you if you decide to modify the code to work in the meantime or temporarily mark as unsupported on windows until the switch happens. The package is generally well written and I only have the few minor comments: General
README
vignette
I won't be able to accept this package until MatrixGenerics gets accepted first. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: cbf1b0a Bump version |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. |
I have adapted the C++ code in a way that the C++14 features are not used anymore and it should now build on Windows with Rtools 35. I have also added the Bioconductor installation instructions to the README and made sure the
I have deleted the LICENSE.md file as it was not necessary. The two README files, I would say, are necessary, because the .Rmd file generates the .md file that is then displayed on GitHub. However, the
I don't remember that is was an issue before. Is it related to the fact that |
Ah I see the NEWS error was already fixed with Bioconductor/BiocCheck@27ea5e2. |
The NEWS file ERROR is on our end. We have a fix implemented in linux and there will be a fix on windows by later this afternoon. I will kick off a manual build so there is at least an accurate linux build. it should post shortly. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Great as soon as MatrixGenerics is accepted I will accept this package. Cheers |
@const-ae I know you already changed the code, but it looks like the migration to rtools40 is happening: https://twitter.com/opencpu/status/1250452381403398149 and https://community-bioc.slack.com/archives/CEQ04GKEC/p1586999356141000 |
Hi, thanks for the links :) @lori, the MatrixGenerics package has been accepted tonight (#1448 (comment)) :) |
Yes we updated the R and tool chain on windows last night. Up to you if you want to revert code. accepting the package regardless. |
Your package has been accepted. It will be added to the Thank you for contributing to Bioconductor! |
The master branch of your GitHub repository has been added to Bioconductor's git repository. To use the git.bioconductor.org repository, we need an 'ssh' key to associate with your github user name. If your GitHub account already has ssh public keys (https://github.com/const-ae.keys is not empty), then no further steps are required. Otherwise, do the following: See further instructions at https://bioconductor.org/developers/how-to/git/ for working with this repository. See especially https://bioconductor.org/developers/how-to/git/new-package-workflow/ to keep your GitHub and Bioconductor repositories in sync. Your package will be included in the next nigthly 'devel' build (check-out from git at about 6 pm Eastern; build completion around 2pm Eastern the next day) at https://bioconductor.org/checkResults/ (Builds sometimes fail, so ensure that the date stamps on the main landing page are consistent with the addition of your package). Once the package builds successfully, you package will be available for download in the 'Devel' version of Bioconductor using https://bioconductor.org/packages/sparseMatrixStats If you have any questions, please contact the bioc-devel mailing list (https://stat.ethz.ch/mailman/listinfo/bioc-devel); this issue will not be monitored further. |
Update the following URL to point to the GitHub repository of
the package you wish to submit to Bioconductor
Confirm the following by editing each check box to '[x]'
I understand that by submitting my package to Bioconductor,
the package source and all review commentary are visible to the
general public.
I have read the Bioconductor Package Submission
instructions. My package is consistent with the Bioconductor
Package Guidelines.
I understand that a minimum requirement for package acceptance
is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS.
Passing these checks does not result in automatic acceptance. The
package will then undergo a formal review and recommendations for
acceptance regarding other Bioconductor standards will be addressed.
My package addresses statistical or bioinformatic issues related
to the analysis and comprehension of high throughput genomic data.
I am committed to the long-term maintenance of my package. This
includes monitoring the support site for issues that users may
have, subscribing to the bioc-devel mailing list to stay aware
of developments in the Bioconductor community, responding promptly
to requests for updates from the Core team in response to changes in
R or underlying software.
I am familiar with the essential aspects of Bioconductor software
management, including:
months, for bug fixes.
(optionally via GitHub).
For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.
The text was updated successfully, but these errors were encountered: