Closed kakopo closed 1 year ago
Hi Kirabo, Thanks for reporting. This was fixed here: https://github.com/Bioconductor/BiocCheck/pull/182/ Best, Marcel
@kakopo Looks like the reason we didn't get the fix is because for some reason the available version of BiocCheck (1.35.9) is lagging several versions behind the version on GitHub (1.35.12). See landing page https://bioconductor.org/packages/3.17/BiocCheck for currently available version. However, this will change today (maybe in the next 20 min or so) because, as indicated by the green LEDs on the build report here https://bioconductor.org/checkResults/3.17/bioc-LATEST/BiocCheck/, version 1.35.12 is about to propagate to the public repos.
Remember to provide your sessionInfo()
when you report a bug so we know what package versions you used. Thanks!
Thanks Hervé,
FWIW the BiocCheck version is also included in the output (see line 2)
> BiocCheck::BiocCheck("BSgenomeForge")
─ BiocCheckVersion: 1.35.9
But sessionInfo()
would be more comprehensive.
I am running
BiocCheck
on theBSgenomeForge
package which has the following output:The information in the
00BiocCheck.log
regarding the issue is more detailed, as shown below;Only 2 functions in the package are greater than 50 lines, and the package itself contains 30 functions exactly.