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 <pabs> I think it is because arch-all packages are depending on packages that only exist on some arches https://qa.debian.org/excuses.php?package=bpfcc 12:19 <pabs> IIRC the release team requires those deps to be satisfiable on i386, so I think bpfcc will need hinting into testing 12:19 <pabs> I got this in an i386 chroot: python3-bpfcc : Depends: libbpfcc (>= 0.5.0-5) but it is not installable 12:19 <ron> oddly, https://qa.debian.org/excuses.php?package=bpfcc says "Migration status: OK: Will attempt migration (Any information below is purely informational)" -- "Valid candidate" 12:20 <ron> so not everything is playing by the same rules if it still isn't :) 12:20 <pabs> yeah, testing migration is sometimes confusing. the log link usually explains things 12:21 <zhsj> Maybe that's it 12:21 <pabs> https://release.debian.org/doc/britney/short-intro-to-migrations.html#migration-phase-2-installability-regression-testing 12:22 <pabs> I'd suggest reportbug release.debian.org, chose other, request hinting pabs suggests to request britney hints to get the bpfcc migrated.
signature.asc
Description: PGP signature
