Any idea why none of the F32 builds for this package are going to stable? I couldn't find any bug reports for container-selinux but that might be the wrong place to look. The problem currently only affects F32, F31 is fine.

BZ#1835275 mozilla-ublock-origin-1.28.2 is available
BZ#1841091 mozilla-noscript-11.0.34 is available

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.

@jherkel: See the above comment by @dimitrisk on the sound-related regression #1852564. (BTW, the link for Fedora-Flavored Markdown is dead.)

Confirming that dpdk-examples-19.11.1-3.fc32 is installable once dpdk-19.11.1-3.fc32 is installed. Have not tested functionality.

BZ#1841960 dpdk-examples-19.11.1-2.fc32 is uninstallable

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

Giving a +1 since this version makes dpdk installable, and since it should have gone to stable by time. Haven't tested functionality.

This is not installable only because the corresponding required version of openvswitch was never pushed to stable. See and . When I install it from , then dpdk is installable.


Not installable:

Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): dpdk x86_64 2:19.11.1-2.fc32 updates 4.0 M

I'm guessing that the mame update was intended to be marked as stable by time. I'd test mame if I knew how.

Today is F30 EOL, so I doubt this will get to stable. I just asked a question at 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).

Just out of curiosity, why didn't this get submitted to stable automatically at 14 days?

BZ#1836699 mozilla-noscript-11.0.26 is available
BZ#1825039 mozilla-ublock-origin-1.26.2 is available
BZ#1825050 mozilla-noscript-11.0.25 is available
BZ#1820622 mozilla-ublock-origin-1.26.0 is available
BZ#1813501 mozilla-noscript-11.0.23 is available
BZ#1797341 mozilla-ublock-origin-1.25.2 is available