Bug#1076843: transition: r-bioc-biocgenerics (r-api-bioc-3.19)
Hi Michael
After the first migrations, a second wave of about 70 migrations
happened after autopkgtests were retried. These can already be seen
on the tracker.
On Mon, 9 Sept 2024 at 09:44, Michael R. Crusoe <[email protected]> wrote:
> We have a question about https://qa.debian.org/excuses.php?package=r-bioc-tcgabiolinks ; the CI for this package has never passed on ppc64el, so we are confused as to why this is now holding up migration.
>
> Likewise for https://qa.debian.org/excuses.php?package=r-bioc-rhdf5 ; the s390x CI has never passed here either.
When autopkgtest infrastructure for new architectures are added,
existing failures in testing are not considered regressions by
britney.
However, if a package is removed from testing, the failures are
considered new, as with any other package attempting to migrate to
testing for the first time.
r-bioc-rhdf5 [1] was auto-removed from testing on 2024-06-25.
r-bioc-tcgabiolinks [2] was manually removed from testing on
2023-07-14, a new upload was done on 2023-07-28 for the previous
r-bioc transition, but was not able to migrate for more than a year.
Regards
Graham
[1] https://tracker.debian.org/pkg/r-bioc-rhdf5
[2] https://tracker.debian.org/pkg/r-bioc-tcgabiolinks
Reply to: