Thanks. I've filed Debian Bug #898329 against the release team.
On Tue, 2018-05-08 at 12:50 +0800, Shengjing Zhu wrote:
> Source: bpfcc
> Severity: normal
>
> Dear Maintainer,
>
> bpfcc didn't migrate to testing. I see you have tried to request RoM
> but still not migrated. After consulting on #debian-dev
>
> 12:18 I think it is because arch-all packages
> are depending on packages that only exist on some arches https://qa.d
> ebian.org/excuses.php?package=bpfcc
> 12:19 IIRC the release team requires those deps
> to be satisfiable on i386, so I think bpfcc will need hinting into
> testing
> 12:19 I got this in an i386 chroot: python3-
> bpfcc : Depends: libbpfcc (>= 0.5.0-5) but it is not installable
> 12:19oddly, https://qa.debian.org/excuses.php?pa
> ckage=bpfcc says "Migration status: OK: Will attempt migration (Any
> information below is purely informational)" -- "Valid candidate"
> 12:20so not everything is playing by the same
> rules if it still isn't :)
> 12:20 yeah, testing migration is sometimes
> confusing. the log link usually explains things
> 12:21 Maybe that's it
> 12:21 https://release.debian.org/doc/britney/sho
> rt-intro-to-migrations.html#migration-phase-2-installability-
> regression-testing
> 12:22 I'd suggest reportbug release.debian.org,
> chose other, request hinting
>
>
> pabs suggests to request britney hints to get the bpfcc migrated.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
