On 22 July 2023 at 21:45, Paul Gevers wrote: | Source: lme4 | Version: 1.1-31-1 | Severity: serious | Control: close -1 1.1-34-1 | X-Debbugs-CC: [email protected] | Tags: sid trixie | User: [email protected] | Usertags: out-of-sync | | Dear maintainer(s), | | The Release Team considers packages that are out-of-sync between testing | and unstable for more than 30 days as having a Release Critical bug in | testing [1]. Your package src:lme4 has been trying to migrate for 32 | days [2]. Hence, I am filing this bug. | | The version in unstable causes 3 autopkgtest failures when tested in | testing, all on i386. The failures are due to autopkgtest timeout after | 2:47 h, while normally these tests run in minutes, so this suggests the | tests hang. In unstable, r-cran-afex and r-cran-mertools pass (so this | is probably a (set of) package(s) in unstable that also needs to migrate | together with lme4), but r-cran-mlmrev also times out in unstable. | | If a package is out of sync between unstable and testing for a longer | period, this usually means that bugs in the package in testing cannot be | fixed via unstable. Additionally, blocked packages can have impact on | other packages, which makes preparing for the release more difficult. | Finally, it often exposes issues with the package and/or | its (reverse-)dependencies. We expect maintainers to fix issues that | hamper the migration of their package in a timely manner. | | This bug will trigger auto-removal when appropriate. As with all new | bugs, there will be at least 30 days before the package is auto-removed. | | I have immediately closed this bug with the version in unstable, so if | that version or a later version migrates, this bug will no longer affect | testing. I have also tagged this bug to only affect sid and trixie, so | it doesn't affect (old-)stable. | | If you believe your package is unable to migrate to testing due to | issues beyond your control, don't hesitate to contact the Release Team.
The lme4 package is in fine standing at CRAN https://cloud.r-project.org/web/checks/check_results_lme4.html and build everywhere on Debian (see this and other links) https://cloud.r-project.org/web/checks/check_results_lme4.html If three other packages (that I have nothing to do with) fail in _their autopkgtests_ may I suggest you talk to the maintainers of _those packages_? lme4 is _core_ package, written and maintained by current and former R Core members. It is one of the most widely used and watched packages around. This is most likely an issue of shooting the messenger as the root cause with be with those other packages. It could be an issue as simple as CRAN (and upstream) no longer checking on i386 though it usually does not fail there. Dirk | Paul | | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html | [2] https://qa.debian.org/excuses.php?package=lme4 | x[DELETED ATTACHMENT OpenPGP_signature, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
