Bug#898329: marked as done (release.debian.org: bpfcc not migrating to testing)
Your message dated Fri, 18 May 2018 14:43:02 +0200
with message-id <ad17dbd4-2b70-f375-087f-f2757b74a758@debian.org>
and subject line Re: Bug#898329: release.debian.org: bpfcc not migrating to testing
has caused the Debian Bug report #898329,
regarding release.debian.org: bpfcc not migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
898329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898329
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
As quoted in Debian Bug #898151
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.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (100, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 10/05/18 12:17, Ritesh Raj Sarraf wrote:
> Package: release.debian.org
> Severity: normal
>
>
> As quoted in Debian Bug #898151
>
> 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 :)
Just to clarify things: being a valid candidate means britney will try to
migrate that package to testing. That can still fail (and fails in this case)
because the package is not installable on i386 (which is a requirement). I'm
overriding that in this case with a force-hint hint.
Emilio
> 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.
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers testing
> APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (100, 'experimental'), (1, 'experimental-debug')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>
--- End Message ---
Reply to: