we would like to submit an R package to bioc available at
A corresponding manuscript is available from
Unfortunately, we recently didn't check for conflicting package names on CRAN and meanwhile a package with a similar name was accepted:
p@fgcz-148:~/__checkouts/R > R CMD build rawR && R CMD check rawR_0.1.5.tar.gz --as-cran * checking for file 'rawR/DESCRIPTION' ... OK * preparing 'rawR': * checking DESCRIPTION meta-information ... OK * cleaning src * checking for LF line-endings in source and make files and shell scripts * checking for empty or unneeded directories Removed empty directory 'rawR/src' * building 'rawR_0.1.5.tar.gz' * using log directory '/home/cp/__checkouts/R/rawR.Rcheck' * using R version 4.0.3 (2020-10-10) * using platform: x86_64-pc-linux-gnu (64-bit) * using session charset: UTF-8 * using option '--as-cran' * checking for file 'rawR/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'rawR' version '0.1.5' * package encoding: UTF-8 * checking CRAN incoming feasibility ... ERROR Maintainer: 'Christian Panse <email@example.com>' New submission Conflicting package names (submitted: rawR, existing: rawr [https://CRAN.R-project.org]) Conflicting package names (submitted: rawR, existing: rawr [CRAN archive]) ...
Since the manuscript & GitHub repo. is already online and made it into blogs and social media, we of cause would like to prevent having to rename our package for bioc submission. Is this possible somehow? We also expected that checks would happen in a case sensitive manner.
"rawR" != "rawr"
“Package:” field: This is the name of the package. This should match the github repository name and is case sensitive. A package name should be descriptive and not already exist as a current package (case-insensitive) in Bioconductor or CRAN. Avoid names that are easily confused with existing package names, or that imply a temporal (e.g., ExistingPackage2) or qualitative (e.g., ExistingPackagePlus) relationship."
Thanks for your help, Tobi