-
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
seqArchRplus #2790
Comments
Hi @snikumbh Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
Thanks for submitting this package. I rendered the vignette and I find that it is not sufficiently demonstrative of what the package does. There is
and so on. Please compile the vignette and look at it as something that a newcomer should be able to consume with interest and some aesthetic satisfaction. This would mean that you suppress certain messages in your methods, have good show methods for data structures of significance, and display some of the visualizations that you describe. Let us know your plans @vjcitn |
Thanks for the comment/suggestion. Will work on it and reply here. |
Hi @vjcitn |
Hi @vjcitn |
A reviewer has been assigned to your package. Learn what to expect IMPORTANT: Please read this documentation for setting Bioconductor utilized your github ssh-keys for git.bioconductor.org |
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. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Hi @lshep,
which going by info at What do you suggest in this regard? R CMD check has actually passed fine, and this error did not show up with BiocCheck when run locally. Thanks. |
Bioconductor will only use whatever version is available through CRAN. If it is not available via CRAN Bioconductor will not have access as we do not use remotes or download specific versions of packages. For what its worth I can reproduce this locally on my computer so I suggest making sure you are using the right version of R and all updated packages by check
|
Received a valid push on git.bioconductor.org; starting a build for commit id: 61caf154101acac04cc0f2b2692175ed2f6363e8 |
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. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Hi @lshep Could I please ask you to install the updated version of Brobdingnag 1.2-9 from CRAN on the builders? Thanks in advance. I just re-installed Brobdingnag and the error is no more there. I will then bump and push again to trigger a build. |
If it is a new version number on cran than it should update automatically. Can you bump the version and try again? |
Received a valid push on git.bioconductor.org; starting a build for commit id: ddee1b266e5c4e10503b48fb87e49a5c11203d0b |
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. This link will be active Remember: if you submitted your package after July 7th, 2020, |
OK, still the error. One way to check directly would be to |
I think you might need to declare Brobdingnag in your dependency list? I still get the same ERROR as before after installing the new version locally but when I am checking my sessionInfo I do not see Brobdingnag loaded
However I am doubtful that that would work too:
|
I was not sure about re-installing Matrix, so I tried to look for my command history. Here it is I re-installed all three (Matrix, Brobdingnag, and dbplyr), and the error went away. Interestingly, even dbplyr does not directly depend on Brobdingnag (it perhaps does indirectly via the tidyverse, but I may be wrong). |
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: "ABNORMAL". Please see the build report for more details. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Received a valid push on git.bioconductor.org; starting a build for commit id: a7807fbbaf13c75357bbe9f77813da4bb71acb4a |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Hi @lshep The package looks good to go. Thanks for your patience all along. Best, |
Hi @lshep Thanks. Appreciate all your help. |
Sorry for the delay - I'll try to get to a review before the end of hte week |
Please remove or populate the currently empty README.md I am unable to run the code in the vignette. When I work through the code that is shown to a rendered vignette I get the following ERROR in section 3.1.2
|
Received a valid push on git.bioconductor.org; starting a build for commit id: 0559ac65699b8f203da49b98782943f027e3f0a6 |
OK. This error in running line 312 is anticipated (and reproduced) if/when line number 226 is not run (previous chunk) which is not shown to the user. I have changed the vignette to include that part into the chunk that is visible to the user with a clear note in the comment. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Done. I have made the necessary changes (moved that code to the visible chunk). Removed the empty README.md as well. |
Hi @lshep |
Yes I will try to review shortly sorry for the delay. |
Minor comment: R ships with the GPL-3 license so there is no need to include it as a seperate file. Please update the package DESCRIPTION to just |
Noted, thanks. Best, |
Sorry I was short yesterday. I think the rest of the package looks good and would be willing to accept with the licensing change. |
OK, great. On it then! Thanks. |
Received a valid push on git.bioconductor.org; starting a build for commit id: 06af1a14d08005e486e0d032785648b3e00a9864 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. This link will be active Remember: if you submitted your package after July 7th, 2020, |
Hi @lshep, all done! Thanks. |
Ping :) |
Hi @lshep Best wishes, |
Your package has been accepted. It will be added to the Thank you for contributing to Bioconductor! Reviewers for Bioconductor packages are volunteers from the 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/snikumbh.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/seqArchRplus 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 Bioconductor Package Naming Policy and acknowledge
Bioconductor may retain use of package name.
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 Bioconductor code of conduct and
agree to abide by it.
I am familiar with the essential aspects of Bioconductor software
management, including:
months, for bug fixes.
(optionally via GitHub).
For questions/help about the submission process, including questions about
the output of the automatic reports generated by the SPB (Single Package
Builder), please use the #package-submission channel of our Community Slack.
Follow the link on the home page of the Bioconductor website to sign up.
The text was updated successfully, but these errors were encountered: