Your message dated Thu, 9 Nov 2023 19:57:20 +0100
with message-id <[email protected]>
and subject line Re: Bug#1041738: src:lme4: fails to migrate to testing for too
long: causes timeout in autopkgtests on i386
has caused the Debian Bug report #1043130,
regarding r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1043130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043130
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=lme4
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
On Sun, 6 Aug 2023 10:44:35 +0000 Graham Inggs <[email protected]> wrote:
> Yet r-cran-mlmrev[3] still seems to have the timeout issue in unstable.
The timeout of r-cran-mlmrev's autopkgtests on i386 is the last
blocker for lme4, so I will allow lme4 to migrate and (attempt) to
clone this bug to r-cran-mlmrev.
This issue seems to have solved itself somewhere in September or early
October.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
