• Bug#1101386: src:lme4: fails to migrate to testing for too long

    From Dirk Eddelbuettel@21:1/5 to Paul Gevers on Wed Mar 26 22:10:01 2025
    On 26 March 2025 at 21:37, Paul Gevers wrote:
    | Source: lme4
    | Version: 1.1-35.5-1
    | Severity: serious
    | Control: close -1 1.1-36-1
    | Tags: sid trixie
    | User: [email protected]
    | Usertags: out-of-sync

    Hm, it so happens that there was a new upstream version 1.1-37 released yesterday (that I packaged yesterday too) so we'll see how it fares.

    Dirk

    | 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 this bug report. The current output of the migration
    | software for this package is copied to the bottom of this report and
    | should list the reason why the package is blocked.
    |
    | 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.
    |
    | This bug submission immediately closes the bug with the version in
    | unstable, so if that version or a later version migrates, this bug will
    | no longer affect testing. This bug is also tagged 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.
    |
    | This bug report has been automatically generated and has only been sent
    | manually. If you have any comments with regards to the content or the
    | process, please reach out to me.
    |
    | Paul
    |
    | [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
    | [2] https://qa.debian.org/excuses.php?package=lme4
    |
    | Current text from [2]:
    | Migration status for lme4 (1.1-35.5-1 to 1.1-37-1): Waiting for test
    | results or another package, or too young (no action required now - check
    | later)
    | Issues preventing migration:
    | ∙ ∙ autopkgtest for r-cran-clubsandwich/0.5.11-1: amd64: Pass, arm64:
    | Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test
    | in progress, s390x: Pass
    | ∙ ∙ autopkgtest for r-cran-gamm4/0.2-6-2: amd64: Pass, arm64: Pass,
    | armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in
    | progress, s390x: Pass
    | ∙ ∙ Too young, only 1 of 5 days old
    | ∙ ∙ Build-Depends(-Arch): lme4 r-base (not considered)
    | ∙ ∙ Build-Depends(-Arch): lme4 r-cran-reformulas (not considered)
    | ∙ ∙ Depends: lme4 r-cran-reformulas (not considered)
    | Additional info:
    | ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lme4.html
    | ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻ ∙ ∙ | Waiting for reproducibility test results on arm64 - info ♻ ∙ ∙ Waiting | for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting for
    | reproducibility test results on i386 - info ♻
    | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature]

    --
    dirk.eddelbuettel.com | @eddelbuettel | [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)