Closing the bug since multcomp has now migrated. On 2019/08/19 21:33, Dirk Eddelbuettel wrote:
These problems still seem self-imposed to me. We (maybe randomly ?) appear to be checking (maybe out-of-sync ?) permutations that upstream (ie CRAN) does not see.
Well, not randomly, we check multcomp from unstable against its reverse-dependencies from testing.
If one of multcomp's reverse-dependencies from testing is not compatible with the new multcomp, but there is a new version in unstable that is, then it is likely that adding a Breaks to multcomp will hint to the package manager not to install them together, thus ensuring we don't try to test incompatible versions.