-
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
bugphyzz #3367
Comments
Hi @sdgamboa Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
We don't allow data to be store in github. Please store data on zenodo or some other trusted server. If a trusted serve is not available please consider using ExperimentHub. |
@lshep, we have published our data on zenodo and use it as the default option in our main function. A couple of functions still use data from external sites. One of them is not exported. The other is exported, but we wrote in the documentation that it should be used by curator/developers. These functions are not used in any other function meant for end users. Finally, a dataset that was originally imported from a github repo is now included in the Please let me know if I need to make more changes. Thank you! |
Please also include a section in the vignette that is similar to an abstract describing why you are submitting the package to bioconductor and a comparison to an existing Bioconductor packages. |
We have added the package to git.bioconductor.org but I am having trouble kicking off an initial build of the package. I'm currently investigating. |
For Now this should be true: Your package has been added to git.bioconductor.org to continue the 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 the Bioconductor Single Package Builder. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Figured out the issue. If you have difficulty triggering builds with pushes to git.bioconductor.org let me know and I can try to reprocess the package but I think it should be okay. |
Received a valid push on git.bioconductor.org; starting a build for commit id: 475801d3e42da79725446199ae4e90061ff70ffe |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
@lshep, I added an abstract to the vignette and expanded the introduction to describe the package in more detail. I explain how the package should fit within Bioconductor workflows and related packages. Please let me know if that fulfills the request. I got an error in the build, but I think this is a problem with one of the dependencies of another package (mia):
|
Received a valid push on git.bioconductor.org; starting a build for commit id: 604ff536de53970333f79ff29006bc4af4dddf80 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. Congratulations! The package built without errors or warnings Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
A reviewer has been assigned to your package for an indepth review. |
Received a valid push on git.bioconductor.org; starting a build for commit id: 496e8d6e661db1e90f4574c81fb1749afa964085 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. Congratulations! The package built without errors or warnings Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
@sdgamboa may we expected updates soon? |
@lshep, yes. Thanks for following up. I've already made the required changes. I'll bump the version today. |
Received a valid push on git.bioconductor.org; starting a build for commit id: 96dae082e576c0690e52df7ba0be965f4c15afae |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Received a valid push on git.bioconductor.org; starting a build for commit id: 74ffe67004db23383bcbcb24392ee30adb70f296 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Received a valid push on git.bioconductor.org; starting a build for commit id: 9dc230555d8581b5a4a198f81ff7d92d9c0c2ca5 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
@lshep, I think there could be some issues with the connection on nebbiolo2 (Ubuntu). I keep getting an error when building the vignette or running the tests of the package. The error seems to be related to the function that downloads the data. This doesn't happen on my local machine (I deleted the cache). It doesn't happen on GitHub either. |
Received a valid push on git.bioconductor.org; starting a build for commit id: 12b69a764fde049a09e0f7a5f8588fb5e64baa7a |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. Congratulations! The package built without errors or warnings Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Dear @DarioS, Thank you for your feedback. I think I've addressed all of the requested changes below:
I homogenized all function names, variables, and arguments to camelCase. Please see
I changed all
Added
The makeSignatures function can now handle
I was not able to reproduce this issue. I'm able to open the vignettes in my browser (Linux machine) with either
The input for Please let me know if other changes are required. Thanks. |
The issues raised have been addressed. |
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 default branch of your GitHub repository has been added to Bioconductor's 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/sdgamboa.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/bugphyzz 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: