Re: Bug#1120975: Please let r-base migrate by removing blocking packages
On Wed, Nov 19, 2025 at 01:14:09PM -0100, Graham Inggs wrote:
> Hi Dirk
>
> On Wed, 19 Nov 2025 at 11:01, Dirk Eddelbuettel <edd@debian.org> wrote:
> > | Looking at the excuses page you linked to above, only r-cran-bit64,
> > | r-cran-freetypeharfbuzz and r-cran-grimport are blocking the migration
> > | of r-base, the remainder have "failure will be ignored".
> >
> > Out of curiousity, and as I of course saw that too on the excuses page, which
> > 'state variable' governs this, and how can one set / unset it?
>
> In general, it is the state of a package's autopkgtests in the testing
> suite that governs this.
> e.g. r-cran-bayestestr is red [1] and r-cran-bit64 is green [2] (as of
> 2025-11-08 09:13:11 UTC)
>
> One way to reset the state is to trigger the autopkgtests with the
> fake 'migration-reference/0' package. If the autopkgtest is already
> failing in testing and the 'migration-reference/0' result turns red,
> then migration will no longer be blocked.
The easiest way to do the latter:
https://tracker.debian.org/pkg/r-base
∙ ∙ Autopkgtest for r-cran-bit64/4.6.0-1-4: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
Clicking on the recycle symbol ♻ after "reference" goes to a page with
a Retry button for the migration reference test.
> Regards
> Graham
>...
cu
Adrian
Reply to: