[R-pkg-team] Bug#960962: src:r-cran-roxygen2: fails to migrate to testing for too long: not installable on armel
elbrus at debian.org
Mon May 18 20:43:05 BST 2020
Control: close -1 7.1.0-2
Tags: sid bullseye
User: release.debian.org at packages.debian.org
As recently announced , the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:r-cran-roxygen2 in its current version in unstable has been trying
to migrate for 60 days . Hence, I am filing this bug.
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 bullseye, 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.
Your package gained a new dependency (r-cran-knitr) which isn't
installable on armel due to node lacking there.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the R-pkg-team