On 15 March 2019 at 07:49, Andreas Tille wrote: | On Thu, Mar 14, 2019 at 06:27:35AM -0500, Dirk Eddelbuettel wrote: | > | > | > No issue at CRAN for multcomp: | > | > | > | > https://cloud.r-project.org/web/checks/check_results_multcomp.html | > | > | > | > So this is likely self-inflicted at Debian. | > | | > | @Dirk: Could you please be more verbose in how far that link is a sign | > | that DoseFinding 0.9-16 works with multcomp 1.4-10. | > | > It is a table of checks across architectures and R version. None shows an issue. | > | > CRAN run reverse-depends on all package updates prior to admitting to CRAN. | > | > multcomp being on CRAN means there was no issue with its reverse depends. | | Thanks for the clarification. | | > CRAN may not check Suggests. I argued for years we should not either. | | I do not follow discussions on CRAN but I'd consider warnings about | issues with Suggests a nice feature. | | > If it breaks in Suggests, you "get to keep the pieces". I do not have the | > time to investigate what I consider to be a non-problems. Happy to help, but | > this is self-inflicted. | | In how far it is self-inflicted if some R package does not pass its test | suite?
It has no issues at CRAN as I stated. The package is fine. If our process shows up errors I consider it self-inflicted. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org