Public bug reported:
r-cran-diffobj 0.3.8-2 has been in stonking-proposed for 54 days and can't
migrate. Its armhf and s390x builds will never succeed:
Migration status for r-cran-diffobj (0.3.6-2 to 0.3.8-2): BLOCKED
missing build on armhf: r-cran-diffobj (from 0.3.6-2)
missing build on s390x: r-cran-diffobj (from 0.3.6-2)
arch:armhf not built yet, autopkgtest delayed there
arch:s390x not built yet, autopkgtest delayed there
Build status for 0.3.8-2:
amd64, amd64v3, arm64, ppc64el, riscv64: Successfully built
armhf: Dependency wait on r-pkg-team-core-architecture (since 2026-08-27)
https://launchpad.net/ubuntu/+source/r-cran-diffobj/0.3.8-2/+build/33497657
s390x: Dependency wait on r-pkg-team-core-architecture (since 2026-08-27)
https://launchpad.net/ubuntu/+source/r-cran-diffobj/0.3.8-2/+build/33497660
Root cause
----------
0.3.8-2 adds r-pkg-team-core-architecture to Build-Depends and to the binary
Depends. That package is built from dh-r (20260707), whose architectures are
"all amd64 arm64 loong64 ppc64el riscv64". This is an intentional Debian R team
decision to stop supporting armhf, s390x and i386, and it's already widespread:
258 packages in stonking depend on r-pkg-team-core-architecture. The dependency
wait will never resolve. r-base-core 4.6.1-5 is still published on armhf and
s390x, which is why the old diffobj binaries are still installable there.
Reverse dependencies on armhf/s390x (identical on both)
-------------------------------------------------------
Packages that depend on it directly (Depends, no alternatives):
r-cran-waldo 0.6.2-1 (arch: all)
r-cran-vdiffr 1.0.9-3 (arch-specific)
r-cran-unitizer 1.4.24-1 (arch: all)
Packages that only suggest or recommend it, and are unaffected:
r-cran-brms, r-cran-webmockr
Removing only r-cran-diffobj would make 11 packages uninstallable, counting
everything that depends on those three in turn:
r-cran-testthat 3.3.2-3 (arch-specific)
r-cran-vdiffr 1.0.9-3 (arch-specific)
r-cran-waldo, r-cran-unitizer, r-cran-devtools, r-cran-mockery,
r-cran-patrick, r-cran-httptest2, r-cran-cmdfun, r-cran-dbitest,
r-bioc-megadepth (all arch: all)
Build-dependency impact: on armhf and s390x, the only sources with binaries
that build-depend on anything in this group are r-cran-testthat and
r-cran-vdiffr themselves. No other builds break.
Caveat: R autopkgtests (pkg-r-autopkgtest) that pull in r-cran-testthat will
end in badpkg on armhf and s390x. Britney counts that as a regression until
the migration-reference baseline also fails, so expect some short-lived noise.
Request
-------
Please remove these binaries from stonking on armhf and s390x:
r-cran-diffobj 0.3.6-2
r-cran-vdiffr 1.0.9-3
r-cran-testthat 3.3.2-3
Removing only diffobj would leave testthat and vdiffr uninstallable rather
than gone. The arch:all packages need no action.
Example:
remove-package -s stonking -a armhf -a s390x -b \
-m "Debian R team no longer supports armhf/s390x
(r-pkg-team-core-architecture)" \
r-cran-diffobj r-cran-vdiffr r-cran-testthat
Possible wider cleanup: stonking still has 153 arch-specific r-* binaries on
each of armhf and s390x. More packages will hit this same blocker as they
adopt r-pkg-team-core-architecture, so removing them all in one pass may be
worth considering.
** Affects: r-cran-diffobj (Ubuntu)
Importance: Undecided
Assignee: Graham Inggs (ginggs)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169962
Title:
Please remove r-cran-diffobj, r-cran-vdiffr, r-cran-testthat on
armhf/s390x from stonking (r-pkg-team-core-architecture)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/r-cran-diffobj/+bug/2169962/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
