Closed LiNk-NY closed 4 months ago
@LiNk-NY - Sorry for the delay. The review of the packages are below. The required changes must be made while the suggested changes do not have to be (though we strongly encourage them). Comment back here with updates that have been made and when the packages are ready for a re-review.
Thank you Kayla @Kayla-Morrell for your review. I have updated the packages. Please see below.
AnVILBase
- [x] REQUIRED: The
R CMD check
did not finish because of the other AnVIL packages suggests. Any issues should be corrected once this is resolved and can complete.
Both AnVILAz
and AnVILGCP
packages should be installed first. I am not sure why there is an error in the SPB since both packages should be installed before AnVILBase
gets run. Any insights Lori? @lshep
https://bioconductor.org/spb_reports/AnVILBase_buildreport_20240603105555.html
- [x] SUGGESTION: No Bioconductor dependencies detected.
AnVILBase is an infrastructure package and does not use Bioconductor dependencies. The downstream packages AnVIL
, AnVILAz
, and AnVILGCP
do.
AnVILAz
- [x] SUGGESTION: All declared Imports should be used.
- [x] SUGGESTION: Import utils in NAMESPACE as well as DESCRIPTION.
- [x] SUGGESTION: Empty or missing \value sections found in man pages.
I don't see this when running BiocCheck
AnVILGCP
- [x] SUGGESTION: Provide 'URL', 'BugReports' field(s) in DESCRIPTION
- [x] SUGGESTION: Import parallel in DESCRIPTION as well as NAMESPACE
- [x] REQUIRED: 'sessionInfo' not found in vignette(s).
- [x] SUGGESTION: Avoid using '=' for assignment and use '<-' instead.
- [x] SUGGESTION: Avoid the use of 'paste' in condition signals.
- [x] SUGGESTION: Avoid redundant 'stop' and 'warn*' in signal conditions.
Some are false positives, e.g., "first error" in the error message, "function returned an error" in the converted warning
- [x] REQUIRED: There should be runnable examples in man pages that document exported objects.
- [x] REQUIRED: Use 'donttest{}' instead of 'dontrun{}' where possible.
- [x] SUGGESTION: Consider adding a NEWS file.
@LiNk-NY - Thank you for making the necessary changes. I would like to see a clean build report of AnVILBase before I accept the packages. If that issue can get resolved than I'd be more than happy to accept.
Best, Kayla
Received a valid push on git.bioconductor.org; starting a build for commit id: c8c58cdd186e92f43882dc40954d3c7f057514b2
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". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: macOS 12.7.1 Monterey: AnVILBase_0.99.25.tar.gz Linux (Ubuntu 22.04.3 LTS): AnVILBase_0.99.25.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/AnVILBase
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Received a valid push on git.bioconductor.org; starting a build for commit id: a4b1a38ee694b0512e2c7a86502012d3b1bd476d
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 on all platforms.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: macOS 12.7.1 Monterey: AnVILAz_0.99.9.tar.gz Linux (Ubuntu 22.04.3 LTS): AnVILAz_0.99.9.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/AnVILAz
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Received a valid push on git.bioconductor.org; starting a build for commit id: 03d3a30483b6e4aae76e67b59b28f2dea0319602
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". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: ERROR before build products produced.
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/AnVILGCP
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Received a valid push on git.bioconductor.org; starting a build for commit id: 8127648d1c251da73084fcb1d65e99f6fdbaeb16
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: "WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 22.04.3 LTS): AnVILGCP_0.99.27.tar.gz macOS 12.7.1 Monterey: AnVILGCP_0.99.27.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/AnVILGCP
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Hi Kayla, @Kayla-Morrell Thanks for taking a look.
All the packages are passing build and check now.
There is a false positive from the SPB but it only affects one platform:
* checking package dependencies ... ERROR
Packages suggested but not available: 'AnVILAz', 'AnVILGCP'
Best regards, Marcel
@LiNk-NY - Looks good, thanks!
Best, Kayla
Your package has been accepted. It will be added to the Bioconductor nightly builds.
Thank you for contributing to Bioconductor!
Reviewers for Bioconductor packages are volunteers from the Bioconductor community. If you are interested in becoming a Bioconductor package reviewer, please see Reviewers Expectations.
cannot build unless issue is open and has the 'pre-review' label or '2. review in progress' label, or is closed and has the 'TESTING' label.
cannot build unless issue is open and has the 'pre-review' label or '2. review in progress' label, or is closed and has the 'TESTING' label.
The default branch of your GitHub repository has been added to Bioconductor's git repository as branch devel.
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/LiNk-NY.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("AnVILBase")
. The package 'landing page' will be created at
https://bioconductor.org/packages/AnVILBase
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 default branch of your GitHub repository has been added to Bioconductor's git repository as branch devel.
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/LiNk-NY.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("AnVILAz")
. The package 'landing page' will be created at
https://bioconductor.org/packages/AnVILAz
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 default branch of your GitHub repository has been added to Bioconductor's git repository as branch devel.
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/LiNk-NY.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("AnVILGCP")
. The package 'landing page' will be created at
https://bioconductor.org/packages/AnVILGCP
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 Bioconductor Package Naming Policy and acknowledge Bioconductor may retain use of package name.
[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.
[x] 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:
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.