This is extremely unlikely to actually get to stable. It will probably be ejected from the push because of the failed test, similar to https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d5b760af5 . There hasn't been a successful push in 2 months. Could someone look into why it's impossible for this to get to stable? Or at least explain why the failed test is required for F32 but not for F31? Will this affect F33?
Couldn't help noticing all the ejects. I have container-selinux-2.135.0-1.fc32 installed from the morning of June 12. I don't have updates-testing enabled and never installed it manually, so it must have gotten into the stable repo, despite bodhi saying it was obsoleted. "dnf distro-sync" wants to downgrade to 2.132.0-1.fc32. The errors here look similar, so it's possible the same thing may happen to this update as well. Please try to determine why these errors are happening. Thanks.
Although I can confirm that the latest version of dpdk-examples is not installable. When I try, it wants to install the original release version and also downgrade dpdk and openvswitch.
Installing: dpdk-examples x86_64 2:18.11.6-1.fc32 fedora 804 k Downgrading: dpdk x86_64 2:18.11.6-1.fc32 fedora 3.1 M openvswitch x86_64 2.12.0-2.fc32 fedora 2.0 M Skipping packages with broken dependencies: dpdk-examples x86_64 2:19.11.1-2.fc32 updates 869 k
This is not installable only because the corresponding required version of openvswitch was never pushed to stable. See https://bugzilla.redhat.com/show_bug.cgi?id=1841411 and https://bodhi.fedoraproject.org/updates/FEDORA-2020-add0c5f7c9 . When I install it from https://kojipkgs.fedoraproject.org/packages/openvswitch/2.13.0/1.fc32/data/signed/12c944d0/x86_64/ , then dpdk is installable.
Today is F30 EOL, so I doubt this will get to stable. I just asked a question at https://bodhi.fedoraproject.org/updates/FEDORA-2020-51ce773eb5 as to why the update that was just obsoleted didn't get submitted to stable automatically at 14 days (which would have gotten it to stable by now).