On 14 March 2019 at 11:03, Andreas Tille wrote: | Control: forwarded -1 Bjoern Bornkamp <bbn...@gmail.com> | | (@Bjoern: For the full issue please read | https://bugs.debian.org/924514 | which is probably more relevant for DoseFinding debugging | than the Debian specific things below. ) | | Hi, | | On Wed, Mar 13, 2019 at 03:58:14PM -0500, Dirk Eddelbuettel wrote: | > | > On 13 March 2019 at 21:39, Paul Gevers wrote: | > | Source: multcomp, r-cran-dosefinding | > | Control: found -1 multcomp/1.4-10-1 | > | Control: found -1 r-cran-dosefinding/0.9-16-2 | > | Severity: important | > | X-Debbugs-CC: debian...@lists.debian.org | > | User: debian...@lists.debian.org | > | Usertags: breaks needs-update | > | | > | Dear maintainers, | > | | > | With a recent upload of multcomp the autopkgtest of r-cran-dosefinding | > | fails in testing when that autopkgtest is run with the binary packages | > | of multcomp from unstable. It passes when run with only packages from | > | testing. In tabular form: | > | pass fail | > | multcomp from testing 1.4-10-1 | > | r-cran-dosefinding from testing 0.9-16-2 | > | versioned deps [0] from testing from unstable | > | all others from testing from testing | > | > 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. CRAN may not check Suggests. I argued for years we should not either. 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. Truly sorry, Dirk | @Paul: I think its not really relevant for Buster release since multcomp | will not migrate due to freeze so for the moment I will not do anthing | for the moment (may be after Buster release DoseFinding maintainers at | CRAN found a solution - otherwise we need to do something about this). | | > Also, DoseFinding only _Suggests:_ multcomp | > | > https://cloud.r-project.org/web/packages/DoseFinding/index.html | | That's correct. But due to the use in the autopkgtest and the test | script is provided in the doc directory as example for users dh-r | upgrades those Suggests to Recommends[1]. | | Kind regards | | Andreas. | | [1] https://salsa.debian.org/r-pkg-team/dh-r/blob/master/dh/R.pm#L192 | | | | | I copied some of the output at the bottom of this report. Unfortunately, | | there is no error reported, but successful runs have more output. | | | | Due to the nature of this issue, I filed this bug report against both | | packages. Can you please investigate the situation and reassign the bug | | to the right package? If needed, please change the bug's severity. | | | | More information about this bug and the reason for filing it can be found on | | https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation | | | | Paul | | | | [0] You can see what packages were added from the second line of the log | | file quoted below. The migration software adds source package from | | unstable to the list if they are needed to install packages from | | multcomp/1.4-10-1. I.e. due to versioned dependencies or breaks/conflicts. | | | | https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-dosefinding/2099783/log.gz | | | | autopkgtest [23:10:49]: test run-unit-test: [----------------------- | | testgFit.R passed | | testplanMod.R passed | | testsDesign.R passed | | testsFitting.R passed | | testsMCPMod.R passed | | autopkgtest [23:10:55]: test run-unit-test: -----------------------] | | | | [DELETED ATTACHMENT signature.asc, application/pgp-signature] | | | -- | http://fam-tille.de -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org