Closed FelixErnst closed 4 years ago
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 on all platforms.
Please see the build report for more details.
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 on all platforms.
Please see the build report for more details.
@LiNk-NY everthing is ready for review. Please disregard the WARNINGS
, since the label is somewhat stuck probably due to the number of packages in this issue. All packages have cleared the build without ERROR
or WARNINGS
.
Hi Felix, @FelixErnst Apologies for the delay. It took me some time to go over the number of files in the packages. On the other hand, the review is pretty short due to the organization of the packages.
Please see below. Thank you for your submission. Best, Marcel
assertive
)Minor:
library
calls only in one
chunk. For example, you can set
results="hide",include=TRUE,message=FALSE,warning=FALSE
to show the chunk but not the results or messages etc.GenomicFeatures
can change at any time and you will have to
support any changes to them.dbplyr
).Hi Marcel, @LiNk-NY
thanks for the review and the comments.
I removed the non eval chunk from the vignette. I didn't know that chunk option setup since I never had a close look at how startup messages relate to normal messages. Thanks for the hint.
Regarding the use of dbplyr
: I didn't want to add a layer on the AnnotationDbi
interface and follow more closely what was done for the TxDb
class.
I will push the changes next week.
Felix
Hi Marcel, @LiNk-NY
thank you for the review and the suggestions.
I removed the single call to assertive and combined the first two chunks in the vignette. Thanks again for the hint with the chunk settings.
Regarding the use of dbplyr
: I looked into it, but opted to take the challange to implement the two version of SQL generators. It was a helpful exercise to take suggestions from the TxDb
class and rework and optimize space requirements, table relations and SQL statement generator to achieve the functionality for this use case. Certainly lifted some cobwebs from my SQL skills.
I will push the changes shortly.
Felix
Received a valid push; starting a build. Commits are:
215f363 included changes from Bioconductor review
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 on all platforms.
Please see the build report for more details.
Hi Marcel, @LiNk-NY
any news on the changes?
Cheers Felix
Hi Felix, @FelixErnst
I've reviewed your changes and comments.
Thank you for your quick response. I will accept the package.
Don't forget to include an Installation
section in the vignette.
Best,
Marcel
Your package has been accepted. It will be added to the Bioconductor Git repository and nightly builds. Additional information will be posed to this issue in the next several days.
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/FelixErnst.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/ https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
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 BiocManager::install("EpiTxDb")
. The package 'landing page' will be created at
https://bioconductor.org/packages/EpiTxDb
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.
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/FelixErnst.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/ https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
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 BiocManager::install("EpiTxDb.Hs.hg38")
. The package 'landing page' will be created at
https://bioconductor.org/packages/EpiTxDb.Hs.hg38
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.
@mtmorgan Thanks for adding the packages to Bioconductor's git repo. Could you also add EpiTxDb.Sc.sacCer3
and EpiTxDb.Mm.mm10
? Thank you
@mtmorgan not sure where EpiTxDb.Hs.hg38 got added but these three packages are annotation packages so @Kayla-Morrell will probably have to do some magic.
Re-opening for additional processing
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/FelixErnst.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/ https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
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 BiocManager::install("EpiTxDb.Sc.sacCer3")
. The package 'landing page' will be created at
https://bioconductor.org/packages/EpiTxDb.Sc.sacCer3
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.
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/FelixErnst.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/ https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
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 BiocManager::install("EpiTxDb.Mm.mm10")
. The package 'landing page' will be created at
https://bioconductor.org/packages/EpiTxDb.Mm.mm10
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]'
[x] I understand that by submitting my package to Bioconductor, the package source and all review commentary are visible to the general public.
[x] I have read the Bioconductor Package Submission instructions. My package is consistent with the Bioconductor Package Guidelines.
[x] 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.
[x] My package addresses statistical or bioinformatic issues related to the analysis and comprehension of high throughput genomic data.
[x] 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:
For help with submitting your package, please subscribe and post questions to the bioc-devel mailing list.