Hi Dirk, On Fri, Mar 15, 2019 at 05:50:38AM -0500, Dirk Eddelbuettel wrote: > | > 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.
I'm sorry, but I fail to understand. What we are doing is to run the test suite shipped by upstream of DoseFinding. Am I understand you correctly that we should not run the test provided by upstream in our packages? From my point of view specifically the fact that we've found some incompatibility between package A (r-cran-dosefinding) and one of the packages its needs to run its test suite B (r-cran-multcimp) is a good reason that we are doing this. IMHO it means that there is some reason for action. This might be either fixing the code of package A or B or simply fixing the test suite of package B. My perception of Debian maintainership is to uncover this kind of issues. Kind regards Andreas. PS: I remember you once was offended since I moved a discussion about some topic about a specific issue that turned to become generic about packaging from Debian R list to debian-devel. I never understood why you were offended about this but since I see some generic problem that becomes abstracted here as well it might turn out that I do so in some future reply of mine. -- http://fam-tille.de